MultivendorX Pro
-
Posts
-
-
Can you please provide an update on when we should expect the newer version of the Stripe API is set to be released for the MVX Pro Stripe Marketplace module? I know I was told a few months ago that it was being worked on, but I haven’t seen it as part of any updates – core or Pro – so I wanted to see if you have a projected released date for this. We ran into an issue and the updated API is needed to fix or prevent it.
-
-
Hi Sangita, we ran into a problem with 3 vendors on a single order using Stripe Marketplace module (Stripe Connect Express with Destination Charges) and the first vendor’s charge succeeded, but the bank flagged and denied the second charge for security reasons so Stripe didn’t even try to charge the 3rd one. Consequently, the entire order and all suborders got deleted from the website even though the customer was charged for the products from the first vendor and received an email that the order was successful. Stripe support told us that we needed to use the latest Stripe API version and that would fix part of this issue.
If I look in the MVX Pro code, it shows “STRIPE_API_VERSION = ‘2019-02-19’;” so it doesn’t appear MVX Pro is using the latest or one of the latest versions.
If you can’t update to the latest version, can you tell me how to possibly handle the scenario that we ran into? So that if Stripe sends back a payment failed response on a second or third charge that the entire order won’t be removed? It’s a difficult scenario to replicate so I’m not sure how to go about that.
-
-
Hi Sangita, I talked to Stripe support again and it seems the first Stripe support person was wrong and gave me bad information. The issue still exists however the solution is not on Stripe’s end regarding the version of the API. With Destination charges, there can be multiple charges for one order (for example, 3 vendors and 3 charges for 1 order) so when one of those 3 charges fail, something bad in MultivendorX/WooCommerce happens since the order gets deleted.
I’m not sure if you have seen this before. We’re considering changing to Separate Charges and Transfers instead of Destination. Do you have any thoughts about how to prevent the order deletion in the event that not all charges are successful on an order, but at least one is?
-
@Justin Harrison We have made multiple attempts to replicate the situation on our side, but unfortunately, we have been unsuccessful in doing so. Please provide us with details about the conditions necessary to recreate this issue on our end (specifically, the reasons for Stripe charges being declined). It is crucial for us to experience the same scenario and encounter the error to effectively assist you. Without replicating the issue and receiving the corresponding error, our ability to provide accurate assistance is limited. Your cooperation in this matter is greatly appreciated.
-
I don’t know how to replicate the scenario. I’ve never seen it before and there’s no way to replicate it in a sandbox that I can figure out. A customer’s bank allowed the first charge for Vendor #1 and then denied the second charge for Vendor #2 that were both part of the same order. I have no idea how to replicate a denial on only part of an order in a sandbox environment. It’s more theoretical on figuring out how it might happen because I don’t know how to recreate that on Stripe’s end. I am in the same boat as you trying to troubleshoot the issue because it’s nearly impossible to replicate.
-
@Justin Harrison, We made multiple attempts to replicate the issue on our side, but unfortunately, we couldn’t reproduce it. Without being able to recreate the problem and examine the error, it’s challenging for us to implement a fix for the issue.
Can you contact the stripe team, whether they can provide any such scenario for testing end, that might help us. -
@Sangita. We were never able to replicate the issue intentionally (even though it happened a few times with actual customers) and getting help from Stripe was painful and we got different answers each time we called. Since we switched over to Separate Charges and Transfers, the problem has resolved itself. You can close this ticket. Thank you for trying to help.
-
-
The topic ‘Expected Release Date of Stripe API’ is closed to new replies.