Sandbox Environment
The Eclipse sandbox is a fully functional environment that mirrors production behaviour in all API responses, validations, and workflows. No real money moves and no real payment rails are invoked, but every API call behaves exactly as it would in production.
When your tenant is provisioned, the sandbox comes with a set of pre-configured defaults so you can start making API calls on day one without manual setup.
What's Pre-configured
Wallet Types
Three wallet types are available immediately:
| Type | Purpose |
|---|---|
| System Wallet | Tenant-owned wallets for float, settlement, and operational funds |
| Digital Wallet | Customer-facing wallets for balance, transfers, and withdrawals |
| Card Wallet | Wallets with card issuance enabled — linked to a virtual or physical card |
Pre-funded Wallets
| Wallet | What it's for |
|---|---|
| Tenant root system wallet | Holds float funds for the tenant |
| Source system wallets | Pre-funded — use these as the source for customer wallet top-ups |
| Tenant digital wallet | Pre-funded — use this to test wallet-to-wallet transfers |
Permissions
A default permission set is configured for typical development scenarios, including customer management, wallet operations, card issuance, and payment processing. Permissions can be refined before production.
Payment Types
All hosted checkout payment types are enabled on sandbox. You can generate payment links and process test card payments without any additional configuration.
Admin User
An admin user is created as part of tenant provisioning. This user has full access to both the Eclipse Admin Portal and the APIs.
Credentials
You'll receive the following from the Eclipse onboarding team:
| Value | What it is |
|---|---|
tenantId | Your tenant identifier — used in every API path |
identity | Your admin user login (typically an email address) |
password | Your admin user password |
baseUrl | Your sandbox base URL |
sourceWalletId | The pre-funded source wallet for customer top-ups |
Contact [email protected] if you don't have these.
Admin Portal
The Eclipse Admin Portal is available at {baseUrl}/admin-portal. It uses the same APIs that are available externally — every action in the portal is an API call you could make directly.
The portal is useful for:
- Exploring what API payloads look like before writing code
- Browsing your tenant's wallet types, wallets, and customers
- Testing operations manually without needing to write a request
Test Cards
Use these card numbers for acquiring and top-up testing in the sandbox:
| Card number | Network | Use |
|---|---|---|
4242 4242 4242 4242 | Visa | Successful payment |
2223 0015 0000 0018 | Mastercard M4M | Successful payment |
Any future expiry date and any 3-digit CVV are valid for all test scenarios.
Full test card reference, including QR codes, ATM withdrawals, and acquiring scenarios: Sandbox Testing Accounts.
Where to Start
Once you have credentials, follow the quickstart that matches what you're building:
| Quickstart | Covers |
|---|---|
| Digital Wallets and KYC | Authenticate, onboard a customer, open a wallet, fund it, run KYC |
| Card Issuance | Issue a virtual card, set a PIN, inspect card activity |
| E-Commerce Acquiring | Generate a payment link, accept a card payment, receive a settlement callback |