Sandbox Environment
The development environment athttps://api.dev.wava.co/v1 is a full sandbox that simulates payment processing without moving real money.
What is simulated
- Order creation and status transitions
- Payment gateway responses (push notifications, OTP codes, QR codes)
- Webhook delivery to your development endpoint
- All error scenarios
Getting started
- Create a development account at app.dev.wava.co (see Authentication).
- Get your development
merchant-keyfrom Settings > Integrations > API. - Point your API calls to
https://api.dev.wava.co/v1. - Use the test data values for phone numbers, national IDs, and OTP codes.
Gateway-specific testing behavior
Nequi (auto-confirm via GET)
In development, Nequi push notifications are simulated. To confirm a Nequi order, call the get order endpoint with the order ID. This call will automatically confirm the order and trigger the webhook.Daviplata (test OTPs)
Daviplata orders work the same as production, but use test OTP codes:| OTP Code | Result |
|---|---|
123456 | Success |
000000 | Success |
111111 | Success |
999999 | Error: invalid OTP |
| Any other value | Error: invalid OTP |
Breb
Breb orders return simulated QR codes and transfer keys. The order can be confirmed via polling or webhook.Differences from production
| Aspect | Sandbox | Production |
|---|---|---|
| Base URL | api.dev.wava.co/v1 | api.wava.co/v1 |
| Real payments | No | Yes |
| Nequi confirmation | Auto-confirm via GET /v1/orders/{id} | Buyer approves in Nequi app |
| Daviplata OTP | Test codes only | Real SMS OTP |
| Webhook delivery | To dev URL | To prod URL |
| Rate limits | Relaxed | Standard |
| Merchant key | Development key | Production key |