Payment orchestration platform

One API, one hosted Cashier, any provider

PayXiro extracts payment complexity out of your product and into a dedicated infrastructure layer. Built for trading platforms and fintechs — broker CRMs, prop firms, and trading apps.

Create a Checkout Session
curl -X POST https://payxiro.com/api/v1/checkout_sessions \
  -H "Authorization: Bearer sk_test_..." \
  -H "Idempotency-Key: your-deposit-id" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "500.00",
    "asset_code": "USDT.TRC20",
    "customer": { "external_ref": "12345", "country": "MY" },
    "success_url": "https://your-app.example/deposits/success",
    "cancel_url": "https://your-app.example/deposits/cancel"
  }'

How it works

Your platform connects on one side; the providers you already use connect on the other. PayXiro owns everything in the middle.

1

Create a session

One server-side call to /api/v1/checkout_sessions with an Idempotency-Key. PayXiro returns a hosted Cashier URL.

2

Customer pays

Present the hosted Cashier — redirect, popup, embedded, or headless. Routing and provider capabilities decide the methods shown.

3

Signed webhook credits

PayXiro POSTs an HMAC-signed event when the payment succeeds. Verify it, dedupe on the event id, and credit — never on the redirect.

Everything the middle layer needs

Grounded in what ships today — no theatre. Deposits across crypto providers, with the operational surface a payments team actually uses.

Multi-provider routing

Ordered routing rules with fallback chains and provider-health awareness — no branching in your code.

Double-entry ledger

Balanced journals for every money event; append-only audit trail, balances derived, never edited.

Risk & review

Configurable rules, velocity limits, and a manual review queue that holds suspicious payments for a decision.

Four integration modes

Redirect, popup with a postMessage contract, embedded iframe via embed.js, or fully headless from the API.

Open-amount deposits

Skip the fixed amount — the Cashier shows "send any amount" and the payment settles at whatever arrives.

Signed webhooks

HMAC-SHA256 signatures with a 5-minute tolerance window and an automatic retry schedule out to 24h.

Sandbox with test_gateway

Full API parity against a simulated provider. Magic amounts drive declines, async webhooks, dedupe, and review.

Bring your own providers

A provider is a catalog row plus one adapter — no schema change to add another. The launch crypto providers:

StripeStripe
NOWPaymentsNOWPayments
Match2PayMatch2Pay
B2BinPayB2BinPay
CoinsbuyCoinsbuy

Integrate from the docs alone

Auth, idempotency, the four integration modes, webhook signature verification, and the sandbox test plan — everything an engineer needs to go live.

Get started