G’day - just working with a team in Australia trying to stand up a Sharetribe platform with peer to peer sales. I was surprised when an item I sold was rejected as I hadn’t approved payment in three days.
Can this setting be changed or the function removed?
Hi Dan! The 3 day limit is there, because when the buyer pays, Sharetribe makes a preauthorized payment from buyer’s credit card. PayPal allows us to keep the payment in the preauthorized state max 5 days (if I remember right), and after that the payment can not be completed anymore. The payment will be automatically voided by PayPal after 5 days. So that’s why there’s the limit.
What you could do is to extend the limit to 5 days and it would probably work out of the box. When we implemented this feature, we wanted to add some extra buffer there and that’s why Sharetribe uses 3 days, not 5 days.
I wouldn’t recommend removing this feature.
In addition to the PayPal limitation, I feel that this is also better for buyer experience. When the buyer has made the payment, she probably wants to know as soon as possible if the sale is going to happen or not.
How does this sound to you, does it make sense? I’d like to hear your opinion. What kind of marketplace do you have and why do you think it would make sense to remove the limitation?
Hi,
I answer to this topic long after it has been opened but I’d also like to make at least 5 days and not 3 days. I sell secondhand products and my main competitor offers 7 days to validate. People are used to it and it doesn’t bother them. On the contrary, 3 days is too short because if people go on week-end for more than 3 days, they can’t validate ! And I had that problem that my private sellers weren’t over connected and missed sale…
This could possible be a bug. Even after changing stripe_expiration_period to 1 day , The email was sent with message as 3 days. But the payment was rejected correctly, in one day as per config parameter
You need to accept or reject the request within 3 days.
I appreciate the good work on sharetribe . Its amazing software
Hmm that is strange indeed. That value, in the email, comes from payment_expires_in_count, which through a few hops, uses the same stripe_expiration_period value…
Maybe some troubles with the locale/translation cache? Hopefully, you’ll have a chance to get this right.