Going live
Bring your integration to customers with the right keys, verified transactions and a clear plan for every outcome.
Work through these checks before accepting live purchases. Your app should be able to confirm an order, keep an unresolved purchase pending and help a customer when something needs attention.
Switch the host, key and customer details.
https://api.strongmb.ng/v1
Use your sk_live_ secret key on the server with Authorization: Bearer YOUR_LIVE_SECRET_KEY.
Fetch current products from the live API and use the actual customer details. Use real product codes and customer details in production.
Live purchases use real funds. Confirm the customer, product and price before submitting. Keep the original reference for verification.
Finish failure testing before going live
Use the sandbox fixtures and response examples to verify that your app handles rejected requests, failed purchases and pending outcomes separately. Keep processing orders pending; never treat a timeout as proof of failure.
Connect your production account
Check the account and environment your server will use.
- Use your live secret key
Load your
sk_live_key from secure server configuration. Keep it out of browser code, mobile bundles and logs. Public keys and webhook tokens are not supported for authentication in this version. - Confirm the account
Call
GET /userwith your live configuration and confirm that it returns the intended, active account. - Check your wallet
Read your wallets and identify
primary_ngn. Review its balance, status and limits before accepting live purchases.
Prepare the purchase flow
Make the customer details and order reference reliable.
- Confirm the product and recipient
Use current product codes and prices. For electricity or cable TV, validate the meter or smart card and let the customer confirm the returned details.
- Save before sending
Persist a unique reference and the intended purchase details before submitting the request. Prevent repeated submissions while an order is pending.
- Handle all three outcomes
Read
data.status:successful,processingorfailed. A timeout is an unknown outcome, not proof of failure.
Keep orders up to date
Treat notifications as a prompt to verify the current result.
- Configure your live webhook URL
Save an HTTPS endpoint in Developer settings. Keep your live and test handling separate.
- Verify the reference
Webhook-token verification is not active in this version. Query the incoming reference with your secret key and compare the returned transaction with your saved order.
- Apply each outcome once
Use an atomic order update to prevent duplicate fulfillment. Keep processing purchases pending; do not refund while the transaction may still become successful.
Make problems traceable
Keep enough information to investigate without exposing secrets.
- Record useful diagnostics
Save the purchase reference, metadata code, trace ID, timestamp and environment. Redact secrets and unnecessary customer details.
- Watch unresolved purchases
Monitor processing orders and failures. Keep a way to query an order by its original reference and contact support when an outcome remains unresolved.
Start small. Verify the whole experience.
Run a controlled live purchase with an intended recipient. Live purchases use real wallet funds. Confirm the receipt, wallet movement and transaction lookup, then monitor your first customer orders.
Keep a way to pause new purchases if a product becomes unavailable, while continuing to reconcile existing orders.
Questions? Let’s work through them.
Having an issue or need help with your integration? Join the Strongmb Slack community to ask questions and get assistance from our team and other developers.
Keep API keys and customer details private when sharing examples.
Experiencing a service issue? Check Strongmb’s service status for incident updates.
Did this page help you?
Up to 100 characters. Please leave out personal details, account information and API keys.