Sandbox Environment
| Setting | Value |
|---|---|
| Base URL | https://sandbox.useglyde.co/v1 |
| API Key Prefix | sk_sandbox_ |
Getting Sandbox Credentials
- Log in to your dashboard at dashboard.useglyde.co
- Toggle to Sandbox mode (usually in the top navigation)
- Go to Settings → API Configuration
- Copy your sandbox API keys
Test Bank Accounts
Use these test accounts to simulate different transfer scenarios:Successful Transfer
| Field | Value |
|---|---|
| Account Number | 0264341458 |
| Bank Code | 058 |
| Account Name | Glyde Transfer 1 |
Failed Transfer
| Field | Value |
|---|---|
| Account Number | 49214898 |
| Bank Code | 059 |
| Account Name | Glyde Transfer 2 |
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
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:- Use a tunneling service like ngrok to expose your local server
- Configure the tunnel URL as your webhook endpoint in the dashboard
- Process test transactions and verify webhooks arrive
Going Live Checklist
Before switching to production, verify: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