#ian-payment-cloning

1 messages · Page 1 of 1 (latest)

dense remnantBOT
keen ibex
#

Hi there. Can you share the setup intent id and payment intent id for this scenario?

terse hare
#

pm_0MDBplhLmgflUCXoIHqwwluV

#

seti_0MDBpKhLmgflUCXoYxcHbEix

#

i just created those in my app

#

what other info do you need?

keen ibex
#

The payment intent id too. You said you created a setupintent first then created a payment intent later?

#

And the payment intent is what failed right?

terse hare
#

yes it failed in creating a payment intent

#

so i dont think one is created

keen ibex
#

Yeah can you share the request id?

terse hare
#

i need to go look for it

keen ibex
#

Gotcha. Based on the error you described it sounds like you just need to make sure you set up the PM on the connect account too

terse hare
#

ok so i create it on the platform account first when i call confirmSetup

#

then before i create the payment intent on the server i create teh payment method passing the connect account id

#

but that errors too saying i cant create a sepa_debit payment method in the sub account if i created it already

keen ibex
#

Is there are reason you are creating it on the platform first?

terse hare
#

that error message is in my original post

#

confirmSetup creates it on the platform

keen ibex
#

Are you trying to share it with multiple connect accounts?

terse hare
#

not necessarily but that would be helpful if it were possible.

#

oh i see it here

craggy furnace
#

ian-payment-cloning

#

👋 I'm taking over so let me know if I can help though you seem to have figured it out

terse hare
#

my question is i guess payment method cloning is only supported for ach and card so if i want to do something similar for sepa debit then i guess i should follow that guide and use a different client side method

craggy furnace
#

correct

terse hare
#

do you know of a way to share those payment methods back to the platform

#

or do they have to be isolated to the connect account they were created on?