#mrYi-auth
molten tendon
Hi there!
To clarify your question, you would like to restrict permissions in API calls for specific users?
sterile depot
hello，That is, the authorization is an independent act at the same time and the payment is not made at the same time
molten tendon
Yes! Thank you for your clarification 🙇
If you please take a look at: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
This is the guide I recommend 🙂
There are code examples to show you how to:
- Authorise the payment
- and later on capture the payment
sterile depot
Okay, let me take a look first.
molten tendon
Sure thing! Please let me know if you have any questions.
sterile depot
Does this API also do not collect payment first, and then collect payment from customers after a certain period?
molten tendon
Yes, SetupIntent is also designed to setup future payments.
The difference is, SetupIntent validates and attach card to the Customer object, where this payment method can be reused for future payments.
Where as the previous scenario of authorise and capture later, requires a hold on the fund on the customer's card (this will show up on the customer's statement), and this fund can only hold up to 7 days, any payment capture attempt after this will fail.
sterile depot
“Set up future card payments”
Is there also a capital and period limit? I don't seem to see the relevant description in the documentation?
molten tendon
Regarding the capital limit, that depends on the type of your account, our team is not familiar with this area, if you would like to learn more, I suggest reaching out to https://support.stripe.com for more information, and discuss with them your needs.
As for the period limit, not that I know of.
As long as the PaymentMethod object is attached to the Customer object, there is no expiry (unless the card itself has expired) for how long it can be used.
Hope this helps 🙂