#bebourdain
1 messages · Page 1 of 1 (latest)
What is the issue you're facing? Can you share a Payment Intent ID (pi_xxx) as an example?
Hey again River, how are you? We are not actually facing an issue that we know of at this time. Stripe Support wrote these two messages to us:
"SO note though that since acct_1NQvTSBSaPAUassD is a standard account, they would have to configure their Payment Imtent call creation from their end as this is something you as the platform does not have access to - unless you're using destination charges for them (which is something not really recommended for this type of account)."
"To achieve this, you would need to create a payment intent on behalf of the connect account where you set the payment_method type [2] of your choice and then confirm the payment intent using Stripe.js [3] and the payment element [4]. This will create a checkout session where the customer will have only the payment method option that was passed in the call."
This one specifically confuses me, because we DO have access to their account using Direct Charges, so we are confused.
Do you have the case ID with support?
07180484
I believe that is it. There was a Card's Payment Method inside the case as well.
FYI, I am in another screen, I will be back and check this one every few minutes.
Thanks for sharing the case ID
"To achieve this, you would need to create a payment intent on behalf of the connect account where you set the payment_method type [2] of your choice and then confirm the payment intent using Stripe.js [3] and the payment element [4]. This will create a checkout session where the customer will have only the payment method option that was passed in the call."
What the agent meant is that you may setpayment_method_typesin Setup Intent API or Payment Intent API to control the payment methods to be shown to the customer.
"SO note though that since acct_1NQvTSBSaPAUassD is a standard account, they would have to configure their Payment Imtent call creation from their end as this is something you as the platform does not have access to - unless you're using destination charges for them (which is something not really recommended for this type of account)."
There might be a confusion from the agent here, butpayment_method_typescan be set with Direct Charges (not necessarily with Destination Charges only)
From the case, it seems like you would like to disable the payment method on a specific connected account. It's possible through Payment Method Configuration API, but it's currently in beta: https://stripe.com/docs/connect/payment-method-configurations
You may follow up with the Support about the beta access