#kaustuva-le-payments

1 messages · Page 1 of 1 (latest)

vivid stump
edgy crescent
#

Hey there! Are you using direct charges?

reef bone
#

Yeah, I want to create the charge on the connect account but want to save the payment method on the platform account

#

Can I do this by direct charges?

#

On connect account I want to have : cloned customer and payment Intent
On platform account I want to have : original customer and payment Methods attached to the original

edgy crescent
#

No, the PM needs to exist on the connected account for direct charges. So you'd need to clone it to that account

reef bone
#

That's fine. I'm okay with cloning the payment method to the original platform account. But how do I get the paymentMethod from the payment Intent?

edgy crescent
#

No, you most create the PM on the platform and then clone it to the connected account. It doesn't work the other way

reef bone
#

Can I do this?
1.create paymentIntent on connect acccount passing the connect account customer as parameter
2.obtain the paymentMethod from the paymentIntent
3.Clone it to the platform account.
4. Attach it to the platform account customer

edgy crescent
#

This is all outlined at the doc I sent above

reef bone
#

So I cannot directly create paymentIntent and pass setup_future_usage = true?
I have to. create the paymentMethod separately?

edgy crescent
#

If you need the PM on the platform, then you need to create it there and clone it to the connected account to create the direct charge

reef bone
#

So after cloning the paymentMethod to the connect account, I'd craete a paymentIntent using the cloned paymentMethod?

edgy crescent
#

Exactly

reef bone
#

okay. I also need the paymentMethod because I want to pass it to a subscription schedule for a future charge

#

So for applepay and googlepay as well I'd have to create a paymentMethod first and clone it and then create a paymentIntent?

edgy crescent
#

I'm not sure I understand how Apple/Google Pay fit into this?

reef bone
#

They use paymentIntents too and work with subscription schedule

edgy crescent
#

Right, but you don't need a separate Payment Method for them

reef bone
#

Okay

#

So for applepay and googlepay we currently directly create the paymentIntent on the connect account. I want to use the wallet with a subscription schedule too

#

and subscription schedule has the option of passing a paymentMethod as parameter

#

So if I'm not creating a payment method for the wallets, how do I use them with the subscription schedule?

#

Do you have any documentation handy on how to use wallets with subscription api?

edgy crescent
#

How are you collecting payment information from your users?

reef bone
#

We want them to have the choices of 1. card 2. apple pay 3 google pay

#

The first payment ( deposit ) we capture as a regular payment in our system.

#

The remainder we want to capture as a subscription schedule with one instalment

#

and the method of auto debit would be the payment medium in the earlier step. i.e. whichever the user used for the deposit out of 1. card 2.gpay 3applepay

#

so we need to pass the method of payment which was used for the regular payment and use it for creating the subscription schedule

edgy crescent
#

I mean, which API/integration are you using to present payment options to your user? Checkout? Elements?

reef bone
#

Elements

edgy crescent
#

Then if they choose Google/Apple Pay in that UI, the resulting payment will included the associated PM created from that wallet

reef bone
#

...and I can retrieve this PM created from the wallet and use it to create a subscription schedule?

edgy crescent
#

Yep, exactly. It'll be attached to the Payment Intent from your initial 'deposit' payment

reef bone
#

so how do I retrieve a PM from a PI?

edgy crescent
#

There's a payment_method field on the PI object

reef bone
#

Thanks a lot