Paying suppliers in 59 countries from a USDT or USDC balance: how the XEROF API flow works

XEROF — Tue, 10 Nov 2026 18:10:05 +0000

Many companies now hold part of their treasury in USDT or USDC, while their suppliers still want local currency in a bank account. This post walks through how that payment looks when you automate it with the XEROF REST API: what happens in which order, what your system has to store, and where integrations usually go wrong.

XEROF is a Swiss regulated crypto brokerage in Zug (FE Swiss Financial AG, VQF member No. 100954). It is a brokerage and settlement counterparty, not an exchange: there is no order book, and every conversion is priced for the full amount.

The basics


Base URL	`https://online.xerof.ch/gateway/api/v1`
Version	v1
Spec	OpenAPI 3.0.0
Auth	JWT bearer token in the `Authorization` header
Format	JSON over HTTPS

Credentials are issued to onboarded clients on request. Sandbox credentials are available, so you can test the whole flow before production. Rate limits and IP allowlisting are set per client when the credentials are issued.

Authentication

Authenticate with your credentials and receive a signed JWT.
Send it on every request as Authorization: Bearer <token>.
Tokens are short lived. Refresh them; do not cache one indefinitely.

The resource groups

Balances: the balance of every asset on your account, per currency and per wallet.
Wallets: your wallets and their deposit addresses, per asset and network. Each client has its own wallet, never pooled with other clients.
Orders: create and track conversions. Each order returns the executed rate and the XEROF fee as separate lines.
Deposits: incoming on-chain and bank deposits with status, confirmations and references.
Transfers: move assets on chain from your wallet to your own whitelisted address.
Fiat withdrawals: instruct payments in USD, EUR, CHF or GBP to your own or a third-party bank account.
Webhooks: be notified when a deposit lands, an order fills or a payout settles.

A supplier payment, step by step

1. Fund. Read your deposit address from Wallets and send USDT or USDC on Ethereum (ERC-20). This matters: a payment to a third party can only be funded with USDT or USDC on Ethereum. Other assets and other networks can be converted, but the money then goes to a bank account in your own name.

2. Wait for the deposit. Subscribe to the deposit webhook instead of polling. Act only when the deposit is confirmed and credited.

3. Convert. Create an order from the stablecoin to the payout currency. Store the executed rate and the fee from the response as two separate values. Your accountant will ask for both.

4. Pay. Create the fiat withdrawal to the supplier's bank account with your invoice reference. The supplier is checked as a beneficiary before the first payment, so add new suppliers ahead of the due date, not on it.

5. Reconcile. The payout webhook tells you when the payment has settled. Match it to your invoice by your own reference.

The supplier never touches crypto. It receives an ordinary bank transfer from a Swiss regulated counterparty.

Four things that save you a bad day

Send an idempotency reference on every write. If a request times out and you retry, the reference stops a second order or a second payout from being created.
Treat amounts as strings. Amounts come back as decimal strings. Parse them into a decimal type, never a float.
Use webhooks, then verify. Let the webhook trigger the next step, then read the resource once to confirm its state before you act on it.
Keep rate and fee apart in your ledger. They arrive as separate lines for a reason: one is the market, the other is the cost of the service.

What it costs

The brokerage fee follows monthly volume: 1.00% up to USD 250,000, 0.85% up to 1,000,000, 0.65% up to 2,000,000. A payment to a third party adds 0.25%. There is no minimum ticket.

DEV Community: XEROF