Skip to main content

​
Understand neobank terms

Use these definitions when reading the API, architecture, and deployment guides.
An operation state that requires the customer to complete a browser approval on the exact trusted Perflo application origin.
A customer-wide projection of safely classifiable cash and payment rows from agent and Perfolio transaction feeds. It is not a fiat-account ledger.
A short-lived, one-use local record that binds fresh customer authentication to the normalized payload of a sensitive action.
The deterministic, network-free adapter allowed in development and test.
An operation state used when Perflo may have accepted a provider write but the wrapper lacks definitive evidence. The worker never resubmits it.
The adapter that uses each customer’s Vault-encrypted Perflo device session against five exact reviewed HTTPS origins. It is the only production adapter.
Customer authority bound to one beneficiary, United States dollar caps, payment count, expiry, approved clients or rules, and atomic local rolling limits.
The asynchronous result record for every provider mutation. It stores safe request policy, resource links, state, uncertainty, and reconciliation scheduling.
A PostgreSQL event stored in the same transaction as an operation and idempotency record. A unique topic and aggregate pair prevents duplicate delivery.
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.
The generation identifier that binds local resources and operations to one customer Perflo connection. A later connection cannot reuse earlier resources.
Perflo authority binding a recipient destination, chain, United States dollar caps, payment count, and expiry. Browser approval activates the grant.
The derived Vault key named neobank-perflo-credentials, used to encrypt customer and operation provider context before storage in PostgreSQL.