> ## Documentation Index
> Fetch the complete documentation index at: https://api-docs.trypila.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> The terms that show up across the Pila API, in plain language.

<AccordionGroup>
  <Accordion title="AppId">
    The identifier of the app a request belongs to. Sent in the `AppId` header alongside your secret key on every call. Created from **Developers → Configuration** in the dashboard.
  </Accordion>

  <Accordion title="BIN">
    Bank Identification Number — the first six digits of a card number, which identify the issuing bank, the scheme and the card type. Look one up with [Resolve card BIN](/api-reference/cards/resolve-card-bin).
  </Accordion>

  <Accordion title="BVN">
    Bank Verification Number — the 11-digit identifier tied to an individual across all Nigerian banks. Required when creating an individual wallet.

    <Warning>A BVN is sensitive personal data. Never log it in full or store it in plain text — mask it as `*8901` anywhere it appears in your logs.</Warning>
  </Accordion>

  <Accordion title="Bank code">
    The short numeric code identifying a Nigerian bank, used as `recipient_bank_code` on transfers and `bank_code` on lookups. Get the current list from [Fetch banks](/api-reference/general-services/fetch-banks).
  </Accordion>

  <Accordion title="Corporate wallet">
    A wallet created for a registered company rather than an individual, using the business's RC number and details. See [Create a wallet](/api-reference/wallets/create-wallet#corporate-wallet).
  </Accordion>

  <Accordion title="Live">
    The production environment, at `https://api.trypila.co`. Real money, real customers, verified accounts only.
  </Accordion>

  <Accordion title="NUBAN">
    Nigeria Uniform Bank Account Number — the standard 10-digit account number. Every wallet you create has one, and money paid into it credits that wallet.
  </Accordion>

  <Accordion title="One-time-use account">
    A NUBAN issued for a single expected payment, useful for one-off checkouts where you do not want to keep an account open. See [Create a wallet](/api-reference/wallets/create-wallet#one-time-use-account).
  </Accordion>

  <Accordion title="Pool account">
    Your own Pila balance, as opposed to an individual customer wallet. Transfers can be funded from either by setting `source` on the request.
  </Accordion>

  <Accordion title="Route">
    The partner bank a wallet's account number is issued through. You choose it when creating the wallet, and it determines which bank name your customer sees.
  </Accordion>

  <Accordion title="Sandbox">
    The test environment, at `https://sandbox.trypila.co`. Same endpoints and payloads as live, but no real money moves.
  </Accordion>

  <Accordion title="Secret key">
    The private key sent in the `Authorization` header. There is a separate one per app per environment.

    <Warning>Backend only. Never ship a secret key in client-side code, and regenerate it immediately if it is exposed.</Warning>
  </Accordion>

  <Accordion title="Settlement">
    The point at which money actually reaches its destination. A transfer that returns `PROCESSING` has been accepted but not yet settled.
  </Accordion>

  <Accordion title="Transaction ID">
    The identifier returned by any money-movement call. Use it to poll [Transaction details](/api-reference/wallets/transaction-details), to deduplicate webhooks, and to quote a specific payment to support.
  </Accordion>

  <Accordion title="Virtual card">
    A USD card issued through the API with no physical counterpart. Fund it, freeze it, sweep it, or terminate it — see [Cards](/api-reference/cards/create-virtual-card).
  </Accordion>

  <Accordion title="Wallet ID">
    The UUID returned when you create a wallet. Almost every wallet and transfer call takes it as a parameter.
  </Accordion>

  <Accordion title="Webhook">
    An HTTP POST Pila sends to a URL you own when something happens — a deposit lands, a card is charged, a transfer settles. See [Subscribe](/api-reference/webhooks/subscribe) and [Webhook signatures](/api-reference/core-concepts/webhook-signatures).
  </Accordion>

  <Accordion title="x-pila-signature">
    The header on every webhook carrying an HMAC SHA256 signature of the payload, signed with your secret key. Verify it before acting on the event.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.