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

# Glossary

> Define the identity, operation, approval, mandate, adapter, and provider terms used by the neobank.

# Understand neobank terms

Use these definitions when reading the API, architecture, and deployment guides.

<AccordionGroup>
  <Accordion title="action required">
    An operation state that requires the customer to complete a browser approval on the exact trusted Perflo application origin.
  </Accordion>

  <Accordion title="activity">
    A customer-wide projection of safely classifiable cash and payment rows from agent and Perfolio transaction feeds. It is not a fiat-account ledger.
  </Accordion>

  <Accordion title="confirmation intent">
    A short-lived, one-use local record that binds fresh customer authentication to the normalized payload of a sensitive action.
  </Accordion>

  <Accordion title="fake adapter">
    The deterministic, network-free adapter allowed in development and test.
  </Accordion>

  <Accordion title="indeterminate">
    An operation state used when Perflo may have accepted a provider write but the wrapper lacks definitive evidence. The worker never resubmits it.
  </Accordion>

  <Accordion title="live adapter">
    The adapter that uses each customer’s Vault-encrypted Perflo device session against five exact reviewed HTTPS origins. It is the only production adapter.
  </Accordion>

  <Accordion title="mandate">
    Customer authority bound to one beneficiary, United States dollar caps, payment count, expiry, approved clients or rules, and atomic local rolling limits.
  </Accordion>

  <Accordion title="operation">
    The asynchronous result record for every provider mutation. It stores safe request policy, resource links, state, uncertainty, and reconciliation scheduling.
  </Accordion>

  <Accordion title="outbox">
    A PostgreSQL event stored in the same transaction as an operation and idempotency record. A unique topic and aggregate pair prevents duplicate delivery.
  </Accordion>

  <Accordion title="Perflo capability request">
    A requested upstream contract improvement. Current requests cover customer-bound Know Your Customer sessions, fiat provisioning and ledgers, executable remittance, idempotency, signed events, mandate enforcement, and card lifecycle.
  </Accordion>

  <Accordion title="provider binding">
    The generation identifier that binds local resources and operations to one customer Perflo connection. A later connection cannot reuse earlier resources.
  </Accordion>

  <Accordion title="recipient grant">
    Perflo authority binding a recipient destination, chain, United States dollar caps, payment count, and expiry. Browser approval activates the grant.
  </Accordion>

  <Accordion title="Transit key">
    The derived Vault key named `neobank-perflo-credentials`, used to encrypt customer and operation provider context before storage in PostgreSQL.
  </Accordion>
</AccordionGroup>