Overview
The KillB Sandbox environment allows you to test your integration without processing real transactions or moving actual funds.All sandbox transactions use fake money. No real funds will be transferred or charged.
Environments
- Sandbox (Testing)
- Production (Live)
Base URL:
https://teste-94u93qnn.uc.gateway.devFeatures:- Test with fake money
- Simulate payment flows
- No real KYC verification required
- Instant transaction processing
- Full API functionality
- Development and testing
- Integration verification
- Demo applications
- CI/CD testing
Getting Started with Sandbox
Step 1: Get Sandbox Credentials
- Sign up at otc.killb.com
- Navigate to Settings → API Keys
- Create a Sandbox API Key
- Note your sandbox email and password
Step 2: Set Environment Variables
.env
Step 3: Authenticate
Testing Features
Faker Endpoints
Sandbox provides special endpoints to simulate payment events:Fake Cash-In
Fake Cash-In
Simulate a user completing a fiat payment (PSE, SPEI, etc.)Request:What it does:
- Marks the cash-in as completed
- Triggers conversion process
- Moves ramp to next status
Fake Cash-Out
Fake Cash-Out
Simulate completion of crypto-to-fiat conversionRequest:What it does:
- Completes the cash-out process
- Marks ramp as COMPLETED
- Triggers webhooks
Testing Workflows
Complete On-Ramp Test
1
Create Test User
Use any valid-looking data - no real verification in sandbox
2
Create Wallet Account
Use any valid wallet address format
3
Create Quotation
Get a test quote with sandbox rates
4
Create Ramp
Execute the ramp transaction
5
Simulate Payment
Use
/api/v2/faker/cash-in to simulate user payment6
Verify Completion
Check ramp status moves to COMPLETED
Complete Off-Ramp Test
1
Create Test User
Same as on-ramp flow
2
Create Bank Account
Use test bank details
3
Create Quotation
Quote from USDC to COP/MXN
4
Create Ramp
Execute the ramp with crypto source
5
Simulate Completion
Use
/api/v2/faker/cash-out to complete the process6
Verify Status
Confirm status is COMPLETED and webhooks fired
Test Data
Test Bank Accounts (Colombia)
| Bank Name | Bank Code | Account Type |
|---|---|---|
| Bancolombia | 0001 | savings, checking |
| Banco de Bogotá | 0002 | savings, checking |
| Davivienda | 0003 | savings, checking |
Test Bank Accounts (Mexico)
| Bank Name | Bank Code | CLABE Format |
|---|---|---|
| BBVA | 012 | 012XXXXXXXXXXXXXXXXX |
| Santander | 014 | 014XXXXXXXXXXXXXXXXX |
| Banorte | 072 | 072XXXXXXXXXXXXXXXXX |
Test Wallet Addresses
These are example addresses for testing. In sandbox, any validly-formatted address will work.
Sandbox Limitations
| Feature | Sandbox | Production |
|---|---|---|
| Real money | ❌ No | ✅ Yes |
| KYC verification | ❌ Simulated | ✅ Real verification |
| Payment processing | ⚡ Instant | ⏱️ Real timing |
| Transaction limits | ♾️ No limits | ✅ Based on KYC |
| Webhooks | ✅ Yes | ✅ Yes |
| API rate limits | 🔓 Relaxed | 🔒 Enforced |
Debugging in Sandbox
Enable Verbose Logging
Monitor Ramp Status
Switching to Production
When you’re ready to go live:1
Update Base URL
Change from
teste-94u93qnn.uc.gateway.dev to killb.app2
Use Production Credentials
Replace sandbox credentials with production API keys
3
Remove Faker Calls
Remove all calls to
/api/v2/faker/* endpoints4
Implement Real KYC
Handle actual KYC verification and document uploads
5
Add Error Handling
Implement production-grade error handling and logging
6
Enable Monitoring
Set up monitoring and alerting for your integration
Testing Checklist
Before going to production, test these scenarios:Happy Path
Happy Path
- User creation and KYC
- Account creation (bank and wallet)
- Quotation generation
- On-ramp completion
- Off-ramp completion
- Webhook reception
- Receipt generation
Error Scenarios
Error Scenarios
- Expired quotation handling
- Invalid account details
- Insufficient balance
- Failed payment simulation
- Network errors
- Token expiration
- Invalid webhook signatures
Edge Cases
Edge Cases
- Very small amounts (< $1)
- Very large amounts (> $10,000)
- Concurrent transactions
- Rate limiting
- Duplicate prevention (externalId)
- Multiple accounts per user