Vocabulary

The words this portal and the API use, defined as ChatterPay B2B means them. Every term here is one you can meet while integrating, operating or evaluating the platform: in a request, in a response, on an operation's timeline, or in what your own deployment is responsible for.

• Adapter: a component that translates ChatterPay's common model to the specific API or mechanics of a blockchain or provider. You never call one directly; it is why one request shape works across networks that do not resemble each other.
• Base units: the smallest indivisible unit of an asset, as an integer — 1,000,000 for one USDC with six decimals. Every amount in a request, a quote and an operation is in base units, so nothing is lost to a rounded decimal.
• Bundler: the service that collects UserOperations and submits them to the EntryPoint on an EVM network. ChatterPay operates or configures it; your integration never addresses it.
• Capability manifest: the versioned document that states which networks, assets, contracts, providers, execution mode and limits are enabled for one deployment. It is what makes a capability available to you, or not yet.
• Chain account: the blockchain account behind a wallet on one specific network, with that network's own address. One wallet can hold a chain account per enabled network.
• Deposit route: the address, and any memo or tag the network requires, that a user's funds can be sent to from outside the platform in order to be credited to their wallet.
• EntryPoint: the central ERC-4337 contract that receives and processes UserOperations on an EVM network.
• EUTXO: Cardano's extended unspent-output model. A transfer spends whole outputs and builds new ones, which is why a Cardano operation reports outputs rather than a balance decrement.
• Event: a durable record of a state change, readable in order from a cursor so your backend can catch up after being offline without missing one.
• Finality: how certain it is that a transaction a network has confirmed will not be reverted. Each network reaches it differently, and an operation states the confirmation level it waited for.
• Hot wallet: a wallet whose key is available to a connected service that can sign online.
• Idempotency: the property that lets you repeat a request without duplicating its financial effect. Every financial mutation takes a unique request id; sending it again returns the original operation instead of creating a second one.
• Leg / OperationLeg: one independent transaction that is part of a composite operation, with its own network, provider, amount, hash and status.
• Ledger: the append-only record of the internal movements and adjustments tied to an operation, from which amounts, fees, gas, refunds and compensations can be reconstructed.
• Operation: the durable resource that represents a transfer, a swap or another financial action, and carries its whole lifecycle. It is what you follow after submitting an intent, and what a webhook tells you about.
• partner_managed custody: the model in which you control the keys and the signing authority for your users' wallets.
• Partner Signer Gateway: the signing service under your control. It validates a signing request and uses the key matching its keyReference and the authorized policy, so the key never reaches the platform.
• Paymaster: the ERC-4337 contract that pays an operation's network fee on an EVM network, which is what lets a user send without holding the network's own coin.
• Private key: the cryptographic secret that produces valid signatures for a blockchain account.
• Provider: an external service a capability executes or is assisted by — an RPC endpoint, a bundler, a paymaster, or a route aggregator.
• Quote: the priced estimate of an operation before it is executed: the route, any asset conversion, each fee and the total debit. Accepting a quote is what turns an intent into an operation.
• Reconciliation: comparing an operation, the ledger and external evidence to confirm the result and record any difference or adjustment.
• Self-custody: a model in which the user holds the signing authority and no third party can move their funds unilaterally.
• Self-hosted: a deployment whose runtime runs inside your own cloud environment, operated by you.
• Sponsorship: the platform paying an operation's network fee out of a funding account instead of the sender's balance. A quote states when a cost was sponsored and who bore it.
• Tenant: the unit of administrative and data isolation inside a deployment. Your credential determines your tenant, and no request parameter can reach another one's data.
• Trustline: on Stellar, the explicit authorization an account must hold before it can receive a given asset. A Stellar deposit route exists only once the trustline for that asset does.
• UserOperation: the ERC-4337 structure describing an action a smart account requests. Its own hash, userOpHash, is published on the operation, its steps and its legs.
• UTXO: an unspent transaction output on Bitcoin. A transfer spends whole outputs, which is why the fee and the change are part of what an operation reports.
• Webhook: a signed HTTP notification ChatterPay sends to the endpoint you registered, so your backend learns about a state change without polling.