#salteesam - checkout sessions

1 messages · Page 1 of 1 (latest)

gloomy sentinel
#

Hello! Just starting a thread for you -- I'll review and respond as soon as I can 🙂

#

You can't do this with checkout -- they will both need to exist at the same level

#

You can use destination charges to send funds to the connected accounts with checkout

#

but the session and payment reside with the platform, along with the saved payment methods

#

Doing what you describe is a fairly advanced custom integration

#

If you already have the payment methods saved, you really don't need to use checkout anyways, you'd be creating the payments directly

#

Why are you using Checkout for the later payments?

manic onyx
#

hmm yeah it's tough, because we want the payment on the connect account but the payment method on the platform account.

We were using checkout sessions, because before we did not save cards. now we are starting to save cards. And then will lets customers checkout as a guest (use the checkout session), or login and use an existing payment method.

so instead could I just:

  • create a payment method on the connect account
  • clone the payment method from the platform account to the connect account
  • use it to pay the payment intent

The only concern here is with the taxes. do payment intents calculate taxes automatically? or will i need to join the order/tax beta?

gloomy sentinel
#

The latter - payment intents don't support this directly. If your primary use case for looking at checkout for these future payments is taxes, the beta is likely the way you want to go with this.