Apple Wallet and Google Wallet use cases
A loyalty card, a train ticket, a boarding pass or a hotel booking: the mechanics never change. You create a template once, you send a pass to each customer, then you keep it alive (updates, notifications, redemption).
Each page below starts from a real industry. It walks through the customer journey, the API calls in order and the traps to avoid. Pick yours, or the closest one.
Try our live demosLoyalty and membership cards, coupon, ticket, transit pass, booking: create a real pass and get it on your phone.
How to read a use case
Every page follows the same structure:
-
The pitch: the business problem and what the pass does on the customer's phone.
-
The customer journey: a diagram showing who calls whom, from your system to the customer's wallet.
-
The integration workflow: numbered steps. Each step shows who acts and which endpoints are called.
Badge Who acts Back-office You, in the eldo wallet back-office. No code. Your server Your CRM, POS, ticketing system or back end calls the API. eldo wallet The platform generates, sends or updates the passes. End customer Your customer adds, shows or receives the pass. -
Best practices: what works in production, and what breaks.
-
Go further: related knowledge base articles and endpoints.
Start with the quickstart and authentication. Then read templates and passes: it is the idea the whole API is built on.