#afenster
1 messages · Page 1 of 1 (latest)
Hi, are you offering a free trial? Is this for subscriptions? What is the use case?
I'm new to the company. I believe the use case is the person calls to make a reservation. We enter the card into the Payment Element with no charge. Later when the person shows up or cancels, we charge the appropriate amount.
So we would be able to charge the person's card ending in XXXX.
I see, what integration are you using currently? Checkout? Elements?
We are migrating from the Charge system to PaymentIntents. In the current system it looks like we do a $0 authorize, get a token and do not capture. (If I understand it correctly.) I am looking for the PaymentIntent equivalent.
In the new system we have a Payment Element used when people call and tell us their number. We are adding Stripe Terminals for in-person payments.
Application is a React UI and a .Net backend.
I'd encourage you to take a look at out Setup Intents: https://stripe.com/docs/payments/save-and-reuse in this case.
This lets you collect a payment method without making a payment first and then charge them in the future.
OK, I'll look it over. I didn't see that.
Would making a $0 payment with a PaymentIntent have the same effect? Would a $0 charge show up on the customer's statement?
Because I've already got all the code working.
That is, right now I can take a $10 deposit and then charge the rest later. So would taking a $0 deposit be the same thing?
That is not going to work I'm afraid.
OK. When my boss asks why not, what do I say? You can't confirm a $0 payment?
I was looking for our document but the reason is that we have a minimum requirement: https://stripe.com/docs/currencies#minimum-and-maximum-charge-amounts
If you pass $0, it would throw an error.
I remember that now. That's right - a 50 cent minimum in the US.
That's all the questions I have. Thank you for your assistance. 🙂
Happy to help!
Sorry, I'm back.
It looks like in the existing system they authorize $1 and then don't capture it. Is that something I could do with PaymentIntents? Or is that a bad idea?
No worries, that is against card network policies and that is not recommended at all.
OK, thanks again.
Sure!