Glossary

Key terms

Comercio (Merchant) : The legal entity that receives payments through B4bit Pay. Groups one or more devices and users.

Dispositivo (Device) : A collection point within a merchant. Each device has its own API Key and Secret Key. It can be physical (POS terminal, register) or virtual (website, payment link).

API Key (X-Device-Id) : UUID4 that identifies the device to the REST API. It is sent in the X-Device-Id header of every request.

Secret Key : Hexadecimal key used only to verify the HMAC-SHA256 signature of incoming webhooks. It is never sent in requests.

Pasarela (Gateway) : The B4bit Pay infrastructure that processes payments. It is used in two modes: Redirect Gateway (hosted by B4bit) and API Gateway (you build the UI).

Criptomoneda (Cryptocurrency) : Digital asset based on blockchain (BTC, ETH, USDT, etc.). In B4bit Pay, each combination (currency, network) has its own symbol.

Divisa fiat (Fiat currency) : Legal tender (MXN, USD, EUR, etc.). B4bit Pay charges and displays amounts in fiat but settles internally in USDC.

Stablecoin : Cryptocurrency whose value is pegged to a stable asset, usually the USD (USDT, USDC, DAI).

USDC : Stablecoin backed 1:1 by USD. B4bit Pay uses it internally as the settlement currency.

Lightning Network / BTCL : Off-chain payment network on top of Bitcoin, virtually instantaneous. B4bit Pay uses the BTCL symbol. The flow requires a BOLT11 invoice instead of an address.

TAG / MEMO : Additional identifier required by XRP, XLM and ALGO to route the payment to the correct recipient in shared wallets. If not sent, the funds are lost.

Webhook : HTTP request that B4bit Pay sends to your server when a payment state changes. It is signed with HMAC-SHA256.

HMAC (Hash-based Message Authentication Code) : Algorithm to verify the authenticity and integrity of a message with a shared secret key. B4bit Pay uses HMAC-SHA256.

Nonce (X-NONCE) : Unix timestamp included in the webhook to prevent replay attacks. Reject requests with a nonce older than 15-20 seconds.

Reference : Optional field that the merchant includes when creating an order. Used to correlate the B4bit Pay order with your internal system (for example, the order ID in your database).

Input currency : The cryptocurrency and network used by the customer to pay. If not specified when creating the order, the customer chooses it on the gateway.

Output amount (expected_output_amount) : The amount you charge, in fiat currency.

Input amount (expected_input_amount) : The equivalent amount in cryptocurrency, calculated by B4bit Pay using the rate at the time the order is created.

Safe : Boolean field of the payment. true indicates that the payment has ≥1 blockchain confirmation and it is safe to release the product/service.

Good fee : Indicates whether the network fee of the incoming transaction is adequate. If it is false, the confirmation may take longer.

RBF (Replace By Fee) : Bitcoin mechanism to replace a pending transaction with one paying a higher fee. B4bit Pay detects it and flags the rbf field when applicable.

KYB (Know Your Business) : Process of verifying the merchant’s business identity. In B4bit Pay it activates three levels according to operated volume.

LFPIORPI : Ley Federal para Prevención de Operaciones con Recursos de Procedencia Ilícita (Mexican Federal Law for the Prevention of Operations with Resources of Illicit Origin). B4bit Pay operates as a “vulnerable activity” under this law.