Skip to content

Developer sandbox ​

Develop and test against https://sandbox-api.keshless.com. This environment has its own database, test credentials, simulated balances, transaction history and webhook queue. Existing integrations keep their current URLs and credentials.

Create your workspace in the developer dashboard. Choose a workspace name, email and password to submit an access request. An administrator must approve your workspace before you can use sandbox tools or create your own kl_test_ integration key. Approval grants E250 in simulated merchant funds once. After approval, choose Create test key in the dashboard. Save the key when it is shown; you can rotate or revoke it in the dashboard.

Keep the kl_test_ integration key on your server. A sandbox key never authorizes live operations, and live keys do not work in this sandbox. All workspaces use the same API endpoint, so you do not need an individual subdomain.

The dashboard also lets you create test customers, refill simulated balances, run payments and refunds, configure webhook receivers and inspect captured SMS.

Test payments and failures ​

Use the quick start to obtain your merchant-owned test customers and exercise payments, status lookups and refunds. The fixtures cover verified customers, payments with a PIN, insufficient funds and unverified customers. Their test PIN is 1234. Payments above E50 require a PIN; every supplied PIN is checked, including for smaller payments.

The sandbox uses the same payment logic, retries and signed webhook format as the integration API. Its initial fees are zero. Live fees, funding and settlement require separate verification. All sandbox funds are simulated.

Refill test funds ​

bash
curl -X POST https://sandbox-api.keshless.com/api/integration/sandbox/funds \
  -H 'X-API-Key: YOUR_SANDBOX_KEY' \
  -H 'Idempotency-Key: test-customer-refill-1' \
  -H 'Content-Type: application/json' \
  -d '{"amount":50,"customerId":"YOUR_FIXTURE_CUSTOMER_ID"}'

Omit customerId to refill the merchant's simulated balance. A refill can add up to E5,000 within the wallet cap. Reusing the same retry key and body returns the previous outcome; a changed body returns 409. You cannot fund another merchant's customers. Fixture requests return the current balances without resetting them.

Test SMS without sending messages ​

bash
curl -X POST https://sandbox-api.keshless.com/api/integration/sms \
  -H 'X-API-Key: YOUR_SANDBOX_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"to":"+26876000000","message":"Your test code is 123456"}'

curl https://sandbox-api.keshless.com/api/integration/sandbox/messages \
  -H 'X-API-Key: YOUR_SANDBOX_KEY'

Messages are stored in your merchant's sandbox inbox. The send response explicitly reports simulated: true and delivery: "CAPTURED". No SMS reaches the phone. The inbox supports limit and offset and is private to your merchant.

Webhooks and going live ​

The fixture response provides a signature-checking receiver on the sandbox host. You can also configure your own public HTTPS test receiver. Events are marked environment: "sandbox"; treat them as test events even when received on your own infrastructure. Delivery failures remain visible in webhook history.

The sandbox does not expose real cash withdrawals, card/operator funding, KYC uploads or live provider callbacks. Going live requires explicit activation and separate live credentials. Test keys, balances and events never become live money or sales. Existing integrations continue using their current settings.

Keshless payment integration documentation