Virtual Card Program

Requests

A virtual card is available to Customers as part of account opening. After the customer is in a status of active, a card record will be created and available from the /debit_cards endpoint by passing in the customer_uid as a parameter. The type value assigned to the card is virtual and ready_to_use will be TRUE.

The card will move through the following statuses:

  1. queued - This is the first state a debit card will enter. This status indicates that a create request has been submitted successfully from the Client and is queued to be issued. A debit card will be in this state for a very short (less than one second) period of time.
  2. issued - This is the second state a requested debit card will enter. An Issued debit card has been assigned a PIN, PAN, CVV, and expiration and these details are submitted to a card printer for physical card production. The last 4 digits of the card are available once this status is reached.
  3. usable_without_pin - The card has been activated but the PIN has not been set.

The card will transition to the usable_without_pin status shortly after being created. Once the card status is in usable_without_pin, it can immediately be used in online and card-not-present transactions.

The following is a sample response of a GET request for a debit card in a virtual card program:

{
            "uid": "CTQN5RavQ4gYcXZe",
            "external_uid": null,
            "customer_uid": "PDS4deLJPJCKJTnf",
            "pool_uid": "g177aFUjmQR747N2",
            "synthetic_account_uid": "hpiNhTdW2Y7YFPXL",
            "custodial_account_uid": "V6MRN7bRGRr1ay9a",
            "card_last_four_digits": "2470",
            "status": "usable_without_pin",
            "type": "virtual",
            "ready_to_use": true,
            "issued_on": null,
            "closed_at": null,
            "locked_at": null,
            "lock_reason": null
        }

To view the virtual card image, do the following:

  1. Post to the GET Debit Card Access Token endpoint
  2. Supply the token in the GET Virtual Card Image request

The card image will be customized for the Customer with the Customer's name, card PAN, CVV, and expiration date overlaid on the card design supplied during implementation. The default sandbox program configuration has a virtual card available.

Example card image:

Activation

Virtual cards are ready for card-not-present transactions (i.e. online purchases) and do not need to be activated. A PIN cannot be set for a virtual card. Virtual cards will not work in PIN-required transactions.

Storage

Virtual cards contain PCI sensitive information. The card image and card details can not be stored on your application. Each time the card image needs to be rendered, please request a new card image token and follow the steps listed above for viewing the virtual card image. The token is valid for five minutes from the time of the request. The same token can be used 3 times over a 5-minute period before another token must be requested.

Mobile Wallets

A debit card of type = virtual can be added to a mobile wallet and used for payments via a mobile wallet application (i.e. Apple Pay, Google Pay, Samsung Pay). As stated above, virtual cards can be used for card-not-present transactions (i.e. online purchases), a PIN cannot be set for a virtual card, and virtual cards will not work in PIN-required transactions. These remain true for the virtual card in a mobile wallet as well.

Mobile wallets must be configured for your Program before they are available. Please work with your implementation manager to configure mobile wallets for your Program.

Reissuance

Virtual cards can be reissued with the reasons of Lost or Stolen.

  1. lost - The customer loses the device or access to the application with the virtual card image on it. The customer inadvertently shares the card image and requires a new card.
  2. stolen - The customer's device was stolen or notices transactions that they did not initiate.

Virtual cards cannot be reissued with the reason of Damaged.

Lost or Stolen Virtual Cards

When a card in a virtual card Program is reissued with a reason of Lost or Stolen, the existing card details are no longer valid and will not work in future transactions. The card reported Lost or Stolen will persist in a status of lost or stolen and ready_to_use will be set to false.

After reporting the card Lost or Stolen, the customer can immediately request a new virtual card image. The new card UID will follow the statuses of:

  1. issued - An Issued debit card has been assigned a PIN, PAN, CVV, and expiration and these details are submitted to a card printer for physical card production. The last 4 digits of the card are available once this status is reached.
  2. usable_without_pin - The Card has been activated but the PIN has not been set.

The reissued virtual card will have a new PAN, CVV, and expiration. This card is immediately available for card-not-present transactions (i.e. online purchases).

Rize will generate a new card UID for the replacement card. A sample API response to the GET /debit_cards endpoint below shows how Rize will respond after a virtual card is reissued with a reason of Lost.

{
   "total_coun"":2,
   "count":2,
   "limit":10,
   "offset":0,
   "data":[
      {
         "uid":"ACufBCVf3NXSmat1",
         "external_uid":null,
         "customer_uid":"Rx7uUJRrB5da1UqG",
         "pool_uid":"2Mb11wPwDhqSzG8M",
         "synthetic_account_uid":"4Rvh6bDTGmYz1YKj",
         "custodial_account_uid":"xnCEMvtdA1jAfRCS",
         "card_last_four_digits":"1423",
         "status":"usable_without_pin",
         "type":"virtual",
         "ready_to_use":true,
         "issued_on":"2022-03-29",
         "closed_at":null,
         "locked_at":null,
         "lock_reason":null
      }
{
         "uid":"KGv8airro5pG9KUd",
         "external_uid":null,
         "customer_uid":"Rx7uUJRrB5da1UqG",
         "pool_uid":"2Mb11wPwDhqSzG8M",
         "synthetic_account_uid":"4Rvh6bDTGmYz1YKj",
         "custodial_account_uid":"xnCEMvtdA1jAfRCS",
         "card_last_four_digits":"6237",
         "status":"lost",
         "type":"virtual",
         "ready_to_use":false,
         "issued_on":null,
         "closed_at":"2022-03-29T17:20:22.467Z",
         "locked_at":null,
         "lock_reason":null
      }
   ]
}