#pc_api

1 messages · Page 1 of 1 (latest)

fiery groveBOT
#

đź‘‹ 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/1326243290013634580

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

atomic hamlet
#

Hello! I think that Dashboard link got cut off or broken by our bot or Discord, can you share that again?

#

Also, can you tell me if you're using direct or destination charges?

fossil garden
#

I truncated the link to hide the customer’s ID

atomic hamlet
#

Oh, gotcha.

fossil garden
#

can you tell me the diff between direct and destination charges please ?

atomic hamlet
fossil garden
#

k just a sec

#

direct charges

atomic hamlet
#

With direct charges the payment and refund objects all exist on the individual connected accounts. To access them via the API you'd need to specify the connected account ID in your request, so you would already know which account was involved.

#

You would use that technique combined with the Refund APIs, the Payment Intents APIs, etc.

fossil garden
#

there's only charge and payment_intent as parameters, but can I use account_id aswell ?

atomic hamlet
#

See the docs link I provided above about making requests on connected accounts.

#

The account ID is not a parameter, it's set in the header of the request.

fossil garden
#

ok i'll check

#

oh i see now, thx !