Create a new User.

A POST request sent to create a User and Wallet. This endpoint is common to both prepaid and debit programs. The country of residence is required to determine the region where the cards will be issued from.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Data to create a new user with a wallet.

Common User Data

wallet
object
required

non-custodial primary wallet information of the user.

string
length between 2 and 64

The first name of the user - Minimum of 2 up to 64 characters in length as a string. In case the user have several first names, they can be concatenated with a whitespace.

string
length between 2 and 64

The last name of the user - Minimum of 2 up to 64 characters in length as a string. In case the user have several last names, they can be concatenated with a whitespace.

string
length ≤ 303

Legitimate email ID of the card user.

phone
object

Phone number. This should be unique across all users.

date

Date of birth of the card user in YYYY-MM-DD format.

string
length ≤ 2

Country of birth of the card user in ISO 3166-1 alpha-2 country code.

string
required
length ≤ 2

Country of residence of the card user in ISO 3166-1 alpha-2 country code.

address
object
shippingAddress
object
Responses

400

The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

401

Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.

403

The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.

409

The was a conflict with the existing resource.

429

The user has sent too many requests in a given amount of time ("rate limiting").

500

The server has encountered a situation it does not know how to handle.

502

This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.

503

The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.

504

This error response is given when the server is acting as a gateway and cannot get a response in time.

Language
Credentials
Header
LoadingLoading…
Response
Choose an example:
application/json