Testing & Sandbox Simulator

You can test your entire payment, disbursement, and webhook flow in the Pycer Sandbox without moving real funds. Toggle Sandbox Mode in your Pycer Portal under Gateways & Currencies → Payment Gateways and use the test credentials below.

1. Pycer Express Prompt & Mobile Wallet Test Numbers

Use these test mobile numbers when calling POST /api/v1/rails/express-prompt or POST /api/v1/payments in sandbox mode:

Test Phone Number	Test PIN	OTP	Simulated Outcome
`+254700000001`	`1234`	`123456`	Success — Instant `payment.completed` callback
`+254700000002`	`1234`	`123456`	Delayed Success — Completes after 10 seconds
`+254700000003`	`0000`	`123456`	Customer Cancelled — User dismissed prompt (`resultCode: 1032`)
`+254700000004`	`1234`	`123456`	Insufficient Balance — Declined (`resultCode: 1`)
`+254700000005`	`9999`	`123456`	Invalid PIN — Declined (`resultCode: 2001`)
`+254700000006`	`1234`	`123456`	Prompt Timeout — Expired (`resultCode: 1037`)

2. Pycer Card Switch Test Cards

Use these test card numbers on the Pycer Checkout page when testing card acquiring in Sandbox Mode:

Card Number	Network	CVC	Expiry	Simulated Outcome
`4242 4242 4242 4242`	Visa	Any 3 digits	Any future date	Approved (Frictionless)
`4000 0025 0000 3155`	Visa	Any 3 digits	Any future date	3D Secure 2.2 Challenge Required
`5555 5555 5555 4444`	Mastercard	Any 3 digits	Any future date	Approved
`4000 0000 0000 0002`	Visa	Any 3 digits	Any future date	Declined (Generic Decline)
`4000 0000 0000 9995`	Visa	Any 3 digits	Any future date	Declined (Insufficient Funds)

3. Pycer Inter-Bank Switch Test Accounts

Use these test account numbers when testing real-time bank transfers (POST /api/v1/rails/bank-transfer) or merchant payout sweeps (POST /api/v1/merchants/settlement/sweep):

Account Number	Bank Code	Outcome
`0100000001`	`PYCER_BANK_01`	Instant Settlement (`00`)
`0100000002`	`PYCER_BANK_01`	Account Name Mismatch (`14`)
`0100000099`	`PYCER_BANK_01`	Account Frozen / Compliance Hold (`62`)

4. Creating a Test Payment via REST API

curl -X POST https://pycer.quantivogroup.com/api/v1/payments \
  -H "Authorization: Bearer $PYCER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "100.00",
    "currency": "KES",
    "customer_email": "sandbox@pycer.quantivogroup.com",
    "customer_phone": "+254700000001",
    "description": "Pycer Sandbox Test Order",
    "metadata": { "environment": "sandbox" }
  }'

Use the returned checkout_url to complete the interactive test flow, or inspect the instant webhook callback dispatched to your server.

5. Simulating Webhooks

From the Pycer Developer Portal

Sign in at https://pycer.quantivogroup.com/login
Navigate to Security & Access → Developer Hub (/admin/developer)
Under Webhooks, click Test Webhook next to your registered endpoint
Select an event type (payment.completed, payment.failed, refund.completed)
Pycer dispatches a live HTTP POST with a valid X-Pycer-Signature HMAC-SHA256 header and displays the response status and latency.

Via REST API

curl -X POST https://pycer.quantivogroup.com/api/v1/webhooks/tests \
  -H "Authorization: Bearer $PYCER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-app.com/webhooks/pycer",
    "event": "payment.completed"
  }'

Getting Started

SDKs & Libraries

Plugin System

Building Plugins

Translations

AI Tools

Testing & Sandbox Simulator

Testing & Sandbox Simulator

1. Pycer Express Prompt & Mobile Wallet Test Numbers

2. Pycer Card Switch Test Cards

3. Pycer Inter-Bank Switch Test Accounts

4. Creating a Test Payment via REST API

5. Simulating Webhooks

From the Pycer Developer Portal

Via REST API

Testing & Sandbox Simulator

1. Pycer Express Prompt & Mobile Wallet Test Numbers

2. Pycer Card Switch Test Cards

3. Pycer Inter-Bank Switch Test Accounts

4. Creating a Test Payment via REST API

5. Simulating Webhooks

From the Pycer Developer Portal

Via REST API

Related Pages