Charge Assist supports a retry mechanism for failed payments in Stripe. Usually a payment fails because of insufficient balance of the user.
How it works?
When the session starts with an ad hoc payment method from Stripe:
- App takes a pre-authorization, which can be defined by the CPO or it takes the default value of 20 in Charge Assist App.
- In case pre-authorization failed, session will not be started
- In case pre-authorization was successful, session will start
- Start session request will be sent to Charge Station
- In case charge station did not respond OR rejects the session, pre-auth will be returned instantly. It depends per bank how long it will take before the money is released for the user.
- After stopping a session, a payment request will be sent to Stripe
- In case the total costs are less than the pre-authorization, the money will be deducted from the pre-authorization amount and the remainder will be given back to the user
- In case the total costs are more than the pre-authorization (for example €22.50 while €20,- was reserved), the pre-authorization will be refunded first, and a payment attempt of €22.50 will be made. This is the scenario where failed payments mainly are happening.
- For failed payments, a retry mechanism is in place:
- Runs automatically at night
- Tries three times (nights) in a row to get the full payment
- After, no automated retries but manual retry still possible via our Support department.
F.A.Q.
How to change the pre authorization value for my chargers, when ad-hoc charging is being used through Charge Assist app?
The pre-auth can be defined per CPO. By default, 20 will be considered. If needed to change this, consult with your CSM and he will be able to implement it.