Posteering

Wallet

Posteering's stored-value rail. Customer-owned, provider-held wallets with a real account number — create, fund, spend, and move balances through one neutral protocol.

The stored-value rail

Wallet is Posteering's stored-value capability: a customer-owned account that holds a balance and moves it — the sibling of Bankrail ("collect and transfer") and Vending ("vend a good"). Each wallet is an independent, provider-held account with its own real account number a customer can fund directly.

The balance never pools in Posteering. It lives in a licensed institution's account — one real account per customer, BVN-KYC'd, with the bank as custodian of record. Posteering directs moves against that account; it is never the custodian.

What it gives you

  • Create a wallet — provision a customer-owned wallet. Returns a wallet handle and a real, fundable account number.
  • Balance — read a wallet's available balance.
  • Credit — fund a wallet (where the provider supports merchant-initiated credit).
  • Debit — spend from a wallet (approval-gated per provider).
  • Transfer — move value between two wallets on the same provider.
  • External send — pay out to a named external bank account.
  • Callbacks — signed notifications when funds land or a move settles.

The provider is data

A wallet is backed by a provider (Xpress Wallet today, backed by Providus). The provider name is data, never a code path — its auth, field names, and unit conventions live inside its adapter. Adding a provider changes nothing in the wallet contract. You integrate the neutral wallet vocabulary; the provider is a deployment detail.

Amounts are always kobo (integer minor units).

Base URL

https://api.posteering.com/api/v1/wallet

Through the One API

Reach Wallet the same way you reach any product — through the One API's passthrough (/products/wallet/passthrough/...) and provisioning (/products/wallet/provision). The One API stays agnostic; this doc defines the wallet shapes it threads through untouched. See Create a wallet for the KYC fields provisioning requires.

On this page