Skip to main content
POST
/
auth
/
register-user-v2
Register user
curl --request POST \
  --url https://raas-partner-cv.nomas.cash/v1/auth/register-user-v2 \
  --header 'Content-Type: application/json' \
  --header 'api_key: <api-key>' \
  --data '
{
  "phoneNumber": "+5215521206703",
  "firstName": "Maria del Carmen",
  "lastName": "Arenas Mendoza",
  "dob": "1987-06-24T07:00:00.000Z",
  "address1": "Cancún International Airport, Carretera a Aeropuerto Cancún, Cancún, Quintana Roo, Mexico",
  "countryCode": "MX",
  "city": "Cancún",
  "state": "Q.R."
}
'
{
  "userId": "OSZwErXgt1MGPHwkYJVqz3LTN0R2",
  "status": "OnProcess"
}

Authorizations

​
api_key
string
header
required

Body

application/json

DTO with extended PII (address, dates) for validators.

Core body for partner user registration (register-user-v2 and related). At least one of phoneNumber or email is typically required by the route. Reused as requester on POST /request-money-full (see RequestMoneyFullParams in model/operation).

​
lastName
string
required

Primary legal last name (e.g. paternal surname). Example: Hernández.

​
firstName
string
required

Legal first name(s). Example: Ana.

​
address1
string
required

User legal address, Street and number. Example: Blvd. Kukulcan Km. 4.5.

Strongly recommended to avoid OFAC matches.

​
countryCode
string
required

Country code. ISO 3166-1 alpha-2.

​
city
string
required
​
state
string
required

Address state/province/department. ISO 3166-2:CC (CC: country code). Or the state short name. Example: DF for Distrito Federal, JA for Jalisco.

​
phoneNumber
string

required

Mobile phone number with country code. Must be a valid mobile phone number. Example: +5215521206703 for MX.

It doesn't allow duplicates.

​
lastName2
string

Optional second last name when used (e.g. maternal surname). Example: Gómez.

Strongly recommended to avoid OFAC matches.

​
gender
enum<string>

Self-reported gender when the product collects it. Example: Female.

Available options:
Male,
Female,
Other,
None
​
dob
string<date-time>

Date of birth in ISO 8601 format (YYYY-MM-DD or full date-time). DOB must be a real calendar date and the person must be at least 18 and under 100 years old.

Strongly recommended to avoid OFAC matches.

​
email
string

Email address. It doesn't allow duplicates.

Strongly recommended.

​
middleName
string

Middle name when collected. Example: María. Strongly recommended to avoid OFAC matches.

​
address2
string
​
address3
string
​
streetNumber
string
​
zipCode
string
​
birthState
string

Address state/province/department. ISO 3166-2:CC (CC: country code). Or the state short name. Example: DF for Distrito Federal, JA for Jalisco.

​
lang
enum<string>

User Language. ISO 639-1. Example: es for Spanish, en for English.

Available options:
en,
es
​
placeDetail
string

Place detail from address if available. Must be a valid place detail json from google maps.

​
latitude
number<double>

Latitude from address if available.

​
longitude
number<double>

Longitude from address if available.

​
callLocationLatitude
number<double>

Latitude from user location if available.

​
callLocationLongitude
number<double>

Longitude from user location if available.

Response

200 — OK. Async registration accepted.

Scenarios for this response:

ScenarioHow to reproduceTypical code / body
Registration acceptedValid RegisterUserParams, phone/email not already enrolled.userId (+ optional status).

See also Full scenario matrix.

Successful user resolution for partner token endpoints (id + optional CIP snapshot).

​
userId
string
required

User ID

​
status
string

Status of the user's CIP process

Available options: Completed, UpgradePending, UpgradeInProgress, UpgradeFailed, UpgradeSoftFailed, AccountUpgradeInProgress

​
statusDetail
enum<string>

Status detail of the user's CIP process

Available options:
None,
InvalidAddress,
InvalidEMail,
UnreadableDoc,
ProvideAdditionalInfo,
InvalidPersonalData,
OtpPrivacyMissing,
OtpContractMissing,
Compliance,
ComplianceBlocked,
OfacFailed