Skip to main content

Payments Architecture

Celar provides multiple API endpoints to handle different payment operations, such as pay-ins, payouts, rates, withdrawals, and reporting.

Each endpoint currently focuses on a specific operation, making it easier to integrate, validate, and reason about individual payment flows.

Current Structure​

At present, Celar exposes separate endpoints for different payment operations, including:

  • Fiat payout transfer – sending value from stablecoins to fiat rails
  • Pay-ins – accepting stablecoin deposits
  • Payouts – sending stablecoins from Celar-managed wallets to external recipients
  • Withdrawals – moving funds out of Celar-managed wallets to psps and dev external wallets
  • Refunds – returning funds to customers for previous pay-ins
  • Statuses & Reports – tracking and reconciling payments
  • Rates – retrieving exchange rates of fiat to crypto
  • Institutions – Getting institutional payment partners to use in fiat payout transfers

This structure reflects the current implementation and ensures clarity while each operation is built, tested, and stabilized independently.

Direction: Unified Transfers Endpoint​

As Celar continues to evolve, we are moving toward a unified Transfers API that will support multiple payment behaviors through a single endpoint.

Under this model:

  • A single transfer endpoint will handle different payment operations
  • The specific behavior will be determined by an explicit operationType
  • This allows new payment flows to be introduced without breaking existing integrations

For now, only fiat payouts are supported, and the remaining ones will be introduced incrementally as they are implemented.

What This Means for Integrators​

  • You should continue using the existing, documented endpoints
  • Only operations explicitly documented as supported should be used
  • Future consolidation will be additive.

Celar’s goal is to simplify integrations over time while maintaining stability and clarity at every stage.

We recommend following the documentation for each operation as it exists today, while keeping an eye on updates as additional transfer capabilities are rolled out.