#BilalSaeedAlam

1 messages · Page 1 of 1 (latest)

arctic basaltBOT
timid peak
#

What's your question?

plush spire
timid peak
#

Ah, so once the Setup Intent is confirmed and the Payment Method is created, you can usually just pass the Payment Method ID to create payments via a Payment Intent, Invoice, or Subscription

plush spire
#

Okay so i can store this id into database, so i will be easy for charging future payments.

timid peak
#

Exactly!

plush spire
#

Perfect thank you man.

#

Can you tell me one thing jsut?

#

I will charge payment through backend like i am using Node JS, so when i need to charge any customer i will use Payment Intent for that?

timid peak
#

yup! You create a Payment Intent on the backend and you can also confirm it on the backend, so you don't have to do any client-side confirmations if you don't want to. There are client-side options too though

#

It all depends on what you want to do. There are a lot of options

plush spire
#

Perfect, so it will be same for Card options like i am using Stripe Card Element, which is taking card number, cvv, and expiry date and in return creating a token id. I am sending that token to backend and generate a customer id and storing that id into database. Just like the above discussion, can we charge customer in future with this customer id? Like in the backend i will use customer id to get token again and on the base of token i will charge customer?

timid peak
#

As long as you have confirmed the card and attached it to the Customer, you can reuse that Payment Method. So, if you're using the Card Element, then you'll confirm the card on the client-side. Once it is confirmed, you can attach it to the customer and either pass the Customer ID or the Payment Method ID when you create future payments

plush spire
#

Perfect man you helped me a-lot thank you so much.