Integrators

Connect XLO Pay to anything you run

A storefront, an ERP, an internal ledger, a game economy. Everything you need is public — the full API reference, both SDKs, and replayable webhook deliveries you can build against.

What an integration actually involves

Four pieces, whatever you are connecting. Knowing them up front is the difference between a two-day job and a two-week one.

Keys and environmentsAn API key authenticates requests; a separate sk_live key unlocks the wallet to sign. Keeping them apart — and out of your frontend — is the first decision an integration makes.

Webhook handlingA signed endpoint that verifies HMAC, deduplicates on eventId, returns 200 fast and does the real work off the request. This is where most integrations get subtly wrong.

ReconciliationMapping payments to your own orders, crediting the right figure, and handling under- and part-payments without double-crediting a retry.

Checkout and PSPsEmbedding the hosted checkout, connecting Stripe or another provider, and setting the fallback order so a decline retries instead of failing.

What you have to work with

Public and free

→The full API reference — every endpoint, payload and status code, with real sample output rather than illustrations.

→A Python SDK and a Node SDK for the embeddable checkout, with one named method per endpoint.

→Webhook deliveries are recorded and resendable from the dashboard, so you can replay events at your endpoint while you build against them.

→Create an account and derive a test wallet in minutes. No card required.

Know before you build

→XLO Pay is in beta, and currently onboards clients in the UAE, USA and UK only.

→Settlement is USD stable currency only. There is no local-currency support, so price and reconcile in USD.

→Deposits are reported net of fees. Credit the figure the webhook reports, not the figure you quoted.

→Webhooks retry with exponential backoff, so your handler will see the same event twice. Deduplicate on eventId.

A build order that avoids rework

Keys, split

Create the account, issue an API key for requests and keep sk_live server-side only. Never ship either to the browser.

Derive and test

Derive a wallet, take a small payment end to end, and confirm the amount you credit matches the amount that settled.

Webhooks, then idempotency

Verify the signature first, then make the handler safe to run twice. Replay deliveries from the dashboard until both hold.

Reconcile, then go live

Prove your ledger agrees with ours on part-payments and retries before real volume lands on it.

Settle these four before you write anything and the build is a short one: what you are connecting XLO Pay to, which chains and card providers you need, whether you are taking one-off payments or recurring billing, and where the money has to land in your own books.

Start with a test wallet

Create an account, derive an address and take a payment end to end before you commit to anything. No card required, and the API reference is open in the next tab.

Create an account →Read the API reference