#nreddy-tokenize-credentials

1 messages · Page 1 of 1 (latest)

shell oarBOT
echo spear
#

Stripe has been tokenizing card credentials for many years, so we don't have support for VST since we're already handling that step

pastel yew
#

can you share documentation on how to implement it ?

echo spear
#

All of our products tokenize payment credentials. There isn't one singular way to tokenize card credentials

#

nreddy-tokenize-credentials

pastel yew
#

can you explain this more?

currently we have integrated stripe payment-intent APIs in accepting payments. And would like to see how tokenization works with Stripe and understand the advantages of using tokens.

echo spear
#

If you're using Payment Intents APIs to create charges, then you're already doing it. What are you using on the front-end to accept card details?

pastel yew
#

hmm, on front-end we use PaymentIntent confirm API to pass customer credentials directly.

echo spear
#

That doesn't make any sense. The Payment Intent confirm API is a server-side function unless you're using Stripe Elements on the front-end

pastel yew
#

give me a minute to exact explain what we use currently.

pastel yew
gilded shadow
#

Hey there just stepping in for two-shoes who needs to head out -- reading over the above now

#

Those payment method details will typically be collected client side using stripe.js (possibly via our react elements package) which handles that tokenization for you.

#

What exactly are you having trouble with?

pastel yew
#

so how do you I use these tokens that was created ??

gilded shadow
#

Can you share some details of your integration, or any guide you're following?

pastel yew
#

In-fact I know that stripe creates payment-method object every time a customer enters card credentials. Does this mean the payment-object itself represents tokens ?

gilded shadow
pastel yew
#

when we set the setup_future_usage=off_session and also provide stripe customer-ID, the token for that particular payment-methods gets automatically saved to the customer in stripe.

gilded shadow
#

Yes that's right

#

Then you can list those payment methods for a customer

pastel yew
#

okay, yes understood. I can list them as saved payment-methods to customer or use them for subscription charges.

#

So as per my understanding tokenization on stripe is implemented for all payment-methods my default for cards, wallets, giropay, ideal, sepa Diect Debit and so on. And is mostly used to save payment-methods on stripe customer object.

correct me if I am wrong.

gilded shadow
#

Sort of. What are you trying to do, exactly?

#

Or, rather, what isn't working like you expect it to?

pastel yew
#

I recently came across VTS, and started to know that the processing fee for card payments using VTS is much less than on Stripe. I am trying to understand how VTS tokenization works and see if Stripe supports VTS or any such tokenization, so we could reduce our processing fee per transaction.

gilded shadow
#

We provide tokenization via Stripe.js and our Elements, so that's what we recommend using.

pastel yew
gilded shadow
#

That would be something like a payment method pm_123 or a card object card_234 etc

pastel yew
#

hmm, pm_123 (payment_menthod ID) is what I excepted the token to be, but can you explain what card_123 is?

gilded shadow
pastel yew
#

👍 , can I know if using stored payment-methods on the customer has cost benefits on processing fee.

And also will there be any fees for saving or editing payment-methods on customer objects.