MultivendorX Pro
-
Posts
-
-
I am testing out Stripe Realtime payments and it is failing because of an internal error. I see the following in the Stripe logs:
invalid_request_error
The statement_descriptor parameter is not supported for the payment_method_type card. To continue supporting payment_method_type card, please pass in statement_descriptor_suffix or remove the statement_descriptor parameter altogether. Please see https://support.stripe.com/questions/use-of-the-statement-descriptor-parameter-on-paymentintents-for-card-charges for additional details.The link above says “As of 01/02/2024, Stripe no longer supports the statement_descriptor parameter on the PaymentIntent API for PaymentIntents in which one of the supported payment_method_types is card. Attempting to set a statement_descriptor on a PaymentIntent with a card as one of the payment_method_types will result in a 400 error code. For these requests, please use the statement_descriptor_suffix instead.”
Attached are the logs and more in the next private message.
-
-
Website: https://opl.mystagingwebsite.com/
Use this product to simulate checkout: https://opl.mystagingwebsite.com/product/t-shirt-name-4/
or any other product for the “Ultimate Handmade Store” vendor. Other vendors are not configured for Stripe yet.Attachments:
-
Sorry to hear that you have faced an issue on your end and thanks for sharing the staging site. But we need the temporary admin and FTP access too to check the issue. Also please make sure your test stripe access is added in the staging site.
So kindly share that with us accordingly. Also while sharing the access don’t forget to mark your reply as private. -
-
I noticed another thing. Even though the payment fails, the order is showing as valid with the status “pending payment” and the amount is being shown due to the vendor. I am attaching the screenshots.
PS: Woocommerce just released the fix for statement_descriptor issue for their Stripe gateway.
-
-
-
@KC Sorry for the delayed response as we were closed during the weekends.
We have checked the payment flow on your site with your credentials and the payment flow is working fine without the 3D security. But if we enable the 3D security, then there comes an error while placing an order.
However, We have added our stripe account details on your staging site and also added a test vendor to check the flow. We did not face any issue while placing an order with the 3D security.
It seems there is an issue with your stripe account for 3D security. So kindly get in touch with the stripe team in this regard. They will be able to help you accordingly. -
Hi @sangita, it is good that it is at least working without the 3D security. I am currently testing another Multi-vendor plugin together MultivendorX. Both plugins have been failing since Feb 1 because of the statement_descriptor issue. For this reason, I have been already in touch with Stripe. Stripe pointed me to the page I linked in the message. Woocommerce Stripe Gateway was also failing for the same reason. They released a patch for this a few days ago. You can see the details in the screenshot below. Stripe is saying statement_descriptor field cannot be used any longer and you need to use statement_descriptor_suffix or leave out the statement_descriptor.
Attachments:
-
I did some more testing. With my Stripe account and 3D option unchecked, the payment was initially completed.
But in test #1, the same error shows up in the Stripe log, and under the Vendor’s banking overview screen, the order eventually shows canceled. Nothing shows up on the order screen. The order number in Stripe, on the confirmation page, and on the banking overview screen are all different.
In test #2, payment was reported as successful on the order confirmation page. But it showed up in the order list as payment pending and the banking overview screen as unpaid. Order numbers are different everywhere including Stripe error log.
-
We have added our sandbox details for both admin and vendor on your staging site and tested the payment flow with Stripe marketplace. And the flow is working fine. KIndly check the video here https://www.awesomescreenshot.com/video/24892138?key=9c6afd077285f71d52f05211f4ed7cff.
Kindly check the flow on your end with our added sandbox accesses.
It seems like the issue is related to your stripe access.
Regarding the WooCommerce Stripe issue fix, kindly share the pull where they have added the fix for your earlier mentioned issue. Then it will be easier for us to understand it better and we will be able to look into our code according to that. -
-
-
Ignore my previous comment. I realized the order number visible to the vendor is the sub-order number. I noticed the vendor commission was set to 0 for whatever reason even though in the settings > Commissions, I set it to be 95%. The one thing I do not understand yet is that the commission (earnings) reported on the order page and the order details (vendor dashboard) do not factor in the payment gateway fees. For example, the $18 order shows the commission as $17.10 in those reports whereas the Payments > History correctly reports it as $16.28 (after deducting the payment gateway fee of 2.9% + $0.30).
I am awaiting a response from Stripe regarding the other issue. In all likelihood, since my account was created after Stripe’s change of statement_descriptor, it is getting this error.
-
@KC, you will get the payment gateway details in the transaction details tab i.e. https://prnt.sc/d_YAglh2EuUv
Kindly check there regarding the gateway charge deduction.Also, thanks for sharing the github link, our developers will look into this. We will keep you posted.
-
-
-
-
-
-
-
-
Please LOGIN to reply to this topic