TreasuryWire

The ledger behind your fintech wallet.

Your app owns the customer experience. TreasuryWire keeps the books underneath it: wallets, funding account numbers, deposits, payouts and fees, each one recorded as a balanced double entry in books only your business can see.

You start in test mode. Live is a switch away when you're ready.

Try a posting

Adaeze has ₦120,000.00 in her wallet and is on KYC Tier 1, capped at ₦300,000.00.

Change it and the entries update.

DrClearing, Flutterwave25,000.00
CrWallet, Adaeze25,000.00
BalancedDebits 25,000.00 = credits 25,000.00

Wallet after: ₦145,000.00. The deposit was checked with Flutterwave before it was credited.

What a wallet needs underneath

A wallet looks like a number on a screen. Behind it is a ledger that has to be right every time money moves.

A wallet for every customer
Create a wallet per customer in one call. Each gets its own funding account numbers from your bank providers, and a balance you can read at any moment.
Every movement is a double entry
A deposit, payout, transfer or fee always debits one account and credits another for the same amount. Nothing is added to a balance without a matching entry somewhere else.
A history you can trace
Every transaction lists its entries and the balance after each one. When a customer asks where their money went, you can show them.
Your own books, not the bank's
Providers move the money. The ledger records who owns what, so your numbers hold even when a provider's statement is late or wrong.

Where a wallet's balance goes wrong

A balance column on a users table works until the first bad day. The ledger is built for these days.

A webhook arrives twice
Every deposit is keyed on the provider's own event id. The second delivery is acknowledged and ignored, so the customer is credited once.
A payout times out
No answer isn't treated as a no. The debit stands until the bank confirms or fails the transfer, and only a confirmed failure is reversed.
Two payouts hit one wallet at once
The balance check and the debit happen in one step. One payout goes through and the other is refused. The wallet never goes below zero.
A deposit pushes someone past their KYC limit
The money has already arrived, so it isn't bounced. The excess is held in its own account and released when the customer upgrades.

One request per wallet movement

Create a wallet, send a payout, check a balance. Every request carries a key that belongs to your business and to test or live mode, so a test key can't touch real money and no one else can reach your books.

  • Retry safely. The same reference never sends money twice.
  • Know where a payout stands: pending, confirmed or failed, checked against the bank.
  • Deposits are verified with the provider before they're credited.

Send a payout

curl -X POST $API_URL/api/v1/payout/transfer \
  -H "Authorization: Bearer gl_test_…" \
  -d '{
    "ownerRef": "adaeze-0021",
    "currency": "NGN",
    "amount": 40000,
    "accountNumber": "0123456789",
    "bankCode": "058",
    "reference": "rent-march-0021"
  }'

Response

{
  "status": "OK",
  "message": "Transfer initiated",
  "reference": "rent-march-0021",
  "transactionId": "66f1c2…"
}

Made for money in Nigeria

The rules your compliance team already works to are built in, not bolted on.

CBN KYC tiers
Daily and balance limits for Tier 1, 2 and 3 are set up when you sign up, and checked on every deposit, payout and transfer.
BVN verification
Customers confirm their BVN on the provider's consent page. A verified BVN moves them to Tier 2 and releases anything held.
Naira to the kobo
Amounts are stored as whole kobo, never as floating-point numbers, so every total adds up exactly.
Your bank providers
Collections and payouts run through your own Flutterwave, Providus, Paystack or Rolla Pay account. Add a provider and your existing wallets can get its account numbers too.

Locked up where it counts

You hand us provider keys and the record of every naira. Here is how each is kept.

Provider keys are encrypted
Your bank provider credentials are sealed with AES-256-GCM, each one tied to your business. Copied to another account, they won't open.
We can't read your API keys
Only a SHA-256 hash of each key is stored, so a copy of the database doesn't hand anyone a working key.
Test keys stay in test
A test key can't touch live money, and a live key can't post to your test books.
Your books are yours alone
Every request is scoped to one business before it reads or writes a single entry. Other businesses can't see yours.

From signup to live wallets

  1. Create your ledger

    Enter your business name and an email. You get the books for your wallet product in test and live mode, and an owner login.

  2. Build against test mode

    Generate a test key in Settings, then create customer wallets and post deposits and payouts. Each one shows up in the back office as it lands.

  3. Go live

    Add your provider credentials and generate a live key. The same calls now move real money.

Give every wallet a ledger.

It takes a business name and an email. Your ledger is ready as soon as you sign up.

Create your ledger