#ali-i_unexpected

1 messages · Page 1 of 1 (latest)

short barnBOT
#

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

đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.

humble jay
#

Can you share a Payment Intent ID where this is happening

zealous verge
#

for us to us i do not see a payment intent event just a charge.suceed invent but i see it for Canada to canada but here is the id for charge.suceedd evt_1RRvWrRiSJKnLIEVkP3qeIp0 but in that reponse it has a payment intent id of py_1RQaXrRiSJKnLIEVNjbYMi7l but when i search it i see no event

humble jay
#

So I can see exactly why it's failing

#

To be clear:

Error: "No such customer" (platform can't see connected account customer),

is totally expected

#

In destination charges (where you pass transfer_date) the expectation is the customer exists on your platform account

#

To charge a customer that exists on a connect account you need to do a direct charge instead

#

But can you share a request id where you are getting region errors so I can see what's wrong there?

short barnBOT
zealous verge
#

I don't have a Payment Intent ID for the failing US payments because we're using stripe.Charge.create(), not PaymentIntent.

The US payments create charge.succeeded events (py_1RQZgNRiSJKnLIEVHezv9Xq3, py_1RQaXrRiSJKnLIEVNjbYMi7l) but no PaymentIntent.

Canadian payments DO use PaymentIntent (pi_3RK68PDlMrraekeM16rlpyFD) and work perfectly.

For request IDs with regional errors, I can share from the transfer attempts:

  • req_kiRTo94S3SDD6A (transfers_not_allowed: "Funds can't be sent to accounts located in US because it's restricted outside of your platform's region")

The core issue: US uses Charge API with connected account customers, Canada uses PaymentIntent API with platform customers. Should US switch to PaymentIntent pattern?

inner crater
#

Hi there, I'm taking over this thread from my colleague.

zealous verge
#

Hey! do you need other info from me. i am blocked

inner crater
#

Not at the moment, I'm catching up on the thread and looking at the charges you shared.

zealous verge
#

esentially i ahave a connect platform account registered in canada. i have us and canadian users. i have them authorize future debit payment. canadian users verify instantly and US thrpugh microdeposit. that works. then canada to canada payments through this system work but us to us are not. the money is charged and see a charge.sucessed and then nothing. the money is then trapped essentially after.

inner crater
#

Not sure what you mean by the money is trapped. Looking at py_1RQZgNRiSJKnLIEVHezv9Xq3 this is a Direct Charge and you're not passing an application_fee_amount.

#

With direct charges:

  • The payment appears as a charge on the connected account, not your platform’s account.
  • The connected account’s balance increases with every charge.
  • Your account balance increases with application fees from every charge.
zealous verge
#

but what i want is to send the money from one connected account to another connected account. both usa. maybe i am doing this wrong? i can share my code for the us part? or maybe you can share what curl commands i need to run

#

Exactly! I want to transfer the full amount from one connected account to another (both US).

Direct Charges put money in the payer's connected account, but I need it to go to the recipient's connected account.

What's the correct architecture for connected-to-connected transfers? Should I:

  1. Use platform charges with transfer_data instead of direct charges?
  2. Use a different Connect flow entirely?
  3. Convert US users to platform payment methods like my Canadian users?

Canadian users work because I use PaymentIntent with platform customers + transfer_data.

#

can us to us even work on my specific platform?

#

you there?

inner crater
#

Still looking into this

zealous verge
#

thanks. take your time

inner crater
#

Ok, I took a look at your integration for Canadian transactions, you're using Destination Charges with on_behalf_of

#

However with the US you're using Direct Charges.

#

These are two different approaches.

#

Circling back to transferring between the US connected accounts. There's a feature that's restricted.

#

I recommend reaching out to support and requesting that you be allowed to take advantage of this feature.

#

Unfortunately, we're not in a position to grant access.

zealous verge
#

okay. Will they grant acess or i need to prove aomething? How do i streamline it?

#

also once i get acess what method should i use?

inner crater
#

I don't know what the process is for reviewing access. Once they provide access, they will share how you can perform the transfer between the accounts.

#

I'm going to trigger a flow that will have our bot send you a SM to create a support ticket. Let them know you'll like to have the feature enabled for you.