Key terms
Glossary of key terms and concepts used across B2BINPAY DeFi, featuring terminology, definitions, and essential concepts for platform users
Account
An account is a shared multi‑signature wallet. Technically, it's a smart contract deployed for a specific account and network.
Each account is managed collectively by a group of users. Each operation on such account requires certain independent signatures to approve the operation before it's executed.
In the B2BINPAY DeFi app, each account has:
A list of Signers.
A Required signatures threshold.
Refer also to Queue.
Address
An address is a unique blockchain identifier used for deposits, payouts, or transaction execution. Depending on context, an address can represent:
An invoice address (deposit address) created by the smart contracts.
A wallet address belonging to a signer or payout receiver.
Refer also to Deposit address, Invoice, and Payout.
Address book
The address book is a list of saved receiver addresses and labels. Saved entries can be reused when creating payouts or other operations, which reduces manual input and the risk of sending funds to an incorrect address.
Refer also to Payout.
API key
An API key is a credential used to access B2BINPAY DeFi API app programmatically. Each key is associated with a specific account.
API keys are managed on the Settings tab of the Account page.
Refer also to API service and Callback secret.
API service
The API service exposes B2BINPAY DeFi REST APIs for working with entities such as invoices, payouts, and so on.
Refer also to API guide.
Base currency
The base currency is the currency used for presenting balances, totals, and some reports in the B2BINPAY DeFi app. It doesn't change the underlying blockchain currency of deposits and payouts; it only affects how values are displayed and settled in the UI.
The base currency is selected on the Profile settings page.
Balance
The balance of an account or asset is the aggregated value of all relevant transactions. Primary balance types include:
Total balance: Reflects all executed transactions for the account across assets, converted to the base currency.
Uncollected balance: Reflects deposits received on invoice addresses but not yet claimed to the account wallet.
Balance by asset: Shows per‑token and per‑network balances for the account.
Refer also to Deposit, Claim, and Base currency.
Batch claim
A batch claim is an operation that collects funds from multiple invoice deposit addresses in a single claim transaction for a given currency. Batch claims reduce on‑chain fees by aggregating several claims into one transaction, where supported by smart contracts.
Batch claims are initiated from the Claims page when more than one uncollected claim exists for the selected currency.
Refer also to Claim and Invoice.
Batch execution
Batch execution is the process of executing several fully signed queue operations in a single on‑chain transaction. Batch execution is available only when:
The selected operations are fully signed.
Their nonce values form a continuous sequence (for example,
5,6,7).
Batch execution is initiated from the Queue page with the Execute batch action.
Refer also to Queue, Nonce, and Payout.
Blockchain
A blockchain is a specific network environment. Each network is identified by its chainId and has its own set of assets, contracts, and block explorers.
The selected network in the app header determines which balances, queue operations, and transactions are shown.
Callback
A callback is an HTTP notification that the B2BINPAY DeFi app sends to a client system when an invoice- or payout-related event occurs.
Invoice-related callback types:
INVOICE_CREATED: The invoice was created.INVOICE_DEPOSIT_RECEIVED: An incoming deposit transaction was detected on the invoice address.INVOICE_DEPOSIT_CONFIRMED: The incoming transaction has reached the required number of confirmations.INVOICE_PAID: The paid amount is equal the requested amount and the invoice status changes to Paid* (for invoices with indicated amount).INVOICE_UNRESOLVED: The paid amount is greater than the requested amount and the invoice status changes to Unresolved* (for invoices with indicated amount).INVOICE_CLAIMED: Funds from the invoice address have been claimed to the account multisig wallet.
Payout-related callback types:
PAYOUT_CREATED: The payout was created.PAYOUT_SENT: The payout transaction was sent to the blockchain.PAYOUT_EXECUTED: The payout transaction was mined to a block and executed successfully.PAYOUT_FAILED: The payout transaction failed in the blockchain.
Retry policy: If an attempt to send a callback fails, the system will try to resend the callback three times, once every five seconds.
For details, payload examples, and callback verification, see Callbacks.
Refer also to Callback secret, Invoice, and Payout.
Callback secret
The callback secret is a value used to sign callbacks so that the receiving system can verify their authenticity. Rotating the callback secret invalidates the previous value and is recommended when credentials are updated or exposed.
The callback secret is managed on the Settings tab of the Account page. See Configure a callback secret and API keys for more details.
Refer also to Callback and API key.
Claim (collection)
A claim (or collection) is an operation that transfers funds from an invoice deposit address to the account wallet. When withdrawing a token from an invoice address, the native currency is always withdrawn as well.
Claims can be created for a single invoice and currency or grouped into Batch claims.
On the Invoices page, claims are initiated from the Claims tab of a specific invoice.
On the Claims page, claims are initiated from aggregated entries that represent uncollected funds for an invoice and currency.
Refer also to Deposit, Invoice, and Transfer.
Currency
A currency is a cryptocurrency (coin, stablecoin, or token) supported by the system.
Refer also to Blockchain network and Balance.
Deposit
A deposit is an incoming transaction to an invoice or directly to an account.
Deposits increase the uncollected balance of an invoice or account until a Claim or payout moves the funds.
Refer also to Deposit address and Transfer.
Deposit address
A deposit address is a blockchain address generated by the smart contracts for receiving payments. Each deposit address is bound to the wallet (public address):
Funds can be collected only to the owner’s wallet or account.
The smart contract can't direct funds to arbitrary third‑party addresses.
In invoices, the deposit address is represented by a smart contract and managed by the multisig wallet.
Deposit addresses are typically created through Invoices.
Invoice
An invoice is a request for cryptocurrency payment that generates a unique deposit address for receiving funds.
The invoice address is represented by a smart contract and managed by the multisig wallet. Invoice activity is tracked across the Settings, Transfers, Claims, and Callbacks tabs on the invoice details page.
Refer also to Deposit address, Claim, and Transfer. For detailed workflows, see Invoices.
Network
The network is the blockchain environment on which an account operates.
Switching the network in the app header changes:
Which balances are shown.
Which queue operations, invoices, and transfers are visible.
Refer also to Blockchain network.
Nonce
A nonce is the sequential identifier that defines the order of operations executed by a smart contract.
In the B2BINPAY DeFi app:
Each queue operation (for example, a payout or configuration change) has a nonce.
Operations must be executed in nonce order; the item with the smallest nonce is processed first.
Creating a payout with a nonce that matches an existing one creates a conflicting or replacement operation.
Nonce values are visible in the Queue and can be adjusted when creating certain operations such as payouts.
Refer also to Queue, Batch execution, and Operation.
Operation
An operation is an action that requires multisig approval before execution. Examples include:
Account configuration changes (for example, signers and thresholds).
Payouts and other asset transfers.
Each operation has a nonce and require one or more operation signatures.
Refer also to Queue and Payout.
Operation signature
An operation signature is a digital signature added by a signer to authorize a specific operation. Multiple signatures can be attached to the same operation until the threshold is met and the operation becomes executable.
Refer also to Signature, Signer, and Operation.
Payout
A payout is an outgoing on‑chain transfer from the account to an external receiver address. Payouts:
Are created in the Payouts section by specifying a receiver address, currency, amount, and optional callback settings.
Enter the Queue and must be signed by the required number of signers.
For details, see Payouts.
Queue
The queue is an ordered list of operations waiting for signatures or execution. Typical queue items include:
Payouts.
Configuration changes (for example, confirmation rules).
Reject (if you need to cancel an operation in the middle of a queue).
Queue items are processed in the nonce order.
The Queue page exposes:
Pending operations that need signatures or execution.
History of executed or failed operations.
Tools for signing, executing, rejecting, or replacing operations.
For detailed workflows, see Queue.
Read‑only access
Read‑only access is a restricted mode in which an account or user can view data but can't perform sensitive actions.
Read‑only users cannot:
Create, sign, or execute operations.
Add or disconnect accounts.
Change required signatures or other critical settings.
Read‑only states may apply to accounts that were removed from configuration on a given network but still exist elsewhere.
Required signatures
The required signatures value defines how many signers must approve an operation before it can be executed, expressed as X/Y, where:
Yis the total number of signers.Xis the minimum number required to execute an operation.
The setting is configured on the Members tab of the Account page.
Refer also to Multisig, Signer, and Threshold.
Signature
A signature is a cryptographic proof generated when a user signs a message or transaction with their private key. In B2BINPAY DeFi it's used for:
Authentication and login flows (for example, SIWE and EIP‑712 signatures).
Approving multisig operations and transactions.
Refer also to Operation signature and Wallet authentication.
Signer
A signer is an account that has permission to approve and execute operations for an account.
Signers can:
Create operations (such as payouts or configuration changes).
Sign queue items.
Execute fully signed operations.
The list of signers for an account is managed on the Members tab of the Account page.
Refer also to Required signatures and Multisig.
Threshold
The threshold is another name for the number of Required signatures needed to execute a multisig operation. It's defined when the account is created and can later be updated through configuration operations.
Refer also to Multisig.
Transaction
A transaction is a blockchain record representing the execution of a call on a network.
Each blockchain transaction is assigned a unique TXID which is a transaction identifier, or transaction hash. It stores transaction details, such as the sender's and receiver's addresses, amount, and time, all encrypted into a unique alphanumeric string. Each TXID links to a blockchain explorer — a public tool for tracking transactions.
Transfer
A transfer is a record of an on‑chain transaction tracked by the B2BINPAY DeFi app. Transfers can represent:
Incoming deposits to invoices.
Claims collecting funds from deposit addresses to the account.
Payouts and other outgoing operations.
For details, see Transfers.
User
A user represents a wallet address interacting with the B2BINPAY DeFi app.
Users authenticate by signing messages and may belong to one or more accounts as signers or viewers.
Refer also to Wallet authentication and Signer.
Wallet authentication
Wallet authentication is the login mechanism based on external wallets.
Instead of passwords, the B2BINPAY DeFi app:
Generates a message.
Asks the user to sign it.
Verifies the signature to confirm wallet ownership.
Last updated
Was this helpful?