#mallain23_best-practices

1 messages · Page 1 of 1 (latest)

cloud solsticeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1301956496216821800

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

solar siren
#

Hi 👋

That depends entirely on your business case. The default is to just use automatic capture

frail rock
#

My default seems to be manual capture

#

We aren't setting manual or automatic but we are still getting a require capture status

solar siren
#

Okay, would you rather have automatic capture?

frail rock
#

I am trying to figure out the pros and cons and which one to chose?

solar siren
#

As I said, that depends on your business model. The auth and capture approach makes more sense in situations where you provide a service and then collect payment. That way you have already validated the customer can pay their final bill

#

But if you are simply selling a good or charging for the service up front, the auto capture approach might make more sense, as it's less steps

frail rock
#

Ok that makes sense - if the capture fails does stripe cancel the payment intent?

#

Or do I need to handle that myself

solar siren
#

Payment Intents aren't canceled unless you explicitly cancel them. The idea is that you can bring the customer back to attempt to collect funds after the first failure.

frail rock
#

Ok - so when in the flow does the auto capture happen. I know currently we cerate the payment intent, then collect payment method, then confirm payment intent and then cpature the payment (manual flow)

#

How does it work with automatic

solar siren
#

With auto the funds are captured in the confirmation

frail rock
#

Gotcha - and confirm payment intent is always a manual step?

solar siren
#

It depends on your terminal integration

#

For server-driven terminal integrations with readers like the Wise POS E, you pass the Payment Intent to the reader with the process_payment_intent API call and the reader handles it from there

frail rock
#

Ok i think we have the m2 reader

solar siren
#

But with other types of integrations, the reader just collects the card details locally and you need to call the confirm API to pass the payment details to Stripe

#

Okay so that is the later scenario

frail rock
#

gotcha

#

and do you know at what point that the customer gets notified that the card was charged (the funds are on hold) is that when the payment intent is confirmed or when payment method is collected?

solar siren
#

So when a user scans their card with your M2, it's like they have filled out their card details on a website but they haven't pushed the Submit button. When you call the confirm API, that is like the Submit button being pushed

#

and do you know at what point that the customer gets notified that the card was charged (the funds are on hold) is that when the payment intent is confirmed or when payment method is collected?

That is the confirm step, when we perform an authorization with the bank that issued the card

frail rock
#

Ok thanks

solar siren
#

Sure thing! happy to shed what 💡 I can 🙂

frail rock
#

one last question

#

is there a set of error codes to look at to see if the confirm/capture fails - how i should react/if i should let customer try again

solar siren
#

Whether or not you should let the customer retry is up to you but the decline code should tell you if they can use the same card or not

frail rock
#

Ok and if you try a new card, do you have to do anything with the old payment method or just by collecting the new payment method with the payment intent should work?

solar siren
#

If the card was declined, there is no payment method. We don't save it

#

Using the same Payment Intent to collect a new payment method is exactly how you should handle that situation

frail rock
#

thanks

#

ok appreciate it

solar siren
#

Great 🎉 Happy to shed what 💡 I can 🙂