Forum Replies Created
-
Posts
-
Was this resolved? I have the same issue with connecting new users.
It seems Stripe deprecated this option.
“OAuth isn’t available for new Connect platforms. For new accounts, use Accounts API with Express instead. Extensions shouldn’t use Express OAuth, as extensions can’t connect to existing Express accounts”
@sangita It is exciting to hear that you are redoing the dashboard in React. Looking forward to this.
@sangita, is there any tentative timeline for this update? I am working on significant customization of the dashboard. Maybe I can skip that.
@sangita, I looked at the code and don’t see a way to use this filter to add support for webp. The class class-mvx-pro-ajax-media has this case statement (screenshot below). This is what defines what type of media can be displayed. Would it be possible to a line for webp in your future updates? Webp format is becoming very popular due to its superiority over image formats. Thank you for your continued support.
Attachments:
Stripe downgraded my account to use an older API version and I can complete orders now. So, anyone who creates a new Stripe account will face the issue I reported above related to Statement_descriptor.
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.
