Customer
A customer represents a single end-user. Almost every action in Helix requires a customerId
to identify for whom the action is being performed. To correlate a customer in Helix to a user in your system, you can:
- Pass your system's unique user ID into the
tag
property during customer creation. This allows you to use your system's ID to fetch the customer's Helix data via /customer/getByTag - Capture and store the unique
customerId
returned by Helix after customer creation. You can then use /customer/Get to fetch the customer's Helix data.
Take me to the Customer Endpoint Reference
customer Object
Property | Data Type (length) | Description |
---|---|---|
accessTypeCode | deprecated | deprecated |
| array | An array of account objects owned by the customer |
| array | An array of address objects associated with the customer |
| datetime | Date the business information was attested to |
| string (50) | Name of the person attesting to the business' information |
| string (50) | Title of the person attesting to the business' information |
| datetime | Customer birth date |
| string (200) | Description of the business |
| string (300) | Legal name of the business |
| string (26) | Optional. The business name printed on the card. See card name allowed special characters for more details |
| string (100) | Url of the business |
| array | An array of card objects owned by the customer |
| datetime | Date the customer was created. Note: a customer may have been created but is not available for use, depending on the |
| enum | Accepted values vary by program. Possible values:
|
| integer | The Helix-assigned unique ID for a customer. Will be |
| string (50) | A property for holding client-defined data. There is no |
| string (50) | A property for holding client-defined data. There is no |
| string (50) | A property for holding client-defined data. There is no |
| string (50) | A property for holding client-defined data. There is no |
| string (50) | A property for holding client-defined data. There is no |
| string (200) | "DBA" or "Fictitious Business Name" of the business |
| datetime | Denotes the date the customer was reported as deceased. |
| datetime | Date the driver's license expires. |
| datetime | Date the driver's license was issued. |
| string (30) | The identifying number from a government-issued driver's license |
| string | Last 4 digits of the |
| string (2) | State from which the driver's license is issued. |
| string (255) | Customer email address |
| enum | The reason the business is exempt from Beneficial Ownership. See customer.exemptFromBeneficialOwnershipType for more details.
|
| array | An array of externalAccount objects owned by the customer |
| string (64) | First (given) name |
| string (3) | 3 character country code of the country the document was issued by. See ISO 3166-1 Country Codes |
| datetime | Expiration date of the foreign ID |
| string (30) | Unique number of the foreign ID |
| string | Masked value of |
| enum | Valid values:
|
| datetime | Date the business was originally registered |
| string (2) | 2-character state abbreviation of the state where the business was registered |
| enum | Customer's status in regards to the 'fraud' customer verification module. Possible Values:
|
| enum | Customer gender
|
| integer | Helix-assigned unique ID for the industry in which a business operates See the industryClassificationCode object for more information. |
isActive | deprecated | Use status instead |
| boolean | Indicates whether the customer is a natural person or business entity. |
| boolean | Only required when creating a new customer. Confirms that customer viewed and accepted all documents returned via the /bankDocument/list route |
| boolean | Indicates if the business is exempt from providing beneficial ownership information |
| boolean | Denotes if a customer is locked, typically caused by fraud prevention mechanisms or manual intervention via the admin console. A locked customer can not transfer any funds |
| boolean |
|
| boolean | Indicates whether the customer opted in to receiving marketing notifications from the bank. Note: customer may possibly still receive other required notifications from the bank regardless of this flag -- it depends on your program and the bank. |
| boolean | Indicates whether the customer is subject to backup withholding. Helix will withhold the appropriate |
| boolean | Indicates if the customer exempt from US taxes |
| enum | Possible values:
|
| datetime | The last time |
| enum | Customer's status in regards to the 'KYC' customer verification module. Possible Values:
|
| datetime | Timestamp for the last time any action was performed on this customer. Actions include listing, editing, archiving, |
| datetime | Date of last contact with the customer. Set via /customer/setLastContact |
| enum | Type of last contact with the customer. Set via /customer/setLastContact. Date of last contact with the customer. Set via /customer/setLastContact.
|
| datetime | Date when the object was last altered in any way |
| string (128) | Last name (surname) |
| enum | Possible values:
|
| datetime | Denotes the last time |
| string | The reason |
| string (64) | Middle name |
| enum | Customer's status in regards to the 'ofac' customer verification module. Possible Values:
|
| string (5) | Country from which the passport is issued. |
| datetime | Date the passport expires |
| datetime | Date the passport was issued. |
| string (30) | Identifying number from a government-issued passport |
| string | Last 4 digits of the |
| array | An array of phone objects associated with the customer |
| string (21) | Optional. Name a customer prefers to use and referred to when being addressed. |
| enum | Possible values:
|
| enum | Possible values:
*Values are effectively the same. Helix database, reporting, and bulk files will reflect **Only valid for programs using legacy onboarding API endpoints. Programs using Helix's /customer/onboard API endpoint will not see these values. |
| string (20) | A customer's name suffix. Examples:
|
| string (50) | A client-assigned, unique identifier to represent exactly one customer in the Helix production environment. This typically represents the user ID in your system. The Helix sandbox environment allows duplicate tags for testing. |
| string (30) | Social Security Number (SSN), Employer Identification Number (EIN) or Individual Taxpayer Identification Number (ITIN) Numeric characters only, no formatting (i.e., hyphens, spaces) of any kind Example: 123456789 |
| string | Last 4 digits of the |
| enum | Possible values:
|
| boolean | Default is |
*Property relates to business account functionality. Use of business account functionality requires approval from Q2 and your bank partner.
**Property relates to Preferred Name functionality. Use of Preferred Name functionality requires approval from Q2 and your bank partner.
Updated 17 days ago