Create a new end-user under the authenticated client. - If `userId` is provided, it will be used; otherwise a new UUID will be generated. - `bins` config defines which BINs are enabled for this user and what fees the client wants to charge. - `status` is optional and defaults to `pending` if omitted. - Optional `meta` allows storing arbitrary JSON.
Request body
application/json
· UserCreateRequest
· required
| Field | Type | Required | Description |
|---|---|---|---|
bins |
array of Bin |
yes | Enabled BINs and fees to charge this user. |
meta |
object |
no | User metadata (JSON). For B2C cardholders this must contain personal data fields (firstName, lastName, email, birthday, gender, idType, idNo, nationality, etc.). See `CreateUserCardholder` endpoint for the full list of required fields. `meta` is stored as given and is **not** validated here — the field rules (charsets, length limits, mobile-only phone, reference codes) are enforced when the cardholder is created, so apply them in your own form validation to avoid a late rejection. |
status |
string |
no | Initial user status. Defaults to `pending`. |
userId |
string |
no | Optional user ID. If omitted, a new UUID will be generated. |
Responses
| Status | Body | Description |
|---|---|---|
201 |
UserCreateResponse |
User successfully created. |
400 |
Error |
Invalid request. |
Specification
This page is generated from the OpenAPI specification, which remains the authoritative machine-readable source.