The Super Wallet APIs enable you to securely store customer payment cards, generate reusable payment tokens, and perform one-click or recurring charges without requiring customers to re-enter their card details.
This feature is designed for merchants who want to support:
-
Card-on-file payments
-
Tokenised transactions
-
Subscriptions and recurring billing
-
Faster repeat checkouts
-
Secure customer payment profiles
Super Wallet handles sensitive card data securely and returns tokens that can be safely stored and used for future charges.
Start Here
Run all Super Wallet requests in Postman and explore payloads, responses, and example flows.
Super Wallet Workflow
Follow this step-by-step workflow to onboard customers into Super Wallet, save payment methods, generate subscription tokens, charge stored cards, retrieve transactions, and manage card lifecycle operations using the DPO Pay v6 API.
What you can do with Super Wallet
Using the Super Wallet APIs, you can:
-
Create customer wallet accounts
-
Add and delete cards linked to a customer
-
Generate charge tokens for stored cards
-
Retrieve subscription tokens
-
Charge customers using tokens (including recurring charges)
-
Pull account details
-
Retrieve transaction history
Common use cases
-
Saving a customer’s card for future purchases
-
Enabling one-click checkout
-
Implementing subscription billing
-
Charging customers on a schedule
-
Reducing PCI scope by using tokenised payments
-
Managing customer payment profiles programmatically
Typical flow
A common Super Wallet integration follows this pattern:
-
Create Account – create a wallet profile for the customer
-
Add Card – securely store the customer’s card
-
Generate Token – obtain a charge or subscription token
-
Charge Token – process payments using the stored token
-
Manage Wallet – retrieve transactions or remove cards when required
flowchart TD
A[Start] --> B[Create account]
B --> C[Add card]
C --> D{Token needed}
D --> E[Create charge token]
D --> F[Create subscription token]
E --> G[Charge token]
F --> H[Charge token recurrent]
G --> I[Get transactions]
H --> I
I --> J{Manage wallet}
J --> K[Pull account]
J --> L[Delete card]
J --> C
K --> M[End]
L --> M
Security note (optional callout)
Card details are never reused directly after storage. All future transactions are performed using tokens, reducing exposure to sensitive data and improving compliance with security standards.
If you’d like, I can also provide:
-
A short 1–2 sentence description version (like you used for xPay), or
-
A “Before you begin” section (auth requirements, PCI notes, prerequisites), or
-
A small diagram / flow outline for the wallet lifecycle.

