Skip to main content
All CollectionsDriver support centerGuest Charging Using QR Code Scanning (Scan to Charge)
Understanding Stripe Payment Hold for Improved Transaction Security
Understanding Stripe Payment Hold for Improved Transaction Security

Learn how Stripe payment hold improves transaction security for Scan to Charge, reducing failed payment risks.

Lizzie Karmi avatar
Written by Lizzie Karmi
Updated yesterday

Stripe payment hold enhances transaction security for Scan to Charge transactions, reducing the risk of revenue loss from failed payments.

How Stripe Payment Hold Works

The Stripe payment hold feature pre-authorizes and holds a fixed amount for Scan to Charge transactions ($50/€50/£50, etc). This process secures funds before charging begins, minimizing the risk of failed payments, especially from guest users.

Benefits of Stripe Payment Hold

Reduced Revenue Loss

By pre-authorizing funds, the risk of failed transactions is significantly reduced, protecting operators from potential revenue loss.

Enhanced Security for Guest Transactions

This feature is particularly beneficial for guest users, where the risk of payment failure may be higher due to lack of account history.

Flexible Charging

Once charging is complete, the actual charge is applied based on the amount of energy used. Any remaining funds from the pre-authorized amount are then released back to the user's account.

How the Process Works

  1. Pre-authorization: When a user initiates a Scan to Charge transaction, Stripe pre-authorizes the fixed amount.

  2. Charging: The charging session proceeds as normal.

  3. Final Charge: Upon completion, the actual amount used is charged to the user's payment method.

  4. Fund Release: Any difference between the pre-authorized amount and the actual charge is released back to the user.

By implementing this Stripe payment hold feature, operators can ensure more secure transactions and reduce the risk of revenue loss from failed payments, particularly in guest-user scenarios.

Did this answer your question?