@dancoburn89, I think I know whatâs happening here.
Youâll need to use slightly different API calls for Direct Charges (as Stripe requires you to pass through the Seller Stripe Account ID in the header when getting data direct from a Connected account).
There is a 'Direct Chargeâ version of the âRetrieve Checkout Session Detailsâ call, but not the other you may be running.
Can you let me know what other API calls youâre using and I can add versions that will be compatible with Direct Charges?
Sorry for the hassle. I appreciate the documentation around Direct Charges isnât as detailed as it should be.
on embedded checkout for client secret â> stripe connect - retrieve checkout session details (direct charge)âs client secret.
Api provider - retrieve checkout session details (direct charge)
path checkout session â > current pages transactionâs checkout session ID
header stripe account â> current pages transactions seller account ID
on the success page:
Payment status= stripe connect retrieve checkout session detailâs payment status
aaaand i think i just found the issue as im writing this, probably using the old call for payment status. Let me switch that over and test and ill update if its fixed.
Yep, switched over the updating the payment status from retrieve checkout session details to retrieve checkout session details (direct charge) and now all workflows are running as they should. I really appreciate your help! Its great to have good support behind this plugin.
1 Like
No problem @dancoburn89. Glad we were able to get that sorted.
Best of luck with your app and any other questions just let me know.
