#Zambo
1 messages · Page 1 of 1 (latest)
Hi 👋
Can you share the request IDs where you are seeing these failurs?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Hello: req_mgGU64sLWomK9w
Okay so I'm trying to follow this flow. So the PM is first created from your US account with on_behalf_of set to your UK account, then cloned to the CA account and that is when you are trying to use it and hitting SCA issues?
That's correct, and the US account is the platform account
And you have the same customers who need to pay off-session across multiple accounts?
There are flows where users make an initial payment and then follow up payments are charged later by us off-session, and another flow where users provide payment details only, which we would again charge later off-session
Hi, stepping in as snufkin is away. Pease give me some time to catch up here.
I'm trying to reproduce this on my end, it might take some time.
Thanks, let me know if I can provide more detail.
If I can summarize and get your confirmation here, that would be great.
You're creating an on_behalf_of SetupIntent using a cloned Payment Method from a US Platform account to a UK connected account. You're using a card that is Authenticate unless set up and seeing SCA failures when you specificed off_session. Is that correct?
Not quite, we create the SetupIntent with the US Platform account with on_behalf_of set to the UK account. Then we clone the resulting payment method to the destination connected account with connect, and attempt to direct charge that payment method using Connect
Can you share the Setup Intent creation request id please for the above Payment Method used on this request, req_mgGU64sLWomK9w?
Sure: req_5uyFRppMgGoTEO
Any further guidance here? This must be a fairly common case - multiple currencies and entities and the need for SCA support
I'm still trying to test. I needed to create a new account, thank you for your patience.
I'm confirming with a colleague now
Ok thanks
I was able to talk this through with my teammate and we think this might be a test mode quirk that we will flag with the team. On this particular case, it looks like you created the Setup Intent on_behalf_of a GB account. Then, the cloning took place on another account that is from a different region which is leading it to fail SCA. Could you try creating the Setup Intent and clone the Payment Method on the same account to see if that solves the issue?
Yes - this is how we were directed to accommodate this case in the thread above. Per my original message:
Create a SetupIntent on our platform/US account with on_behalf_of set to our UK account, followed by cloning the payment method to the destination connected accounts (US account/USD, CA account/Canada) using the Authenticate unless set up test card, and we're still seeing SCA failures every time we create an off_session payment intent
We only have API keys in our app for the US/platform account
So we need to be able to store payment methods that we bill later with our different subsidiaries or in different currencies - depending on their contracts/purchases with us
It sounds like you're suggesting to not use Connect and just manage each account with its own API keys separately? I don't think that allows for this use case
Yes, that should work in live mode but we think in test mode, it's buggy.
The above answer was for
So we need to be able to store payment methods that we bill later with our different subsidiaries or in different currencies - depending on their contracts/purchases with us
On this portion:
It sounds like you're suggesting to not use Connect and just manage each account with its own API keys separately? I don't think that allows for this use case
No, that is not what I'm suggesting.
We have let the team know of this buggy behavior in test mode.
Thank you for bringing this to our attention.
Okay - but we can't really push this to production without knowing that it will work?
Appreciate the assistance - are you able to provide me with an avenue to escalate the issue? SCA support is critical for us
This is supported and works in live mode. You can write in to Stripe Support but there is not timeline on when it will be addressed I'm afraid.
Okay thanks