Skip to main content

Architecture

CashXChain is built as a modular, API-first orchestration platform for modern payments. The architecture is shaped by the hardest cases — cross-border, multi-currency, multi-rail B2B — and applies to simpler payment workflows without modification.

The architecture separates customer experience, instruction preparation, compliance metadata, route selection, and regulated execution. This separation is central to CashXChain's security, scalability, and regulatory posture.

Architecture layers​

Customer or Platform
        |
        v
CashXChain API and Dashboard
        |
        v
Instruction and Orchestration Layer
        |
        +--> Ledger and audit trail
        +--> FX quotes and routing
        +--> Beneficiary and account metadata
        +--> Compliance metadata preparation
        +--> Webhook and notification service
        |
        v
Regulated Partner Execution Layer
        |
        +--> Banking and payout partners
        +--> Stablecoin and settlement partners
        +--> On/off-ramp partners
        +--> Screening and KYB/KYC partners
        |
        v
Payment Rails and Networks

CashXChain responsibilities​

CashXChain is responsible for:

  • API and dashboard user experience.
  • Account and user permission model.
  • Instruction validation.
  • Route evaluation.
  • Quote orchestration.
  • Metadata structuring.
  • Ledger and audit trail.
  • Webhook normalization.
  • Statements and reconciliation views.
  • Integration tooling.

Partner responsibilities​

Regulated partners perform regulated activities where required, including:

  • Fiat custody or safeguarded account services.
  • Crypto-asset custody where applicable.
  • Payment execution.
  • Stablecoin issuance, redemption, or transfer execution.
  • AML/CFT and sanctions screening.
  • Travel Rule obligations.
  • Local payout processing.
  • Banking scheme participation.

Zero-custody design principle​

CashXChain's target architecture is a zero-custody and zero-disposal-authority model. CashXChain prepares and routes instructions, but user funds remain in partner-controlled infrastructure where regulated execution takes place.

This principle affects product design:

  • No customer private keys are held by CashXChain.
  • No customer funds are directly controlled by CashXChain.
  • Partner authorization is required for execution.
  • If CashXChain is unavailable, funds remain accessible through the relevant partner arrangements.

Multi-rail routing engine​

The routing engine evaluates cost, speed, corridor availability, compliance requirements, partner status, liquidity, and settlement characteristics. It is designed to choose the best practical route for each transaction while preserving auditability.

CashXChain treats both off-chain banking rails (SEPA, SWIFT, ACH, FPS, local payout schemes) and on-chain rails (regulated stablecoins on supported chains) as first-class infrastructure. Stablecoins are also used internally as a settlement medium between partners and corridors when this produces a better outcome than bank-only routing. See Rails for the full list of sending and funding rails.

Ledger-first accounting​

CashXChain maintains an internal ledger for operational visibility and reconciliation. The ledger reflects payment states and balance movements but does not replace partner records, bank statements, or legally required account records.

Environment separation​

Sandbox and production are separated by base URL, credentials, webhook endpoints, data, and operational controls. Never reuse production secrets in sandbox or sandbox secrets in production.