Skip to content

Everything between “pay by transfer” and money in your bank

Yusr issues a one-time account number for every payment, confirms the transfer the moment it lands and settles your net amount. You integrate once; matching, notifications and settlement are done.

One account number per payment

Each transaction gets its own Nigerian bank account number that expires when the payment window closes. Because the account belongs to exactly one order, every transfer is matched without reading narrations.

  • Your name on the account

    The account name shows your business display name, so customers recognise who they are paying.

  • Expiry from 10 minutes to 72 hours

    30 minutes by default. Short for checkouts, longer for invoices.

  • Exact amounts in kobo

    Amounts are integers, and several transfers to the same account are summed.

  • No duplicates

    References are unique per account, and idempotency keys make retries safe.

Real customers do not always send the exact amount

Underpayments, overpayments and late transfers are detected, recorded and reported. Your account settings decide what happens next.

  • Paid

    The exact amount arrived before expiry. You are notified and the payment settles on schedule.

  • Underpaid

    Less than requested arrived. The amount received is recorded, the customer can top up, and your settings decide whether to accept or refund.

  • Overpaid

    More than requested arrived. The excess is flagged and handled according to your settings.

  • Late

    Money arrived after the account expired. It is never silently lost: it is recorded and accepted or refunded per your settings.

  • Expired

    No transfer arrived in time. Release the stock or create a new transaction for another attempt.

Know the moment money lands

Three channels, one payload. Webhooks are the source of truth for fulfilment, the live event updates the checkout page, and polling is the fallback.

Confirmation channels compared
WebhookRealtimePolling
What it isHTTPS POST signed with HMAC-SHA256 over a timestamp and the raw bodyA socket subscription to one transaction (browser) or every event (server)GET the transaction by id, or find it by your reference
DeliveryAt least once, retried with backoff for about 22 hoursCurrent state is sent on every connect and reconnectEvery 5 seconds is recommended; rate limited
ToolsDelivery log and one-click resend in the dashboardShort-lived client tokens keep secret keys off the browserStable error codes and request ids

Split at source, settled to your bank

Each collection is split as it is booked: the fee comes off and your share is credited to your balance. Settlement pays the net amount to your verified bank account.

  • T+0 or T+1 schedules

    Agreed during onboarding, with a minimum settlement amount.

  • Verified payouts only

    Your settlement account is confirmed by name enquiry before you go live.

  • Clear statements

    Gross, fees, net and the transactions in every batch, as CSV and by API.

  • Double-entry ledger

    Behind every balance, reconciled daily.

Settlement, 6 Oct 2026

Transactions
3
Gross collected
₦75,000.00
Fees (1.5%)
−₦1,125.00
Net to your bank
₦73,875.00

Illustrative figures.

A dashboard for finance, support and developers

Everyone on your team gets the view they need, with test and live mode clearly separated.

  • Collections at a glance

    Today, 7-day and 30-day collections, success rate, pending settlement and recent transactions.

  • Find any payment

    Search by your reference, transaction id, account number, customer email or amount, and follow each payment’s timeline.

  • Webhook delivery log

    Every attempt with status code, latency and response. Resend an event or send a signed test event in one click.

  • CSV exports

    Download transactions and settlements for your accounting tools.

  • Team roles

    Owner, Admin, Developer, Support and Viewer, with two-factor sign-in required for Owners and Admins.

  • Audit log

    Key rolls, webhook changes, settings and team changes are recorded with who, what and when.

Test every scenario before you go live

Test keys are issued the moment you sign up. The sandbox runs on our own simulator, so it is fast and behaves like production: same API, same webhooks, same live events.

  • Simulate every outcome

    Paid, underpaid, overpaid, late and expired, from the API or with one click in the dashboard.

  • Separate data

    Test and live data never mix. Test-mode objects are invisible to live keys.

  • Go live when ready

    Submit your business verification from the dashboard. Live keys are issued once it is approved.

Start collecting bank transfers

Create an account, copy your test keys and make your first sandbox transaction in minutes. Go live once your business is verified.