Physical Card Program

Setup

Physical cards require material selection and design reviews with Rize and Rize's card printer. Please work with your implementation manager to supply the correctly configured card art requirements.

Requests

Physical cards can be requested after the Customer is in a status of active. POST requests to the /debit_cards endpoint will initiate a request to the Rize card printer with the designated physical card art. Rize will return a card UID. The type value assigned to the card is physical and ready_to_use will be false.

A physical card transitions 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 a few moments after this status is reached.
  3. printing_physical_card - The physical card is being produced. This status applies only to new physical cards; the corresponding status for replacement cards is printing_physical_card_replacement.
  4. shipped - The card has been shipped. This status applies only to new physical cards; the corresponding status for replacement cards is card_replacement_shipped.
  5. usable_without_pin - The card moves to this status after the card is activated via the PUT /debit_cards/{uid}/activate endpoint.
  6. normal - The card moves to this status after a PIN is set. At this point the card is available for PIN-required transactions.

Activation

Customer must supply the last 4 digits, expiration, and CVV in a specified format. See the Activate a Debit Card endpoint for activation details. After the card is activated, it can be used in online and card-present transactions that do not require a PIN.

PIN Set

To enable PIN required transactions, Customer must set their PIN. See the Get Debit Card PIN Token endpoint for debit card PIN set. Refer to the Guidance on PIN Set section for debit card PIN set.

Mobile Wallets

A debit card of type = physical can be added to a mobile wallet and used for payments via a mobile wallet application (i.e. Apple Pay, Google Pay, Samsung Pay). The mobile wallet will allow transactions depending on the status of the card. If the card is in a status of usable_without_pin, the mobile wallet will only support transactions that do not require a PIN.

  • If the card is in a status of normal, the mobile wallet will support transactions that require a PIN.
  • If a card is reissued, it must be re-added to the mobile wallet with the updated card details. For details on how to enable cards on a mobile wallet, please work with your Rize implementation manager.

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

Physical cards can be reissued with the reasons of Damaged, Lost, or Stolen.

The following definitions apply to the reissue reasons:

  1. damaged - A card reissued due to being damaged indicates that the physical card has been altered.
  2. lost - The customer loses or inadvertently shares the physical card details and requires a new card.
  3. stolen - The customer's physical card was stolen or notices transactions that they did not initiate.

A new physical card will be printed and issued to the Customer. See the endpoint reference here for how to reissue a card.

Damaged Physical Cards

When a physical card is reissued for a reason of Damaged, the existing card remains active for all card transactions.

Rize does not create a new card record for cards reissued as Damaged. The existing UID will persist while a replacement card is printed and shipped. See a sample GET /debit_cards request below for a debit card after being reported Damaged. The ready_to_use value remains true as the replacement card is printed and shipped to the Customer.

{
    "total_count": 1,
    "count": 1,
    "limit": -1,
    "offset": 0,
    "data": [
        {
            "uid": "hmWFH7qUghTa39Zt",
            "external_uid": null,
            "customer_uid": "ioFy9vFnHL6bjCg8",
            "pool_uid": "tfQRNhtunfhhBLWJ",
            "synthetic_account_uid": "u5o76Vya3sxe7R6s",
            "custodial_account_uid": "dmmpgG4rfjQGJCCt",
            "card_last_four_digits": "9133",
            "status": "printing_physical_card_replacement",
            "type": "physical",
            "ready_to_use": true,
            "issued_on": null,
            "closed_at": null,
            "locked_at": null,
            "lock_reason": null
        }
    ]
}

*Note: If a Customer had set their PIN prior to reporting the card as Damaged, the PIN will persist to the new card. PIN set is not required to enable the new card for PIN required transactions.

A Damaged card transitions from the statuses of:

  1. damaged - Card transitions to this status after it is reported as Damaged.
  2. printing_physical_card_replacement - Card transitions to this status after the card printer receives the request to print a new card.
  3. card_replacement_shipped - Card transitions to this status after the new card is shipped.
  4. normal - If the Customer had set their PIN previously, the card transitions to the normal status after the Customer activates the new card.
  5. usable_without_pin - If the Customer had not set their PIN previously, the card transitions to this status after the customer activates the new card.

The replacement card will have the same PAN with an updated CVV and expiration.

Lost or Stolen Physical Cards

When a physical card is reissued for a reason of Lost or Stolen, the existing card is inactivated immediately and cannot be used in future card transactions. Rize will supply a new card UID for the replacement card. The lost/stolen card record is available from the API and persists in a status of Lost or Stolen for reference. After a card is reported as Lost or Stolen, the new debit card transitions through statuses similar to a new card request:

  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 a few moments after this status is reached.
  2. printing_physical_card_replacement- The physical card is being produced. This status applies only to replacement physical cards with the same PAN; the corresponding status for new cards is printing_physical_card.
  3. card_replacement_shipped - The card has been shipped. This status applies only to replacement physical cards with the same PAN; the corresponding status for new cards is shipped.
  4. usable_without_pin - The card moves to this status after the card is activated through PUT /debit_cards/{uid}/activate endpoint.
  5. normal - The card moves to this status after a PIN is set for the first time. At this point the card is available for PIN-required transactions.