Skip to main content

Key features

CashXChain combines a developer-friendly API, a business-grade payment model, and a compliance-aware orchestration layer.

API-first infrastructure​

The money workflow is one API: business verification, currency accounts, balances, beneficiaries, payouts, FX quotes and conversions, statements, webhooks and request logs. Sandbox and production serve the same routes, so an integration changes a base URL and a key to go live. See the Quickstart.

Fiat-native user experience​

Business users work in familiar terms: EUR, USD, local currencies, invoices, suppliers, customers, statements, and payment references. They do not need to manage wallets, gas, seed phrases, or blockchain explorers.

Multi-currency balances​

CashXChain gives businesses one view of their currency accounts — local accounts with their own bank details in EUR, GBP, USD and CAD, and further currencies over SWIFT — with available and pending balances for each.

Quote-driven FX​

FX is handled through explicit quotes. A quote defines what is sold and bought, the rate after our margin, the margin itself, any unit fee, and when it expires. This gives finance teams predictability before committing to a transaction.

Payment orchestration​

CashXChain normalizes every rail into one payout lifecycle: created, submitted, processing, settled — or failed, cancelled, returned. Teams integrate once and support multiple corridors, currencies, and payment types over time — starting with the cross-border and B2B cases that benefit most.

Webhooks​

Signed webhook delivery, with retries over a day and a delivery log you can read through the API. Today no event is sent for a business's payouts, incoming payments or verification — see Webhooks — so follow payouts by polling.

Compliance-aware architecture​

CashXChain collects and structures information required for business verification, beneficiary setup, risk assessment, purpose of payment, and partner execution. Regulated partners perform regulated checks and execution where required.

Audit trail and reconciliation​

Every payout has a permanent id, the rail's reference, and the times it was created, submitted and settled. Statements list every booked movement with running balances and a checksum third parties can verify. This makes CashXChain suitable for finance teams that need traceability rather than consumer-style payment history.

Sandbox-first integration​

The sandbox serves the same API as production on a simulated rail: verification is approved at once, test money is a click away, and payouts settle inside the request. What the sandbox cannot show — the timing and the bank-side checks of a real rail — is spelled out in Environments.