#brianc-integration
1 messages · Page 1 of 1 (latest)
Depends on your resource and current implementation.
Pre-built checkout is relatively simpler in terms of coding; other options will give you more control on customisation.
But all should work
OK. We are using the UI components now for one client, Prebuilt for another. For each we will need a link back to our site for failed payments. Any samples that you know of for that?
yup, Stripe webhook is built for this purpose.
You can listen to the payment failure events
you can listen to payment_intent.payment_failed
https://stripe.com/docs/api/events/types?lang=node#event_types-payment_intent.payment_failed
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I see. And then send an email to the customer to have them checkout again? in the case of the crowdfunding, the cards are charged after checkout is closed. I'm guessing we need to create another custom checkout page specifically for the purpose of authenticating so the card can be charged? Seems specialized. Any samples of this scenario? I see the flow in the support docs but nothing beyond that with any more detail as how to handle that.
Also, using 4000000000003220 test card to trigger 3D secure flow doesn't seem to trigger it. It just authenticates. Following instructions from here https://stripe.com/docs/payments/3d-secure - testing the 3D secure flow. I can't seem to get this to even trigger. Hoping it's not going to be a long night.... any samples?
I'm guessing we need to create another custom checkout page specifically for the purpose of authenticating so the card can be charged
You don't have to create another form to complete the checkout no, there should be no difference between new and retry.
Another thing, you mentionauthenticating, do you mean 3DS authentication? the 3DS authentication is done while your customer is online in your checkout page.
just curious, are you saving your customer's card and charging them now?
We have scenarios for both - saving card to charge later and charging now.
In order to be SCA compliant
- Saving card: you will have to setup the card using SetupIntnent https://stripe.com/docs/payments/save-and-reuse
Once the card is setup, the transaction will be eligible for offline charges with out requiring your customer to 3DS (authenticate) again
Yes, got it. Setup intents for later, payment intents for now.
correct
For paymentIntent, you can also setup the card by using setup_future_usage=off_session
https://stripe.com/docs/payments/save-during-payment
But this would not replace setup intent, correct?
It is for pay and then save. We don't have that scenario
Any working checkout samples for the 3D/3DS and all of this?
But this would not replace setup intent, correct?
It will. It is like a workflow where your customer on your checkout page, there is a checkbox (do you want to save the card); instead of making two API calls, SetupIntent, PaymentIntent -> you can just achieve this by one API call using PaymentIntentsetup_future_usage=off_session
yes
you can take a look at this sample ^, it contains prebuilt and custom integrations
OK. thanks. Does this include support for 3D/3Ds?
we also have a developer channel https://www.youtube.com/c/StripeDevelopers/videos
Yes, all the implementation supports 3DS
Ah! I wasn't aware of that channel. I will check it out.
Actually as long as you are using PaymentIntent and SetupIntent, you will be SCA compliant
Cool. Ok. Last question.... We currently using .NET/Angular but have you worked with the React components for this? Would that save us some headaches? Really not looking to dive deeply into custom implementation if not needed.
Stripe has our own React library https://stripe.com/docs/stripe-js/react
Stripe Checkout is our prebuilt UI which will save you a lot of headache.
I recommend you take a look at https://stripe.com/docs/payments/checkout and see if that best fits your need
Great! Thanks for your help.