Wallets Overview

Celar provides custodial wallets as a core primitive used across payment operations.
Wallets are used to receive, hold, and transfer stablecoins on supported blockchains.

Each wallet is identified by a unique celar_walletId and is required for interacting with Celar’s payment infrastructure.

Wallets are intentionally abstracted so they can be reused across multiple operations, including but not limited to:

• Pay-ins
• Transfers
• Payouts
• Withdrawals

Wallet Levels

Celar supports two wallet levels, depending on the entity type and use case.

1. Customer Wallets

Customer wallets represent wallets owned by end customers.

• Customer wallets are created by developers
• A customer wallet is created by including a customer_id
• Each wallet is uniquely associated with a single customer
• Funds held in a customer wallet belong to that customer

Customer wallets are typically used when:

• Customers are the final recipients of funds
• Payments are customer-to-customer

2. Organization Wallets

Organization wallets represent wallets owned by the integrating entity (developer or PSP).

• These wallets belong to the organization
• They are not tied to a specific customer
• They are commonly used for:
  • Platform fees
  • Treasury balances
  • Settlement flows

Wallet Lifecycle

1. Create a Wallet

   • Wallets are created via the API.
   • Customer wallets require a customer_id.
   • Organization wallets do not.

2. Fund the Wallet

   • Funds arrive through completed payment flows or transfers.

3. Use the Wallet

   • As a source or destination in payment operations.

4. Monitor & Reconcile

   • Wallet balances and activity can be queried via wallet APIs.
   • Used for tracking inflows, outflows, and fees.