Card
A card is a Helix-issued debit card linked to one or more savings or checking accounts. To correlate a specific card in Helix to a specific card record in your system, store your system's unique key in the tag
property, or store Helix's cardId
in your system.
Creating a physical card and shipping it to the customer is a multi-day process. The standard production workflow is:
- Call /card/initiate
- Wait for physical card to be printed and shipped to the customer.
- Prompt the customer (via your site/app) to activate their card - or in Helix terms, "verify" the card via /card/verify
- Customer can now use the card
NoteWhen reissuing a card in the sandbox environment, if a card is currently in
PendingVerification
orReissuePendingVerification
status, the new status will beReissuePendingVerification
. Otherwise, the new status will beVerified
.
Take me to the Card Endpoint Reference
card Object
Represents a single card. A single customer can have multiple cards. A single card can be tied to multiple accounts (4 checking, and 4 savings). A single account can be tied to multiple cards.
Property | Data Type (length) | Description |
---|---|---|
| array | An array of partially populated account objects. Properties that are populated on each account object:
|
| datetime | Date the card Format: yyyy-MM-ddT00:00:00.000+00:00
Example: |
| integer | Specifies which a card will be assigned to. Defaults to first bin created for your . |
| string (6) | Optional. Identifier used uniquely by various card production facilities for mapping card configurations. |
| string (16) | Optional. Identifier used uniquely by various card production facilities for mapping card configurations. |
| integer | The unique identifier of the customer who typically has the card in their possession. If 0 or null, defaults to value in |
| string (50) | Optional. Identifier used uniquely by various card production facilities for mapping card configurations. |
| integer | Helix-assigned unique ID for the card |
| datetime | Date card was last used for a card transaction. Default value is
|
| string | The masked value of the PAN (Primary Account Number) for the card.
Example:
|
| datetime | Date the card was created Format: yyyy-MM-ddT00:00:00.000+00:00
Example: |
| integer | The Helix-assigned unique ID for the customer who actually created the card (the customer who called ). This customer must have |
| datetime | Date the card |
| array | Optional array of if the card has been provisioned into a Digital Wallet |
| integer | Month the card expired or will expire
Virtual cards have a maximum expiration month of |
| integer | 4-digit year the card expired or will expire
Virtual cards have a maximum expiration year of |
| datetime | Date the card Format: yyyy-MM-ddT00:00:00.000+00:00
Example: |
| string (64) | The cardholder's first name as it should appear on the card verbatim. See /card/initiate for restrictions. See card name allowed special characters for more details |
| boolean |
or and isCreateDualIssuanceSinglePAN = |
| boolean |
endpoint with |
| boolean |
|
| datetime | Date when the object was last altered in any way. Note: This property updates when a card is or . |
| string (128) | The cardholder's last name as it should appear on the card verbatim. See /card/initiate for restrictions. See card name allowed special characters for more details |
| array | Reserved for future use |
| enum | The reason the lock was applied to the card Valid values include:
|
| enum | The type of lock applied to the card. Possible values:
|
| string (64) | The cardholder's middle name as it should appear on the card verbatim. See /card/initiate for restrictions. See card name allowed special characters for more details |
| string | The name of the cardholder as it appears on the card |
| string | The new 4-digit (0-9 only) value to assign to the PIN. Must be encrypted using this public key and converted to base64 per RFC 4648. For example, if the new PIN is
This value will never be returned from the API.
|
| string (50) | A display-friendly name that applies to the card |
| string (18) | Optional. Identifier used uniquely by various card production facilities for mapping card configurations. |
| string (21) | Name customer prefers to use and referred to when being addressed. Customer requested |
| integer | The with |
| string (3) | Optional. Accepts any alphanumeric characters. Valid values are defined by Visa DPS at the time of creation. |
| datetime | Date the card was set to a Reissued status due to calling |
| string | Card renewal override set by client |
| string (20) | Card renewal override reason set by client. |
| integer | Helix-assigned unique ID for the customer requesting to create a card for a business cardholder |
| datetime | Date the request to create the card was sent to the card provider Format: yyyy-MM-ddT00:00:00.000+00:00
Example: |
| enum | Card status Valid values include:
|
| string (50) | A caller-specified, unique identifier for this card. Must be unique within your program. |
| enum | Possible values:
|
| string | Possible values:
|
| datetime | Date the card Format: yyyy-MM-ddT00:00:00.000+00:00
Example: |
Updated 12 days ago