Skip to main content
Glyde’s sandbox environment lets you build and test your integration without processing real money. Sandbox behaves identically to production, so you can validate your entire payment flow before going live.

​
Sandbox Environment

All sandbox transactions are simulated—no real money moves, and no real bank accounts are affected.

​
Getting Sandbox Credentials

  1. Log in to your dashboard at app.useglyde.co
  2. Toggle to Sandbox mode (usually in the top navigation)
  3. Go to Settings → API Configuration
  4. Copy your sandbox API keys

​
Test Bank Accounts

Use these test accounts to simulate different transfer scenarios:

​
Successful Transfer

Transfers to this account will succeed after a brief processing period.

​
Failed Transfer

Transfers to this account will fail, allowing you to test error handling.

​
Test Bill Payments

Sandbox bill payments are answered by Glyde and never reach a real biller. Purchases settle immediately as successful or failed, never pending, and send the matching bill.* webhook.

​
Test billers and products

Every data biller returns the bundles mtn-1gb-30days (₦500) and mtn-2gb-30days (₦1,000). Every cable biller returns the bouquets dstv-compact (₦19,000) and dstv-premium (₦44,500). Network Lookup always resolves to mtn / mtn-airtime. Meter and Smartcard Enquiry return the customer name Glyde Test Customer. Successful electricity purchases return the token 1234-5678-9012-3456-7890 and 42.5 kWh.

​
Failing customers

Use these numbers to test failures. Lookups for them return 422, and purchases for them return "status": "failed" and send bill.failed: Any other valid number succeeds.

​
What to Test

Build confidence in your integration by testing these scenarios:

​
Payment Collection

  • Create a checkout session and complete payment
  • Test both card and bank transfer channels
  • Verify webhook delivery when payment completes
  • Handle expired or abandoned payments

​
Transfers

  • Verify bank accounts before sending
  • Initiate transfers and confirm webhook receipt
  • Test insufficient funds scenarios
  • Handle duplicate reference errors

​
Bill Payments

  • List billers, bundles and bouquets
  • Validate meters and smartcards before buying
  • Buy airtime, data, electricity and cable, and confirm webhook receipt
  • Handle failed purchases with the failing customer numbers

​
Virtual Accounts

  • Create static and dynamic accounts
  • Simulate incoming payments
  • Test account deactivation
  • Verify transaction history

​
Error Handling

  • Invalid API keys
  • Malformed requests
  • Missing required fields
  • Network timeouts

​
Webhook Testing

Webhooks work the same in sandbox as in production. To receive webhooks during local development:
  1. Use a tunneling service like ngrok to expose your local server
  2. Configure the tunnel URL as your webhook endpoint in the dashboard
  3. Process test transactions and verify webhooks arrive

​
Going Live Checklist

Before switching to production, verify:
1

All Flows Tested

You’ve successfully tested payments, transfers, and webhooks in sandbox.
2

Error Handling Works

Your integration gracefully handles all error scenarios.
3

Webhooks Configured

Your production webhook URL is set and your server is ready to receive events.
4

Keys Updated

You’ve replaced sandbox keys with production keys (sk_ prefix).
5

URL Updated

Your base URL points to https://api.useglyde.co/v1.
6

Logging Enabled

You’re logging API requests and responses for debugging.

​
Sandbox Limitations

A few things behave differently in sandbox:
  • Wallet balance — You have unlimited test funds
  • Processing time — Transactions complete faster than in production
  • Bank verification — Only test accounts can be verified
  • Webhooks — May have slight delays compared to production
These differences don’t affect your integration logic—code that works in sandbox will work in production.