Cards
The Card resource represents a card under an account.
Unit provides a cross-platform suite of flexible and customizable white-label UI components, including a card component. You may embed the card component into your app to shorten your time to market and deliver a highly optimized experience to your end customer with minimal engineering investment.
Unit enables you to programmatically review card Authorization Requests when they are made, and decide whether to approve the purchase. This capability gives complete control and visibility into card use.
Card Resource Types
There are multiple types of card resources on Unit, each solves for specific use cases. The table below outlines the different types and use cases.
| Type | Details |
|---|---|
| IndividualVirtualDebitCard | A virtual debit card belonging to an Individual customer, including sole proprietors. The details of the card holder (name, email, phone number etc.) will be the individual customer's details. |
| IndividualDebitCard | A physical debit card belonging to an Individual customer, including sole proprietors. The details of the card holder (name, email, phone number etc.) will be the individual customer's details and by default the card will be shipped to the customer's address. |
| BusinessVirtualDebitCard | A virtual debit card belonging to a Business customer. The card holder may be any person associated with the business. The details of the card holder (name, email, phone number etc.) will be provided as part of the card creation request. In order to create the customer token that is needed to reveal the card information, the card holder must be the business contact or an (authorized user)[/api/customers/#authorized-users]. |
| BusinessDebitCard | A physical debit card belonging to a Business customer. The card holder may be any person associated with the business. The details of the card holder (name, email, phone number etc.) and shipping address will be provided as part of the card creation request. |
| BusinessVirtualCreditCard | A virtual credit card belonging to a Business customer. The card holder may be any person associated with the business. The details of the card holder (name, email, phone number etc.) will be provided as part of the card creation request. In order to create the customer token that is needed to reveal the card information, the card holder must be the business contact or an authorized user. |
| BusinessCreditCard | A physical credit card belonging to a Business customer. The card holder may be any person associated with the business. The details of the card holder (name, email, phone number etc.) and shipping address will be provided as part of the card creation request. |
Cards issued to sole proprietors are business cards for all intents and purposes (BIN, interchange etc.)
Card Statuses
Cards have a Status Property, which represent their current status and determines what actions can or can't be completed using the card.
| Status | Description | Comments |
|---|---|---|
| Inactive | The Card has not been activated by the Customer | Cards can be activated using the Activate card or by calling a the toll-free number printed on the card. Virtual cards do not require activation. |
| Active | The Card has been activated and can be used regularly | |
| Stolen | The Card has been reported stolen by the Customer | A stolen card cannot be reopened. |
| Lost | The Card has been reported lost by the customer | A lost card cannot be reopened. |
| Frozen | The Card has been frozen | |
| ClosedByCustomer | The Card has been closed by the Customer | A closed card cannot be reopened. |
| SuspectedFraud | The Card has been flagged due to fraud suspicion | Cards are defined as "SuspectedFraud" by the card network (e.g. Visa). The network will reach out to the client to confirm recent transactions that were marked as potentially fraudulent and reactivate the card if the transactions are confirmed as not fraudulent. If the transactions are marked as fraudulent or if the client does not respond to the card network, the card will remain in SuspectedFraud status and cannot be used. |
Automated Cards Reissue on Expiry
One month before the card (physical or virtual) is due to expire the cards network and card printer (for physical cards) will automatically re-issue a new card with the same card number, the new expiration date and the new CVV:
- The
card.reissuingwebhook event will be raised - The
Cardresource will include an attributenextExpirationDatewith the value of the new card's expiration date
Exclusions
Cards are excluded from automatic re-reissue if one of the below conditions apply:
- The status of the card is not
Active(i.e.,Stolen,Lost,Frozen,ClosedByCustomer,SuspectedFraud) - The card has not been activated by the customer (i.e., status
Inactive) - There is no card activity in the last 6 months - this includes all card related transactions
New cards validity
The new cards are issued with 3 year validity period.
Cards activation
New virtual cards are issued ready to use instantly and do not require prior activation.
New physical cards require to be activated by the customer before the first use. Activation of the new card blocks the old card from being used further. Once the new card is activated a card.activated webhook event will be raised
Cards Expiry
If the new card is not activated by the expiration date (last day of the month), the old card will become Inactive and a card.statusChanged webhook event will be triggered.
If the new card is activated, the expiryDate attribute of the Card is set to new expiration date (i.e. copied from nextExpirationDate).