#ahsan.aasim

1 messages · Page 1 of 1 (latest)

vestal lavaBOT
charred fjord
#

Hi there, over-capture is only allowed for in-person payment (i.e., POS), not online payments.

obsidian comet
#

So, What should we do in this type of scenario?
We are developing an EV charging station solution. Here users will authorize first and after they charge their EV, we will charge their card. So, this scenario can arise.

#

@charred fjord

charred fjord
#

So you want to hold more than what the user would eventually pay, am I right?

obsidian comet
#

Let's say, to start charging there EV, our users first have to authorize their card. Let's say we pre-authorized 20$. but after they charge there EV, we found that their total bill is 25$. So, How can we increase the pre-auth amount to 25$ and then charge them? Or, what is the general practice here?

#

@charred fjord

charred fjord
#

There's no need to tag me for every message you wrote, I'll see you message and follow up accordingly

obsidian comet
#

okay thanks

charred fjord
obsidian comet
#

Should we cancel the preauthorized amount and then directly charge the amount

charred fjord
#

I'd suggest you to read through the doc that I sent earlier. It has information on how to charge a customer with a saved payment method.

obsidian comet
#

I read the doc about future payments. But we have to authorize a certain amount first. With future payments we are just storing the payment method and later using it.

charred fjord
#

OK, and I believe you know how to authorize a payment. If you don't capture the payment, Stripe will automatically release the funds to your customer after 7 days.

obsidian comet
#

Okay,
So, this is what we have to do.
first authorize an amount. then if total amount is less than or equal to auth amount, we capture the auth amount.
if its more, we just process the payment separately and release the original auth amount.

Am i right?