#Sv1751
1 messages · Page 1 of 1 (latest)
the PI is not Platform/Connect charge
this is also a normal Charge not a Connect Charge
are you trying to create a Direct or a Destination Charge?
because you're not really creating a Connect Charge
this is how to create a Direct Charge https://stripe.com/docs/connect/direct-charges
this is how you create a destination charge https://stripe.com/docs/connect/destination-charges
Can you, please, check this payment. Is it also not real charge? acct_1MtSLHDUm4L7uoSJ
pi_3MtSRNDUm4L7uoSJ3QtbGida
Hi! I'm taking over my colleague. Please, give me a moment to catch up.
sure
Could you please summarise the last question/issue?
They are the same: We use PaymentIntent API and Connect. Currently trying to pass payment method manually in PaymentIntent request and found out that the payment is completed even if the payment method is blocked or disabled for the connected account that we pass at the same PaymentIntent. Is it expected behavior? We are in test mode.
What do you mean by "the payment method is blocked or disabled"?
This one is a Direct Charge
we can block to use payment method for our connected accounts
acct_1MtSLHDUm4L7uoSJ
pi_3MtSRNDUm4L7uoSJ3QtbGida
aa, this is the same
we use direct charges but with connected accounts
we can block to use payment method for our connected accounts
Still not sure what you're referring to with this. How are you blocking a payment method?
in payment method section in dashboard
And you see them in your Connect payments?
You also got settings for your Connected Accounts: https://dashboard.stripe.com/test/settings/payment_methods/connected_accounts
we see them there but they are disabled
Did you disable them for your Connected Accounts? In the panel that I shared?
Do you see them on the Payment Element? For this PI? pi_3MtSRNDUm4L7uoSJ3QtbGida