#majo-authorize

1 messages · Page 1 of 1 (latest)

lethal current
#

heya @limpid copper , can you share more about your use case?

limpid copper
#

Hi @lethal current , our case : we need to allow customer to charge his credit(by paying with card), most of the customers will refill his credit with small amount - 1€, 0.50€... This is not good, because we have a lot of small transactions.
Idea is to preauthorize this small amounts(so we will know that user has required amount of money on his card) and charge him once when he finishes/charge him once in a month(so preauthorizations will increase)

#

Is it possible to do so?

lethal current
#

authorized funds will only be held for 7 days and you can only perform one capture on an authorized payment. If you partially capture a payment, you can’t perform another capture for the difference.

You could cancel the authorized amount and send a new request to authorize the new/same amount after 7 days but it just doesn't seem like the ideal solution to me.

It feels like a usage based subscription may fit your business model better : https://stripe.com/docs/products-prices/pricing-models#usage-based-pricing

limpid copper
#

Most important thing is to be sure, that user has required amount of money available

#

You're probably right, that usage based priicing fits our needs, but I'm missing that confident, that user will have "money to pay" at the end of the month

lethal current
#

If you want to go with authorization, only possible way i can think of is to create an authorization for the new amount before the old authorization is about to expire. But even then, you would potentially face the issue of the user's card not having sufficient funds

#

you could also consider a "wallet" which the user tops up a certain amount

limpid copper
#

We have a wallet in our app 🙂 Thing is, that users sends small amount of moeny to it, but many times - they won't send 100€ to wallet to increase a balance in wallet, but they send 1€ many times(when they spend it, they send another 1€ and so on)...

lethal current
#

you could limit the top up to a min amount?

limpid copper
limpid copper
lethal current
#

then it seems the most viable idea is to auth, create a new auth before the old one expires, and cancel the old auth.

#

yep

limpid copper
#

Great... And when he finishes spending his credit payment will "go live" so real money will be charged from card(so there will be only one live transaction)

#

Great. Thank you very much for your help

#

Last question - is there a pricing for preauthorization or it's free and we will pay only for live payment?

lethal current
#

there's no pricing for preauth

limpid copper
#

Great, thank you

#

Is there any option how to export this chat?(send it to email or so)

lethal current
#

unfortunately no, you can probably copy and paste it into your own document though

limpid copper
#

yeah, I thought so, so I copied to txt 🙂

limpid copper
#

@lethal current I have another question if I may - when I preauthorize payment and then I cancel it(and make a new preauthorization) is there any time limit for how long it takes to return that preauthorized amount to card?

#

or in other words - how long it takes ito release preauthorized money f I cancel preauthorization and if there is difference if user use Apple Pay/Google Pay/Payment Card

wide laurel
#

Hi! I'm taking over alex-stripe. Sorry for the delay.

#

This delay completely depends on the bank, so we don't know.

limpid copper
#

Oh, okay