#s123317_api

1 messages ยท Page 1 of 1 (latest)

tardy condorBOT
#

๐Ÿ‘‹ 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/1442822375895863386

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

left grove
#

๐Ÿ‘‹ happy to help

short knoll
#

Hi ๐Ÿ™‚

#

I can't see in the log if we did a correct API call using the header information

left grove
#

basically you're trying to find the creation request of pi_3SXHjuIpbbIMMVWQ1plAYtvE ?

#

you're passing your own account ID instead of the Connected Account ID

short knoll
#

yes. I would like to be sure our set up is correct. That payment Mor should be a connected account

left grove
#

I'm missing something here

#

when you create a Direct Charge on a Connected Account the -H "Stripe-Account: {CONNECTED_STRIPE_ACCOUNT_ID}" shouldn't be the platform Account ID but rather the connected account's

short knoll
#

Thank you i will check and try again

tardy condorBOT
short knoll
#

We did another test. We have this error: the payment is incomplete with error message โ€œNo such reader: 'tmr_GIkw2wa43GC2Dmโ€.

#

We are processing the transaction with a terminal. The terminal is set up on the platform account.

next trellis
#

hey there ๐Ÿ‘‹ taking over for tarzan - do you have the request ID for this error?

short knoll
#

That one : pi_3SXJzWIRAmXmRSgw1DIGL3ux

#

Hi ๐Ÿ‘‹

next trellis
#

hmmm, I don't see the error in the logs for that payment intent

but regardless, you mentioned that the terminal is set up on the platform account

to use Direct Charges with Terminal, the Stripe-Account header needs to be set in every request, end-to-end (so the terminal should be created on the connected account)

short knoll
#

Problem we are processing some transactions on the platform because for one product we need to token the customer cards and register it to the platform.

next trellis
#

ah I see

#

but it's in private preview, so you'll need to request access for your account

short knoll
#

Online we are setting up the api key then entering -h connected account for direct transactions. We can do this with terminal?

next trellis
#

the integration is the same in terms of how you set the keys and the Stripe-Account header, but the difference is that for Terminal, by default, all resources must be owned by the same account (i.e. for Destination Charges, the platform owns the device - for Direct Charges, the connected account owns the device)

short knoll
#

Ok. So we need that preview feature to make it works

next trellis
#

I believe so, but I'm afraid we're not experts in preview/beta features in this channel

my recommendation would be to follow the 'Contact us' link[0], and explain your use case when you contact us, so the product team running the beta can confirm if this is the right solution for you

[0] mailto:stripe-terminal-betas@stripe.com

short knoll
#

Thank you for your help