Understanding Digital Wallet Payments via Stripe

As a store owner, you will notice that payments made via Apple Pay or Google Pay (Digital Wallets) behave differently in your BRM Back Office compared to traditional physical credit cards. Understanding these differences will help you manage customer expectations and your store’s data.

Why "Saved Cards" don't work with Wallets

To provide your customers with a flexible checkout experience, our system supports both traditional Card Payments and Digital Wallets via Stripe.One of the most frequent questions we receive is why a store owner cannot "save" a customer's card for later use when they pay with a mobile device.

The Single-Use Security Model: When a customer taps their phone at your counter or uses a mobile wallet online, they aren't actually giving you their real credit card number. Instead, the wallet provider (Apple/Google) creates a unique, one-time security token specifically for that single transaction.

• Standard Cards: These provide a "persistent" card number. Because the number stays the same, our system can store a secure "key" to that card, allowing you to charge it again for damages, extensions, or recurring fees. 
• Digital Wallets: Because the "card number" used for the transaction is essentially a "ghost" number that expires immediately after use, it is not a "set card." There is no permanent data for the BRM Back Office to store. 

You can still issue a refund to a wallet via the Stripe Dashboard, however the reservation on Bike Rental Manager will not update automatically and a workaround is a required. 

For more information please see :  How to Process a Wallet Refund via Stripe (Manual Workflow)