Skip to main content

Provider Sandbox testing

SkyPay Sandbox supports two kinds of payment option:

  • SkyPay Simulator produces deterministic local outcomes for automated tests.
  • Paystack Sandbox and Payaza Sandbox open the provider's real test journey.

Your integration does not receive or configure provider credentials. Initiate the payment with an ssk_sand_ SkyPay key, redirect the payer to the returned SkyPay checkout URL, and let the payer choose an available option.

Availability​

SkyPay checks each provider environment independently. A provider appears as Temporarily unavailable when its Sandbox configuration is disabled, missing, or unhealthy. It cannot be selected, and a direct process request returns GATEWAY_NOT_AVAILABLE or GATEWAY_ENVIRONMENT_NOT_CONFIGURED.

SkyPay never falls back from a named provider to the simulator. Retry the same provider later or start a new attempt after showing the payer another available choice.

Process a selected provider​

The hosted checkout sends the selected slug to:

POST /public/payments/{reference}/process
Content-Type: application/json

{ "gatewaySlug": "paystack" }

Use payaza for Payaza or sandbox for the SkyPay Simulator. A repeated process request returns the existing provider hand-off and does not create another provider charge.

Confirm the result​

After the provider returns the payer to SkyPay, the checkout verifies the payment against the same environment. Your server should still rely on a verified SkyPay webhook or GET /payments/{reference} before fulfilment.

Sandbox transactions and webhook deliveries never appear in Live.