Get started
Sandbox and going live
Build and test against the sandbox with the same API you will use in production, then switch base URL and keys.
The sandbox runs the same code as production against test banking and biller providers. No real money moves.
Environments
| Sandbox | Live | |
|---|---|---|
| API base URL | https://staging.lint.finance/api/partner/v1 | https://api.lint.finance/api/partner/v1 |
| Dashboard | sandbox.lint.finance | lint.finance |
| Money | Test funds only | Real naira |
| Keys | Created in the sandbox dashboard | Created in the live dashboard |
Keys, customers, wallets and webhooks are separate in each environment. A sandbox key returns 401 unauthenticated against the live API.
Testing tools
Simulated payments. POST /payments/virtual-accounts/{id}/simulate-transfer pays into a sandbox virtual account as if a customer had sent a bank transfer, and fires the webhook. In live it does nothing.
Test bank accounts. Sandbox payouts and name enquiry only resolve accounts at the sandbox bank, bank code 999240. Account 5010880910 resolves, so you can use it to try name enquiry and payouts. A made-up account number fails with account_resolution_failed, exactly as it would live.
Bills. Bill payments run against the providers' test environments. Some orders come back PENDING first and settle a few minutes later, which is a good way to exercise your webhook handling.
Identity. In the sandbox, BVN checks run against the provider's test service; complete them with OTP 123456.
Going live
- Complete business verification on lint.finance, including BVN.
- Create a live application under Integrations → Applications and store the new credentials.
- Register your production webhook endpoint under Integrations → Webhooks and copy the live signing secret — it differs from the sandbox one.
- Change your base URL to
https://api.lint.finance. - Fund your live wallet before sending payouts or paying bills; both are paid from it.
Never point a sandbox key at the live API or the other way round in the same deploy. Keep base URL, client ID, client secret and signing secret together in one per-environment config.