Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Headers
An idempotency key is an arbitrary unique value generated by client to detect subsequent retries of the same request. It is recommended that a UUID or a similar random identifier be used as an idempotency key. A different key must be used for each request, unless it is a retry.
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
Body
Customer to create
Details of a customer
Customer's status
ACTIVE
, DECEASED
, DENIED
, DORMANT
, ESCHEAT
, FROZEN
, INACTIVE
, PROSPECT
, SANCTION
(beta) Ban status of the person. One of the following:
ALLOWED
– person is not banned or suspendedSUSPENDED
- person is manually suspended due to fraudBANNED
– person is banned due to matching ban rules Note: changing the ban status to or from BANNED can only be performed by the Synctera platform based on ban rules.
ALLOWED
, BANNED
, SUSPENDED
"ALLOWED"
Customer's email
"alice@example.com"
Legal address
User-supplied metadata. Do not use to store PII.
Customer's middle name
"Anne"
Add an optional note when creating or updating a customer. A note is required when updating a customers's ban_status between SUSPENDED and ALLOWED.
Customer's mobile phone number with country code in E.164 format. Must have a valid country code. Area code and local phone number are not validated.
"+14374570680"
Customer's relationships with other accounts eg. guardian. This property is no longer supported. Setting it will return an error.
Shipping address
Customer's full tax ID eg SSN formatted with hyphens. This optional parameter is required when running KYC on a customer. Input must match the pattern ^\d{3}-\d{2}-\d{4}$. The response contains the last 4 digits only (e.g. 6789).
"123-45-6789"
The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.
"abcdef_ghijkl"
Customer's date of birth in RFC 3339 full-date format (YYYY-MM-DD). Must be on or after 1900-01-01 and before current date.
"2000-01-01"
Customer's first name
"Jane"
Customer's last name
"Smith"
Response
Created customer
Details of a customer
Customer's status
ACTIVE
, DECEASED
, DENIED
, DORMANT
, ESCHEAT
, FROZEN
, INACTIVE
, PROSPECT
, SANCTION
All of the customer's addresses
(beta) Ban status of the person. One of the following:
ALLOWED
– person is not banned or suspendedSUSPENDED
- person is manually suspended due to fraudBANNED
– person is banned due to matching ban rules Note: changing the ban status to or from BANNED can only be performed by the Synctera platform based on ban rules.
ALLOWED
, BANNED
, SUSPENDED
"ALLOWED"
The date and time the resource was created.
"2010-05-06T12:23:34.321Z"
Customer's email
"alice@example.com"
This flag indicates whether the person or business has accounts.
Customer unique identifier
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
Customer's KYC exemption
Date and time KYC was last run on the customer
"2010-05-06T12:23:34.321Z"
Customer's KYC status
ACCEPTED
, PENDING
, PROVIDER_FAILURE
, PROVISIONAL
, REJECTED
, REVIEW
, UNVERIFIED
The date and time the resource was last updated.
"2010-05-06T12:23:34.321Z"
Legal address
User-supplied metadata. Do not use to store PII.
Customer's middle name
"Anne"
Customer's mobile phone number with country code in E.164 format. Must have a valid country code. Area code and local phone number are not validated.
"+14374570680"
Customer's relationships with other accounts eg. guardian. This property is no longer supported. Setting it will return an error.
Shipping address
Customer's full tax ID eg SSN formatted with hyphens. This optional parameter is required when running KYC on a customer. Input must match the pattern ^\d{3}-\d{2}-\d{4}$. The response contains the last 4 digits only (e.g. 6789).
"123-45-6789"
Describes the collection method for the customer's SSN:
MANUAL
– the full 9 digits of the customer's SSN was collected.PREFILL
– the customer's SSN was collected using SSN Prefill.
MANUAL
, PREFILL
The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.
"abcdef_ghijkl"
Customer's date of birth in RFC 3339 full-date format (YYYY-MM-DD). Must be on or after 1900-01-01 and before current date.
"2000-01-01"
Customer's first name
"Jane"
Customer's last name
"Smith"