#mike_docs
sly portalBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1439844939671535708
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
agile pelican
Hey! Could I get the request ID where you received the error?
You may refer to this guide to locate request IDs in your Stripe account: https://support.stripe.com/questions/finding-the-id-for-an-api-request
warped wasp
Hey! I can't see the error logs from my testing the other day, so just tried a fresh request.
Here's the corresponding ID: req_isjmynSIj4RWW6
agile pelican
Thanks for sending the request!
This request was made using the account: acct_1R4WEtGH37msJjnK, however, the setupintent was created on the acct: acct_1RxfS56uGy4qW8IZ, you would need to make the request with the Stripe-Account being acct_1RxfS56uGy4qW8IZ in order to access the setup intent
warped wasp
Yeah, so I realise the account is different. What I'm wondering is whether we can retrieve a SetupIntent on a connected account by specifying the ID of the connected account? This is something that can be done via the Stripe Shell, but I'm unable to do this from the Android Terminal SDK using the provided retrieveSetupIntent() method.
agile pelican
Hmmm, I see that the account acct_1RxfS56uGy4qW8IZ is an Express Account, are you planning to use destination charges together with the CA's SetupIntent?
warped wasp
Ahh good question. I'm not across those details as I'm not involved with that part of the integration. Just checking with my client.
warped wasp
So, they're planning to use destination charges for one-off payments, but this feature is already supported and tested in the app. They're not planning to use destination charges with the SetupIntent for the connected account
Re: the Express Account, they're just using these by default, but are happy to use another account type if there's another one that's better suited.
agile pelican
Apologies, I am a bit confused by the setup here😓
What do you mean by "They're not planning to use destination charges with the SetupIntent for the connected account"?
Reading your original question:
Dcode has existing clients (connected accounts?) who have Customers existing on their Accounts.
SetupIntents are created on the Connected accounts for the Customers.
Now Dcode would like to process payments using the Android/iOS Terminal, and the question is how can payments be processes with the setupIntents that exists on the connected accounts?
warped wasp
Sorry for the confusion!
One of the features that Dcode want to support is attaching a payment method to an existing customer on a connected account for recurring charges.
We're fairly new to dealing with SetupIntents in Stripe, but our understanding from the linked doc is that the usual process is to create a new customer that is cloned to the connected account. Something like:
- Create the Customer object on Dcode's Stripe account.
- Create a SetupIntent for that customer.
- The Terminal SDK retrieves that SetupIntent.
- The client side app collects the card via a tap.
- Confirming the SetupIntent creates a PaymentMethod.
- The Customer and PaymentMethod are cloned to the connected account and are subsequently used for recurring charges.
This is fine for new customers, but Dcode want a way to setup recurring charges for customers that already exist on a connected account. We thought that instead of creating a Customer object and corresponding SetupIntent on Dcode's Stripe account, we create a SetupIntent for the customer on the connected account, then continue with steps 3-5 in the above example. We weren't sure whether this was supported, but from testing in the Stripe Shell we thought it may be. If this is the wrong way of going about it, is there another way to set up recurring charges for that customer?
Please let me know if I've explained this poorly!
agile pelican
thanks for the clarification! It sounds like you guys closely followed this doc: https://docs.stripe.com/connect/direct-charges-multiple-accounts#set-up-recurring-payments , which you initially sent.
Just to clarify that this document covers Sharing Payment Methods for Direct Charges
Firstly, let me address some pointers regarding your current setup
- When using Direct Charges, the recccomended connected account type to be used alongside it is Standard Accounts.
- The account (acct_1RxfS56uGy4qW8IZ) which the setupIntent was created on is actually a Express Account type, which is not the recommended Account type.
- I suggest going through this document here to understand the relationship betwenn Standard Accounts and Direct Charges
Next, if Standard Accounts are used together with Direct Charges, then creating Setup Intents for recurring charges might be a little complicated. I think my question would be Is there a need to create the Customer in the Platform (Dcode) Account in the first place? Why not just create it in the connected Account? doc
The Customer object you create on the connected account has no association with the original Customer object stored on your platform account. If you update the original customer information and want to keep them synchronised, you must also update any corresponding customers saved on connected accounts.
It just seems like additional complications compared to just creating the Customer on the Connected account
agile pelican
Just to clarify, cloning payment methods is mainly used when creating direct charges on multiple connected accounts using the same saved payment information.
I understand that there is a lot to go through here. If you would like, we could communicate further over email, from there, we can explain to you more in detail about the different Account types, Charges and provide additional tips on how to achieve the result you want.
warped wasp
Thanks for the info! If we can continue this via email that'd be great! There's more contextual information that I can provide, which will hopefully clear up what we're trying to do. We're based in Melbourne, Australia, so it's actually after close of business here, so I won't be able to get in touch with my client until tomorrow.
Shall I share my email address here?
sly portalBOT
agile pelican
Nope no need to share an email address here!
You can write in to my team - I will be dropping you a DM on how you can do that, and we can take it from there.
sly portalBOT
Hello @warped wasp, we have sent you a direct message, please check it at https://discord.com/channels/@me/1439887364347527220
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.