#adamreisnz-setupintents
1 messages ยท Page 1 of 1 (latest)
We already use the second approach for when a customer is making a payment, so it seems to make sense to use the same approach if an admin adds a card to a customer manually.
Just wondering if there are other things we need to consider here, or if there are advantages to using setupIntents instead
Yes, so with SetupIntents we actually verify that the card information you customer inputted is valid on the network. If there is a 3D Secure, the SetupIntent flow will prompt to the user to authenticate
Right, so what if an administrator is adding the card, will they be able to verify it for the customer?
The customer will presumably give them the card details over the phone, or in person, so they might be able to complete verification
Just curious, but does you business actually handle CreditCard information like that? Accessing CreditCard information means you are PCI Compliance ready
So our business is a SaaS product, and we allow administrators of say sports clubs, to manage and update card details for their members (if needed).
In most cases the admins will not be involved with this process, as the members will do it themselves and everything will work as expected.
However, sometimes there may be older members who are not technologically savvy, and they might ask the admin if they can give them their card number over the phone.
So we provide the tools to do that
And we are now migrating from charges to payment intents, and so far everything has gone well, was just wondering about this use case.
It's working now using my 2nd outlined method, but wondering if I should refactor it to use setupIntents
I see. So it is already operating that way. And what if the card requires a 3D Secure verification? Your customer will talk it over the phone to your admin?
The sort answer to should you switch over to SetupIntens or not? - is yes, we recommend SetupIntents over just creating PaymentMethod
Ok, I will give it a try. Yes I think the customer will just talk them through the authentication over the phone.
I suppose if we keep using the current approach of just attaching it, there will be no verification, and verification will only happen once they try their next payment?
And if we use setupIntent, there will be verification right there and then, so that might be preferred.
Cool will give it a go, thank you for your help
Yes, ideally. And if the verification happen next time, your customer is not there on the phone anymore, so I was wondering how did you handle those situation until now. Any time!
๐
Would it be possible to combine the two flows, e.g. create payment method, then create customer, then attach the payment method to the customer, and finally create a setup intent and confirm that on the client?
Because it looks I can add an existing payment_method ID to the setup intent
Yes!
Brilliant
This worked perfectly, on the first go ๐
Added the card, verification dialog came up, authenticated and all worked as a charm. Thanks again ๐