Réda

[noble topaz]

Hi there

So you are trying to set up PaymentMethods to be charged in the future when your customer is not online, correct?

[tight delta]

hmm, kind of that yes. In fact : I create a Customer Object, then this Customer attach a valid PaymentMethod Object to this account. By signing up in my platform, the customer know that he'll be charged for [for example] 1$ every time an "activation" is made by a user in the mobile app.

[noble topaz]

So you want to use a SetupIntent then when you collect the PaymentMethod

[tight delta]

I want to automatize my invoicing and create a Charge Object for each Customer (monthly), for an amount that I'll get from my server. So the amount is variable a month to another,.

[noble topaz]

That will handle setting it up properly for future use

See: https://stripe.com/docs/payments/save-and-reuse?platform=web

[tight delta]

ok thank i take a look at this

[tight delta]

Just to recap for my use case.

1. I create a Customer object
2. I create a Setup Intent Object associated with the Customer, which will allow me to invoice it later (when I know the amount)
3. When I have the final amount, I invoice the customer by creating a PaymentIntent object, passing the customerId, the payment method id, the value true to off-session and the value true to confirm.

and so there the user has already given me his authorization when creating the setup intent and therefore there will be no other validations necessary suddenly?

[agile pumice]

Correct. The Setup Intent sets the payment method up for future usage without additional authorization.