Submit KYC identity data

curl --request POST \
  --url https://api.etherfuse.com/ramp/customer/{customer_id}/kyc \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "pubkey": "9Qx7r...",
  "identity": {
    "name": {
      "givenName": "John",
      "familyName": "Doe"
    },
    "dateOfBirth": "1990-01-15",
    "address": {
      "street": "123 Main St",
      "city": "Mexico City",
      "region": "CDMX",
      "postalCode": "06600",
      "country": "MX"
    },
    "idNumbers": [
      {
        "value": "XAXX010101000",
        "type": "RFC"
      }
    ]
  }
}
'

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

KYC

Submit KYC identity data

Submit identity information (name, address, DOB, tax ID) for a customer programmatically. This is 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 via this endpoint.

Submitted data will be 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. The response status returns "approved" (not "proposed"). This shortcut is 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 identity data

curl --request POST \
  --url https://api.etherfuse.com/ramp/customer/{customer_id}/kyc \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "pubkey": "9Qx7r...",
  "identity": {
    "name": {
      "givenName": "John",
      "familyName": "Doe"
    },
    "dateOfBirth": "1990-01-15",
    "address": {
      "street": "123 Main St",
      "city": "Mexico City",
      "region": "CDMX",
      "postalCode": "06600",
      "country": "MX"
    },
    "idNumbers": [
      {
        "value": "XAXX010101000",
        "type": "RFC"
      }
    ]
  }
}
'

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

Authorizations

Authorization

string

header

required

API key for authentication. Pass the key directly (e.g., Authorization: your-api-key). Do not use a Bearer prefix.

Path Parameters

customer_id

string<uuid>

required

ID of the customer

Body

application/json

Request body for submitting KYC identity data programmatically

identity

object

required

User identity information

Show child attributes

pubkey

string

Public key of the wallet to submit KYC for. Optional — if omitted, KYC is attached at the organization level.

Response

KYC data submitted successfully

status

string

Example:

"proposed"

message

string

Example:

"KYC data submitted for review"

⌘I