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