#atharv.bagade
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- atharv.bagade, 19 hours ago, 13 messages
Hi, let me help you with this.
You can collect the Payment Method with a SetupIntent and charge it later.
Would this save the card against a user?
We want to make it optional for the user to save the card for future transactions.
It's attached to a Customer object.
So we would have to manually remove it after the payment intent is completed?
Why would you want to remove it?
Alternatively you could put a hold on the Payment Method and capture it later. But the amount needs to be less or equal to the hold. This is not a Terminal article, but explains the logic: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
We want to make it optional for the user to save the card for future use.
We just need a payment method to unblock him
I think this is only available in the US for now.
What do you mean by "unblock him" exactly?
Its a pick and go experince where he just comes, taps his card for us to have a payment method, picks up what he needs and then we charge him after some time based on whatever he has picked.
So all we need to do is hold the payment method till the transaction is completed.
As I mentioned earlier, you have 2 options:
- Save PM for future usage (they save the card and then you charge them for the arbitrary amount without their presence/off-session)
- Place a hold on the PM, but it requires an upper limit amount.
Got it. Thank you. Have a great day.