Implementation steps
Implementation steps for enabling digital wallets
Follow these steps to enable digital wallets in your card program.
1. Establish a BIN or BIN range
Secure a Bank Identification Number (BIN) or a specific rate within a BIN from your sponsor bank. Work with your program manager to reserve the BIN or range.
This BIN provides the foundation for all digital wallet settings. The network project for tokenization ties directly to it. It covers Apple Pay, Google Pay, and Samsung Pay support.
To support additional wallets, contact your Cross River Relationship Manager
2. Design and configure card art
Design the visual asset that represents your card in wallets. Digital wallet card art differs from physical card printing. It must meet strict digital specifications.
Card art specs (general standard)
Asset | Size | Format | Notes |
|---|---|---|---|
Card art | ~1536 x 969 px | PNG | No rounded corners; wallets add them automatically; under 3 MB |
Logo | ~1372 x 283 px | PNG | Transparent background |
Icon | ~100 x 100 px | PNG | Used for app and notification icons |
Check specific network specs for exact requirements.
Metadata
Provide these additional details with your card art:
- Colors: Define Hex/RGB codes for background, PAN text, and label text. These ensure readability in the wallet UI.
- Terms and conditions: A URL or text file with the cardholder agreement. This appears during the "Add to Wallet" flow.
- Contact info: Customer service email, phone number, and website URL.
3. Set up the network project
Your program manager or processor opens a "Digital Enablement" project. They open it with the card networks (Visa or Mastercard) on your behalf.
Action: Submit your card art assets and configuration metadata. Send these to your implementation manager.
Next step: The network creates a Token Service Provider (TSP) configuration. This links your BIN to the digital wallet ecosystem (such as Apple, Google, and Samsung).
4. Test and whitelist
Validate the tokenization flow before going live. Use test cards for all scenarios.
Whitelisting
Your processor allows specific test PANs or ranges. Cards not on the list fail during this phase.
Scenarios to test
- Successful provisioning (green path)
- Declined provisioning (e.g., locked card)
- Token lifecycle events (suspend and resume from your app)
- Transaction processing with provisioned wallets
5. Get approvals and launch
After testing, get formal approvals to activate your program.
Network approval
Your processor submits "Financial Institution" forms. These forms confirm the setup is valid and tested.
Wallet provider approval
The card networks forward your configuration to Apple, Google, and Samsung. This includes your art, terms, and app info.
Outcome
Once the wallet providers approve, they switch on the BIN in their production systems.
Go-live
Your implementation manager assists to remove whitelist restrictions. All cardholders can then add cards to their digital wallets.