> ## Documentation Index > Fetch the complete documentation index at: https://docs.etherfuse.com/llms.txt > Use this file to discover all available pages before exploring further. # Glossary > Key terms used across the Etherfuse API and docs. ## Products & assets| Term | Meaning | | - | - | | **Stablebond** | A tokenized, **yield-bearing** sovereign bond (e.g. CETES) — it earns the yield of the underlying government debt while you hold it on-chain. | | **Stablecoin** | A token pegged to a fiat currency, such as USDC. |### StablebondsStablebonds are **yield-bearing** — they accrue the yield of the underlying sovereign debt while you hold them. \ \ \ \
SymbolBondCurrency
Live from `GET https://api.etherfuse.com/lookup/stablebonds` — public, no API key required. ### Token addressesEach stablebond is deployed on multiple chains, each with its own mint (Solana), asset issuer (Stellar), or token contract (EVM). The addresses below are pulled live and link to each chain's block explorer. Use these to verify a token, add a trustline, or import the asset — but when **quoting or building orders**, always use the `identifier` from [`GET /ramp/assets`](https://docs.etherfuse.com/api-reference/assets/list-assets) rather than hardcoding (sandbox identifiers differ from these production ones).## Transaction types| Term | Meaning | | - | - | | **Onramp** | Buying tokens with fiat (the customer pays MXN and receives tokens). | | **Offramp** | Selling tokens for fiat (the customer sends tokens and receives MXN). | | **Swap** | Exchanging one token for another. | | **Quote** | Time-bound pricing for a transaction. Quotes **expire after 2 minutes**. | | **Order** | An onramp or offramp transaction created from a quote. |## Fiat & banking (Mexico)| Term | Meaning | | - | - | | **MXN** | Mexican peso. | | **SPEI** | Mexico's real-time interbank electronic transfer system. | | **CLABE** | The 18-digit standardized Mexican bank account number used for SPEI transfers. | | **depositClabe** | The CLABE a customer deposits MXN into to fund an onramp order. | | **RFC** | Mexican taxpayer ID (Registro Federal de Contribuyentes). Sandbox uses placeholder RFCs — see the [Sandbox Reference](https://docs.etherfuse.com/test-environment.md). |## Fiat & banking (Brazil)| Term | Meaning | | - | - | | **BRL** | Brazilian real — the fiat currency for Brazil ramps. | | **Pix** | Brazil's instant payment system, operated by the Central Bank of Brazil. The Brazilian equivalent of SPEI. | | **Pix key** (`pixKey`) | The identifier a Pix payment is sent to or received from. Its kind is given by `pixKeyType`. | | **Pix key type** (`pixKeyType`) | The kind of Pix key — commonly a CPF, CNPJ, email, phone number, or a random (EVP) key. | | **CPF** | Brazilian individual taxpayer ID (Cadastro de Pessoas Físicas), required for personal BRL accounts. The Brazilian analog of Mexico's RFC. | | **CNPJ** | Brazilian business taxpayer ID (Cadastro Nacional da Pessoa Jurídica), required for business BRL accounts. |## Identity & compliance| Term | Meaning | | - | - | | **KYC** | Know Your Customer — identity verification for an individual (personal customer). | | **KYB** | Know Your Business — verification of a business entity, such as your organization for production access. | | **Presigned URL** | *([Deprecated](https://docs.etherfuse.com/changelog/deprecation-policy.md).)* A hosted Etherfuse onboarding page generated via the API. Superseded by the [`/idv` launch](https://docs.etherfuse.com/guides/kyc-websdk), which handles KYC and agreement signing in one step. | | **Partner fee** | An additional fee (up to 500 bps) a partner can layer on top of the platform fee. See [Fees](https://docs.etherfuse.com/fees.md). | | **bps** | Basis points. 1 bps = 0.01%; 100 bps = 1%. |## On-chain| Term | Meaning | | - | - | | **Public key / wallet** | A blockchain wallet address registered to a customer. | | **Proxy account** | Etherfuse's internal record linking a customer's wallet and identity. `Proxy account not found` means the supplied IDs don't match onboarding. | | **Trustline** | *(Stellar)* Authorization a wallet must establish before it can hold a given asset. Handled automatically for Stellar onramps. | | **XDR** | *(Stellar)* The encoded transaction format a user signs (e.g. the `stellarClaimTransaction`). | | **Claimable balance** | *(Stellar)* A pending balance the recipient claims; used for first-time wallet onramps. | | **burnTransaction** | The unsigned transaction a customer signs to send tokens when offramping. | | **Stellar anchor** | A bridge between the Stellar network and traditional fiat rails, defined by Stellar Ecosystem Proposals (SEPs). Etherfuse acts as an anchor for Stellar offramps. [Learn more ↗](https://developers.stellar.org/docs/learn/fundamentals/anchors) | | **Anchor mode** | *(Stellar offramps)* Setting `useAnchor: true` makes Etherfuse return the anchor destination account and memo (SEP-24) instead of a pre-signed `burnTransaction` — you build and submit the payment yourself. See [Anchor Mode](https://docs.etherfuse.com/guides/testing-offramps.md#anchor-mode-stellar-only). |## Verification| Term | Meaning | | - | - | | **KYC WebSDK** | The hosted verification flow: you create the customer and launch them, and they complete every step in the widget. See [KYC WebSDK](https://docs.etherfuse.com/guides/kyc-websdk.md). | | **KYC API** | Pushing a customer's personal data, documents and questionnaire answers over the API so they aren't asked for them again, then launching them only for what is left. See [KYC API](https://docs.etherfuse.com/guides/kyc-api.md). | | **Share token** | A single-use token minted in a partner's own Sumsub account that hands Etherfuse a verification the customer already passed, so documents *and* liveness transfer. Requires a data-sharing agreement. See [KYC Sumsub Shared Token](https://docs.etherfuse.com/guides/kyc-sumsub-shared-token.md). | | **Requirement** | One step in a customer's verification, named by its `type`, with a `status` and a `requiresLaunch` flag saying whether only the customer can satisfy it. Returned by `GET /ramp/customer/{customer_id}/kyc?requirements=true`. See [Tracking verification status](https://docs.etherfuse.com/guides/onboarding.md#tracking-verification-status). |## Organization & events| Term | Meaning | | - | - | | **Child organization** | A sub-organization you create (and can apply a partner fee to) on behalf of a partner or customer. | | **Webhook** | An HTTP callback delivering HMAC-signed event updates for orders, KYC, and bank accounts. See [Webhooks](https://docs.etherfuse.com/webhooks.md). | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.