Submit KYC

curl --request POST \
  --url https://api.etherfuse.com/ramp/customer/{customer_id}/kyc \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "identity": {
    "address": {
      "city": "Ciudad de México",
      "country": "MX",
      "postalCode": "06600",
      "region": "CDMX",
      "street": "Av. Reforma 222"
    },
    "dateOfBirth": "1990-05-15",
    "email": "[email protected]",
    "id": "GDUKMGUGD3V6VXTU2RLAUM7A2FABLMHCPWTMDHKP7HHJ6FCZKEY4PVWL",
    "idNumbers": [
      {
        "idType": "curp",
        "value": "GALA900515MDFRPN08"
      }
    ],
    "name": {
      "familyName": "García",
      "givenName": "Ana",
      "motherMaidenName": "López"
    },
    "occupation": "Software Engineer"
  },
  "pubkey": "GDUKMGUGD3V6VXTU2RLAUM7A2FABLMHCPWTMDHKP7HHJ6FCZKEY4PVWL"
}
'

{
  "message": "KYC data submitted for review",
  "status": "proposed"
}

KYC

Submit KYC

Submit identity information (name, address, DOB, tax ID) for a customer programmatically — an alternative to the presigned-URL flow where users complete KYC in the Etherfuse UI.

Use case: partners who want to white-label the KYC experience can collect identity data in their own UI and submit it here.

Submitted data is reviewed by Etherfuse admins before approval; you’ll receive a kyc_updated webhook when the status changes.

Sandbox auto-approval: in sandbox, submitting KYC for a personal customer org immediately approves the customer, fires a kyc_updated webhook, and unlocks orders for the wallet (response status is "approved", not "proposed"). Sandbox-only — production still requires manual review.

Data isolation: partners can only query KYC data they submitted; data submitted by other partners or directly by users is not visible.

POST

ramp

customer

{customer_id}

kyc

Submit KYC

curl --request POST \
  --url https://api.etherfuse.com/ramp/customer/{customer_id}/kyc \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "identity": {
    "address": {
      "city": "Ciudad de México",
      "country": "MX",
      "postalCode": "06600",
      "region": "CDMX",
      "street": "Av. Reforma 222"
    },
    "dateOfBirth": "1990-05-15",
    "email": "[email protected]",
    "id": "GDUKMGUGD3V6VXTU2RLAUM7A2FABLMHCPWTMDHKP7HHJ6FCZKEY4PVWL",
    "idNumbers": [
      {
        "idType": "curp",
        "value": "GALA900515MDFRPN08"
      }
    ],
    "name": {
      "familyName": "García",
      "givenName": "Ana",
      "motherMaidenName": "López"
    },
    "occupation": "Software Engineer"
  },
  "pubkey": "GDUKMGUGD3V6VXTU2RLAUM7A2FABLMHCPWTMDHKP7HHJ6FCZKEY4PVWL"
}
'

{
  "message": "KYC data submitted for review",
  "status": "proposed"
}

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

Request body for submitting KYC identity data

identity

object

required

User's identity information

Show child attributes

pubkey

string | null

The public key of the wallet to submit KYC for (optional — omit to attach to org only)

Response

KYC identity data submitted

Search customer wallets Get org KYC status

⌘I