Skip to main content

Element Pay Partner API

Provider-neutral fiat ↔ crypto ramps and optional banking for B2B partners. Integrate once against Element Pay — we route local African fiat (mobile money and bank) by corridor, return binding quotes, and notify your backend via webhooks when orders settle.

Every customer must KYC

All end-customers must complete KYC in the customer vault before you quote with customer_id (pcus_*). KYC and banking are different products:
  • status=approved → corridor quotes and accepts with customer_id
  • products.deposit_account.status=ready → account open, deposit instructions, sends, etc.
You do not need banking to run African fiat ↔ crypto ramps. See Customer KYC quickstart then Quickstart.
An inline customer object on quote is deprecated — still accepted for existing integrations while you migrate. New work should use the vault. See Quote and accept.

What you can do today

Supported countries and payment methods come from GET /partner/catalog. Details: Corridors overview.

Core pattern (ramps)

Every corridor order follows the same steps after KYC is approved:
  1. Discover — GET /partner/catalog (copy providers[].id → network_id)
  2. Quote — POST /partner/orders/quote with customer_id
  3. Accept — POST /partner/orders/{quote_id}/accept
Settlement: webhooks order.processing, order.settled, order.failed. See Webhooks and Quote and accept.

Where to start

For coding agents: read llms.txt at the docs repo root, then Agent quickstart, then openapi.yaml.

Agent quickstart

Auth, OnRamp path, optional banking/accounts, webhooks, pitfalls.

Local fiat ↔ stablecoin

OnRamp + OffRamp: what changes per corridor, rate lock, finality.

Quickstart

KYC → approved → first KE OnRamp quote → accept.

Customer KYC

Requirements, documents, submit, and approval.

Quote and accept

Request checklist and response examples.

Customer-signed accepts

Optional EIP-712 accept when the customer wallet must authorize.

Banking

Optional — accounts after deposit account is ready.

Base URLs

All partner routes are under /partner/*. Auth: X-API-Key header — Authentication.

Support

Email compliance@elementpay.net for sandbox API keys, corridor enablement, and production onboarding.