Guides
Go live with confidence.
Move from simulated outcomes to controlled, verified live payments.
Before your first live request
- Use an active, approved business account with API access enabled.
- Complete verified bank payout setup before disbursements.
- Keep secrets on the server and persist an idempotency UUID with each payment.
- Display the quoted payer charge or wallet debit before requesting payment.
- Verify webhook signatures, environment, event IDs and payment versions.
- Test success, failure, timeout and repeated callbacks in the sandbox.
Switch the key, keep the interface
Use the same API base URL with your np_live_ secret. The secret chooses the environment. Test references are not visible with live keys. Simulation is unavailable for live secrets.
Confirm outcomes and reconcile
| Status | What it means | What to do |
|---|---|---|
process | Accepted, pending, or under Finance review. | Wait for a newer webhook or read the transaction. |
success | The payment is confirmed. | You can fulfil the order. |
failed | The payment failed. | Inspect the result. A failed payout reports its refund state. |
Keep the NuePay reference, your merchant reference and support request IDs. A pending or uncertain result should be reconciled using the existing payment, rather than dispatched again as a fresh request.
Your live balances, provider availability, account freezes and payout readiness determine which new operations can be accepted.