#brianc-integration

1 messages · Page 1 of 1 (latest)

distant elm
#

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

dim meadow
#

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?

distant elm
dim meadow
#

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?

Learn about authentication to reduce fraud and meet regulatory requirements.

distant elm
#

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 mention authenticating, 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?

dim meadow
#

We have scenarios for both - saving card to charge later and charging now.

distant elm
#

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

Learn how to save card details and charge your customers later.

dim meadow
#

Yes, got it. Setup intents for later, payment intents for now.

distant elm
#

correct

dim meadow
#

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?

distant elm
#

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 PaymentIntent setup_future_usage=off_session

#

yes

#

you can take a look at this sample ^, it contains prebuilt and custom integrations

dim meadow
#

OK. thanks. Does this include support for 3D/3Ds?

distant elm
#

Yes, all the implementation supports 3DS

dim meadow
#

Ah! I wasn't aware of that channel. I will check it out.

distant elm
#

Actually as long as you are using PaymentIntent and SetupIntent, you will be SCA compliant

dim meadow
#

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.

distant elm
#

Stripe Checkout is our prebuilt UI which will save you a lot of headache.

dim meadow
#

Great! Thanks for your help.