bluepnume | Stripe Developers | Page 1

twilit laurelBOT Oct 20, 2022, 4:04 AM

#

edgy meteor Oct 20, 2022, 4:09 AM

#

With standard connected account, the liability is on the standard connected account and the charges can only be performed on the connected account itself with Direct Charges: https://stripe.com/docs/connect/direct-charges

Separate charges and transfers (the scenario you described) is only possible on Express or Custom connected account: https://stripe.com/docs/connect/charges-transfers

sage yacht Oct 20, 2022, 4:13 AM

#

Thanks @edgy meteor , that does make sense.

We actually have that working reasonably well already; we have a connected account, we're creating a one-time token, then we're creating a charge using that token. That works great.

That said: we've been advised that to avoid fraud declines, we should also pass a "customer" when creating any charges.

So, is there some way to create a customer (and pass it when creating a charge) without vaulting a card / creating a payment method? -- just using a one-time token

#

essentially I want to do:

customer + one-time-token -> charge

edgy meteor Oct 20, 2022, 4:21 AM

#

Is there any reason why you use token+charge? It's legacy and no longer recommended. The recommend integration is to use PaymentIntent with Elements: https://stripe.com/docs/connect/direct-charges

You can add customer ID in the request after creating a customer (https://stripe.com/docs/api/customers/create):

customer in Charges API: https://stripe.com/docs/api/charges/create#create_charge-customer
customer in PaymentIntent API: https://stripe.com/docs/api/payment_intents/create#create_payment_intent-customer

#

It's possible to use one-time payment method on a customer with PaymentIntent

sage yacht Oct 20, 2022, 4:37 AM

#

Aha! Thanks @edgy meteor . It worked perfectly once I started using payment intent instead of charge. Appreciate the help!

edgy meteor Oct 20, 2022, 4:39 AM

#

No problem! Happy to help 😄

sage yacht Oct 20, 2022, 4:45 AM

#

One quick follow up @edgy meteor: Is there any way to do this so the customer is attached to the platform account? Rather than creating the customer for every connected account when they make a payment there.

It would be nice to have a history for a single customer as they make payments to different connected accounts on our platform. And I'm guessing that way Stripe will find it easier to track the user and apply fraud checks correctly.

#

Mainly we would like to avoid fraud declines when we take a customer who has already paid on merchant A, and have them pay merchant B in future. We may only be able to run Stripe.js for the first payment so it would be good to carry the user's history forwards

edgy meteor Oct 20, 2022, 4:52 AM

#

Standard connected account with Direct Charges will always have customer created on the connected account. It'll not be possible to create the customer on the platform in this scenario.

sage yacht Oct 20, 2022, 4:55 AM

#

Fair! And for express/custom accounts, the only way would be destination charges, right?

#bluepnume