#mdubya-setupintent-status
ashen gale
so the scenario is. building a saas platform for Service Providers (SP) utilizing Connect. when a SP's customer goes to sign up for service, i want to collect all the users info and payment info in one page. specifically 'cards'. the cards wont be charged(really just placing a hold) until the SP has signed off on the work order.
docs say for 'save for later' scenario to create a checkout session in one section
daring mauve
Sure, saving cards for later with Setup Intents would be the way to go here
ashen gale
in another section i see use PaymentIntent but that requires an amount to charge and in another it says to use a SetupIntent
daring mauve
Are you having issues with that?
ashen gale
SetupIntent was the way i was leaning for the scenario. regarding the 'return_url' paramater
daring mauve
You need to make a key decision: are you taking payment now, or not?
ashen gale
i am not
daring mauve
THen you want to use SetupIntents (or checkout in setup mode)
Not payment intents (or checkout in payment mode)
ashen gale
i can add logic if a quicker paymentintents are needed.
with the return_url, whats being returned? i assume its appended '&setup_intent=x'?
daring mauve
What do you mean by this? I'm not sure I understand what you're asking
ashen gale
thats for paymentIntents but does setupIntents return a similar identifier of some sort?
im creating a user and a setupIntent not connected to anyone simulataneously. i then have to create a stripe customer and attach the setupIntent to that user
quasi sparrowBOT
daring mauve
Yes, the return url would behave similarly for setup intents
ashen gale
can probably figure the rest out. mostly wanted to make sure SetupIntent was the correct method
and while i have you.
sometimes i get this error, someitmes i dont.
"Unable to download payment manifest "https://pay.google.com/gp/p/web_manifest.json".
ive got google pay disabled both at the connect level and at the local level
it doesnt show it
does seem to be unique to Chrome
gusty pulsar