Going live#
Your sandbox integration and your live integration are the same code. Going live means verifying your business, swapping in live keys and live webhook endpoints, and checking that your integration handles every outcome. Work through this page from top to bottom.
1. Verify your business#
Submit your business verification (KYC) from the dashboard under Go live. Have these ready:
| Item | Details |
|---|---|
| Business type | How your business is registered. |
| CAC registration | Your CAC registration number and a copy of the CAC certificate (required). |
| Director | The director's full name and BVN or NIN. Only the last four digits are shown back to you. |
| Business address | Your registered or trading address. |
| Website | Where you sell, if you have one. |
| Expected monthly volume | Your estimated monthly collections, used to set appropriate limits. |
| Supporting documents | Optional: director ID, proof of address, memorandum and articles of association (MEMART), and any other document that helps the review. |
You also need a settlement bank account (see the next step) before you can submit.
Review statuses#
| Status | What it means |
|---|---|
draft | You are still filling in the form. Your answers and uploads are saved as you go. |
submitted | Your submission is queued for review. |
in_review | Our compliance team is reviewing it. |
changes_requested | The reviewer needs more information. Their notes are shown in the dashboard; update and resubmit. |
approved | You are verified. Live mode and live keys are enabled. |
rejected | The application was declined. The reviewer's notes explain why. |
We email you when the status changes.
2. Add your settlement account#
Under Settings → Settlement account, choose your bank and enter the account number. Yusr checks the account name with the bank (name enquiry) and shows it to you before you save. Settlements are paid only to this verified account. Only Owners and Admins can change it. See Settlements and fees for the schedule.
3. Get your live keys#
Once you are approved:
- In the dashboard, switch the mode toggle from Test to Live.
- Open Developers → API keys and roll the live secret key to generate a new
sk_live_…you can copy. Secret keys are stored only as a hash, so the full key is shown only once: store it in your secrets manager straight away. - Put it in your production configuration, for example as
YUSR_SECRET_KEY, and keepsk_test_…in development and staging.
Your code does not change: the key decides the mode. Confirm that the live key works with a read-only call. The
response's mode is live:
4. Register live webhook endpoints#
Test and live are separate worlds: webhook endpoints, signing secrets, events and transactions all belong to one mode. Your sandbox endpoints never receive live events.
- Add your production endpoint in Live mode under Developers → Webhooks, or call
POST /v1/webhookswith your live key. - Live endpoints must use HTTPS and resolve to a public IP address.
- Store the live endpoint's signing secret separately from the test one; it is shown only when the endpoint is created or its secret is rolled.
- Use Send test event to check that your endpoint verifies the signature and answers
2xxwithin 10 seconds.
See Webhooks for signature verification, retries and the event list.
5. Lock down your keys#
- IP allowlist. Add your servers' public IP addresses to your live secret key under Developers → API keys.
Requests from any other address get
403 ip_not_allowed. - Roll without downtime. When you rotate a key, choose an overlap of up to 24 hours so the old and new key both work while you deploy. See Authentication.
- Two-factor authentication. Owners and Admins must use 2FA to sign in; encourage everyone else to turn it on.
- Least privilege. Invite teammates with the narrowest role that fits. See Team roles.
Production readiness checklist#
Before you announce the new payment option, confirm each item:
- Business verification approved and settlement account verified.
-
sk_live_…stored in your secrets manager, only on your servers, never in source control. - Live webhook endpoint registered over HTTPS, subscribed to every event you handle.
- Webhook signatures verified on the raw request body, with the 5-minute timestamp tolerance.
- Events deduplicated by event
id, because delivery is at least once. - Your handler answers
2xxwithin 10 seconds and queues slow work. - Every status handled:
paid,underpaid,overpaid,expired,late_payment,reversed,cancelledandfailed. See Transactions. - Payment behaviour settings for underpayments, overpayments and late payments chosen under Settings.
- Every create request sends an
Idempotency-Key, and retries reuse it. - Your checkout shows
payment.amount, the account number, bank name, account name and a countdown topayment.expires_at. See Displaying payment details. - Polling, if you use it, runs every 5 seconds at most and stops on a final status.
- Errors are logged with their
request_id. See Errors. - IP allowlist set on the live secret key.
- Team members invited with the right roles, Owners and Admins using 2FA.
- A small real transfer completed end to end: account issued, transfer made, webhook received, order fulfilled.
After launch#
- Watch Developers → Webhooks for failing deliveries; failed events can be resent from the dashboard or with
POST /v1/events/{id}/resend. - Check Developers → Logs, which keeps 30 days of API requests with their status and request ID.
- Download settlement reports from Settlements to reconcile payouts with your books.
- Keep your sandbox integration: test changes there before you deploy them.