Submit verification data

First call in the KYC API flow. Nothing else is accepted before it: country is what routes the customer to their country’s requirements.

Answers 202, not 200. The request is validated before we answer; recording it upstream happens after. A 202 means accepted, not satisfied. Read the result from the kyc_updated webhook or GET /ramp/customer/{customer_id}/kyc?requirements=true.

Re-submitting overwrites what was sent before, and never moves the customer’s review status on its own. Personal accounts only.

POST /ramp/customer/{customer_id}/verification

Submit verification data

cURL

curl --request POST \
  --url https://api.sand.etherfuse.com/ramp/customer/{customer_id}/verification \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "firstName": "Ana",
  "lastName": "Ejemplo",
  "dateOfBirth": "1990-01-01",
  "taxId": "XAXX010101000",
  "additionalInfo": {
    "curp": "XEXX010101HNEXXXA4"
  },
  "country": "MEX",
  "address": {
    "street": "Av. Reforma 100",
    "city": "Ciudad de Mexico",
    "region": "CDMX",
    "postalCode": "06600",
    "country": "MEX"
  }
}
'

202

{
  "customerId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "status": "in_progress"
}

Authorizations

Authorization · string · header · required

API key sent in the Authorization header.

Path Parameters

customer_id · string<uuid> · required

The customer (child org) ID. Must belong to the caller's organization or a direct child.

Body

application/json

Personal data a partner submits on the customer's behalf. A Mexican customer (country: "MEX") needs a CURP and RFC to complete verification.

firstName · string · required

lastName · string · required

dateOfBirth · string · required

YYYY-MM-DD. Any other format is a 400.

Example:

"1990-01-01"

taxId · string · required

The customer's tax identification number. The RFC for a Mexican customer.

Example:

"XAXX010101000"

country · string · required

The customer's country, as an ISO 3166-1 alpha-3 code. Alpha-2 codes and country names are rejected. This is the one country field for the customer (there is no separate nationality), and its value routes them to their country's requirements.

Example:

"MEX"

address · object · required

The customer's residential address. Required, and it must match the identity document you upload; the provider cross-checks the two.

Show child attributes

additionalInfo · object

Information beyond the standard personal data, which some verifications ask for.

Show child attributes

Response

202

application/json

Accepted and being applied. The customer's current verification status is returned.

Where the customer's verification stands after a partner write. status is the same value GET /ramp/customer/{customer_id}/kyc reports, so there is one vocabulary across both.

customerId · string<uuid> · required

status · enum<string> · required

The customer's overall verification status. A write never moves it on its own.

Available options: not_started, in_progress, submitted, approved, denied