#cnguyen

1 messages · Page 1 of 1 (latest)

signal sunBOT
simple stirrup
#

Hi. I want to save the customer credit card information with off_session to handle subscription later.

I have 2 way to do it :

  1. I save the credit card with SetupIntent. Then, later, I can use the card with off session

  2. I do an authorize of 1€ for example with off_session. Then I release the 1€. Then later, I can use the card for the subscription

What is the best solution? I'm scared to use the SetupIntent and have more chargeback for example

atomic pagoda
#

Hi 👋 Setup Intents seem like the better approach there to me.

simple stirrup
#

With SetupIntent, it will display the 3DS ? Or not ?

atomic pagoda
#

Setup Intents can trigger 3DS.

simple stirrup
#

It will be a trigger of which amount ?

atomic pagoda
#

As far as I'm aware those perform a zero-dollar authorization.

#

Which is why I would recommend them because I wouldn't anticipate them leading to chargebacks.

simple stirrup
#

It means that, if I save the card through a SetupIntent of "0€" and if I save the card through an authorise and release of XXX€, it's the same importance for Visa/Mastecard ? I will have the same chance/score when I will do a off session subscription / rebill ?

signal sunBOT
simple stirrup
#

Because I thought that, if I do more payments, I will have more chance to have a good score for the card, So more chance to have no trouble with the card network (VISA/Mastercard) and with the subscription/rebill system

atomic pagoda
#

I would assume that creating authorizations that are never captured would look worse to the card networks, but we don't have insights on how they categorize transactions or how that impacts future transactions you try to process.

simple stirrup
#

OK. You have no idea about how visa/mastercard score the card.

#

At least the 3DS allow to have a "good" score ?

hollow prairie
#

👋 stepping in for my teammate!

#

networks really discourage making $1/1€ authorizations. the best solution in this case is to create a SetupIntent in order to save a card for future off-session charges. this should optimize the card for use with future charges but it's ultimately up to the banks to determine whether any additional customer authentication (3ds) is needed at the time of a future off-session charge

#

the purpose of using a SetupIntent is to have a customer complete any authentication at that point in time but the issuing banks can still require 3ds later

simple stirrup
#

I suppose that if I foce the 3DS for the SetupIntent, I will have more chance to don't have it later for off session payment ? Or at least, to have it more than later

hollow prairie
#

Right, though it's still possible that a bank will require a user to complete 3ds again in the future even if they completed it when sharing their payment details for a SetupIntent

simple stirrup
#

sure