Developers

APIs spanning multi-channel collection, settlement, and Payout

Payment API handles multi-channel collection; settlement and Payout APIs cover large-scale conversion and mid-size disbursements. Webhook and reports make all three trackable and reconcilable in merchant systems.

API Coverage

API alineada con los tres servicios principales

Payment API (multi-channel collection)

Crear órdenes de cobro, obtener dirección de pago, consultar estado and procesar confirmaciones.

Settlement API (settlement)

Request large-scale settlement quotes and query status and fee details for crypto-to-fiat conversion or crypto retention.

Payout API (disbursement)

Initiate mid-size crypto wallet, multi-currency fiat, and local-channel payouts; query status and failure reasons.

Webhook & Dashboard

Receive collection, settlement, and Payout events for unified ops and finance views.

POST /v1/payment-intents
{
  "merchant_order_id": "INV-2026-0618",
  "amount": "2480.00",
  "currency": "BTC",
  "network": "BTC",
  "settlement_preference": ["HKD", "USD"],
  "webhook_url": "https://merchant.example/webhook"
}

Webhook event:
payment.confirmed
settlement.review_required

Operational Design

Diseñado para operaciones reales, no solo un botón de pago

Payment-flow issues are not limited to collection—they also include reconciliation, status sync, wrong-chain handling, payout failures, fee accounting, and financial reporting. APIs should be designed together with Dashboard, Webhook, and manual-review workflows.

Admite idempotency key para evitar órdenes o payouts duplicados
Webhook should use signature verification and retry handling
Operaciones de alto riesgo o grandes montos pueden devolver estado review_required
Informes CSV para reconciliation financiera and detalle de comisiones

Secure Integration

Confirmar permisos, firma and reglas de reconciliation antes del onboarding

El sitio público muestra capacidades principales; campos API, eventos, entorno de prueba and flujos de estado se entregan tras review.

Los permisos de API key deben separarse por uso; no mezclar cobro and payout
Webhook should use signature verification, retries, and idempotent design
El sistema financiero debe conciliar transacciones, comisiones, settlement and payout
Operaciones de alto riesgo o payout de grandes montos pueden requerir review manual

FAQ

Which merchants are a fit for API?

API fits platforms and high-frequency merchants that need automated orders, payment-status sync, bulk payout, or finance-system integration.

Is merchant review required before API docs?

Public pages show core capabilities only; fields, sandbox, event names, and permissions are provided after merchant review per scope.

Is Webhook signature verification required?

Merchant systems should use signature verification, retries, and idempotent design to avoid duplicate crediting or bad status sync.

Can I use Dashboard only without API?

Yes. Lower-frequency merchants can start with Dashboard, Payment Link, or Invoice; high-frequency or platform merchants can add API later.

Does API support payouts?

Subject to merchant review, crypto or designated-channel payout requests, status queries, failure reasons, and report reconciliation are supported.

What is typically needed for test onboarding?

Typically callback URLs, a technical contact, expected scenarios, test order flows, and webhook handling.

Need API onboarding documentation?

After merchant review, we can recommend onboarding methods, test flows, and webhook configuration for your architecture.

Apply for onboarding