#kaustuva-le-paymentmethod

1 messages · Page 1 of 1 (latest)

lapis grail
#

hello @shrewd sun! can you share the request id?

shrewd sun
#

req_u2jNtBgOdppwjK

#

when I search for pm_1KTdSHFUtwYrZPVCGZXaoiaZ on the dashboard I can't find it

lapis grail
shrewd sun
#

acct_18NGoVFUtwYrZPVC

#

It's a connect account

lapis grail
#

hmmm, iirc, you won't be able to search in the Dashboard for a PaymentMethod that isn't used to make a payment or attached to a customer yet

#

you should still be able to access it via the API though

shrewd sun
#

Okay. Another thing is my client/frontend is creating it in a connect account. Ideally I'd want it to be created on my platform account. How do I control that?

lapis grail
#

remember to omit/redact your public key in case you hardcoded it

shrewd sun
#

Thanks. I realized I was passing my connect account id additionally while initializing it

lapis grail
#

glad to hear we managed to figure out the issue 😄

shrewd sun
#

Hi I want to create a PaymentIntent on the connect account but save the Payment Method with the customer on platform account.

For this....it was earlier suggested that I create a PM on platform, attach it to a user, clone the PM on connect account and then create a PI with the cloned PM on connect account and then confirm the PI on the front end.

Since the PI will be confirmed on the front end...I would have to load stripe with the connect account.

So in that case, I would have to let the backend create the initial PM and then clone it instead of letting stripe.js create the PM ( since stripe.js would have to be initialized for connect account and I want the PM to be created on platform account )

#

Issue is...on the front end I need to create PM on platform account, but confirm the PI on connect account.

lapis grail
#

i'm a bit confused over the question, could you perhaps try rephrasing?

shrewd sun
#

I want the customer to create a charge on our connect account but save the payment method ( card ) on the platform account. How can we achieve that?

#

We already have clones ( customer and identical account ) on both platform and connect accounts

lapis grail
#

since you've created the PM (assuming with a SetupIntent), it should already setup for off-session usage. As the previous suggestion mentioned, after the PM has been created on the platform, you would clone that PM to the connected account. You can then create and confirm the PaymentIntent (for the connected account) in the server

shrewd sun
#

I haven't created the PM, what is a good way to do it? Is it advisable to create it on the backend?

#

I cannot create it on my front end because stripe on frontend is configured for connect account

#

configured for connect account since I need to confirm the PI on connect account

#

If I configure my front end for platform account... I can create the PM and pass it, complete cloning, create PI etc. but cannot confirm the PI since the PI will be on connect account

#

can I pass {stripeAccount : connect_account_id} header on front end calls?

#

I essentially need to make two front end calls, one for platform the other for connect account

#

is there a server side equivalent for :

await stripe.confirmCardPayment

shadow violet
#

Hi there! Please allow me to jump in to help!

#

To clarify, the confirm on the PaymentIntent does not necessarily have to have the customer to confirm it manually.

#

I recommend creating the PaymentIntent for the Connected account in the server, with the header you have provided above.

shrewd sun
#

Thanks. I'll try that

vagrant whaleBOT
#

This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact

keen flame
#

@shrewd sun what's up?

shrewd sun
#

Hi. So as Makoto recommended, I'm creating and confirming the paymentIntent on the backend now

#

However I want to trigger 3DS check on the front end

#

How do I do it without using stripe.confirmCardPayment

keen flame
#

you should be using confirmCardPayment. Any reason why you don't want to?

shrewd sun
#

Reason why I cannot use it is my stripe object is configured to use {stripeAccount : platform_account_id }

#

and the paymentIntent is on the connected account

keen flame
#

yep then you have to create a different instance of the Stripe object and use that

#

this is something that happens when using this cloning paymentmethod feature

#

it usually makes sense to do

var stripePlat = Stripe(key);
var stripeCA = Stripe(key, {stripeAccount:"acct_xxx"});
...
stripePlat.createPaymentMethod(...)
...
stripeCA.confirmCardPayment(...)
shrewd sun
#

Thanks a lot.
{stripeAccount:"acct_xxx"} header on every stripe.js call would have been nice though haha

#

I'll try what you recommended. Thanks