10 minute readDPS Payment Account Solutions supports plastic and digital card issuance. If you plan to support plastic cards issuance, you have the option of entering into your own agreement with a card vendor already certified to accept the Visa Card Vendor batch file, or you can contract with a vendor of your own choosing, in which case you must perform certification testing before beginning operations.
You can configure to override your card program’s card vendor to manage your card inventory and fulfillment processes across multiple card vendors.
You may also configure to provide the card vendor file 7 days a week or multiple card vendor filed in a day as required by your card vendor.
You can select the card designs and how the cards will be embossed for each of your card programs, or you can provide your own card stock and embossing.
A card is a type of payment instrument that enables cardholders to make in-person purchases or online/e-commerce transactions. Cards can be physical and/or digital and include the cardholder's name, card number, CVV2, and expiration date.
Digital cards are cards that can be accessed through a digital channel like a website or mobile application. Digital cards provide cardholders with instant access to their accounts and enable them to begin transacting immediately. They have no physical aspect and can be used online and in digital wallets
Physical cards are conventional plastic cards that you swipe, insert, or tap at a merchant’s card-reading device. These cards are produced at a card vendor who creates the actual card.
Digital and plastic cards can be ordered as a standalone or in tandem.
You can use the Create Card Order API to issue both digital and physical cards. A cardId, a unique identifier associated with a specific cardholder, is returned in the response.
Card Issuance is the process by which a cardholder is issued either a digital or physical card. DPS Payment Account Solutions issues cards on your behalf.
The Create a Card API allows you to issue a digital and/or plastic card, along with creating a consumer profile and underlying account. For a digital card request, a new card record is created, and the cardholder is instantly issued a card that is ready for use. The digital credentials, such as card number and expiration date, are now available to push to the cardholder’s mobile device. If a cardholder needs a CVV2 for an online transaction, use the Generate CVV2 for a Card API to provide a CVV2 to the cardholder.
For a physical card request, a new card record is created. The card credentials generated by DPS Payment Account Solutions, such as card number and expiration date, are compiled in the Card Vendor File, which DPS sends to your card vendor. The card vendor then generates the CVV values, creates a physical card, and ships it to the cardholder’s address.
With the upgrade card feature enabled, cards meeting certain usage conditions are automatically upgraded to higher card classes, generally allowing the cardholder greater flexibility in how the card can be used.
Typical examples include:
Upgraded cards get a new account number and expiration date, but they retain all account, transaction, and balance history, and the cardholder can continue to access the system as before.
Card upgrades are controlled via the card class definition—a group of features defined for a card program that define such attributes as whether cards issued by the program are personalized or non-personalized, how many reloads are permitted, and whether or not a card can be used for cash at an ATM.
The usage conditions that trigger an automatic upgrade are configured as part of the card class.
These usage conditions include:
You determine the type of card classes the program supports.
Each card class represents some combination of these attributes:
DPS recommends that clients use different BINs to distinguish between card classes.
DPS Payment Account Solutions can support replacing/reissuing expired cards.
You can configure your card program to allow cards to be reissued automatically. You determine how many months prior to the card expiration date the cards are ordered. You can also determine whether a card should be automatically reissued at expiration based upon configurable criteria options.
For cards not automatically reissued at expiration, options are available to not close the account and to reissue the card post expiration manually, or automatically upon receipt of a funding transaction to the cardholder account.
After a reissued card has been activated, the DPS will automatically decline transactions from a cardholder’s old card.
Card replacement is initiated by the cardholder.
Replacement Cards can be ordered using the Visa Developer Center (VDC) in addition to the administrative portal and white-label consumer website (if configured).
A new card number and expiration date is reissued.
Lost/stolen card replacement is supported using the Visa Developer Center (VDC).
To initiate the function, the card status must be set to lost/stolen. The lost/stolen status is then recorded in the cardholder’s profile and lost/stolen replacement order may be placed.
The CVV2 Generation Service enables Visa DPS clients to request and receive the calculated 3-digit security code CVV2 value associated with a cardholder’s account via API integration.
This feature can utilized with the CVV2 Generation Service API.
CVV2 Generation Service API key features:
The ability to use a card for a PIN-based transaction must be explicitly enabled by the you.
Start a Project
API Overview
API Reference