Skip to main content
Use your provider’s sandbox to test the credentials, redirects and payment outcomes that your integration will rely on. Where your merchant has the Internal Test connection enabled, you can also simulate card and test-wallet outcomes inside OrsunPay.

​
Set up test mode

  1. In the merchant cabinet, switch to Test mode (every page shows a test banner).
  2. Under Connections, add a connection with your provider’s sandbox credentials. The mode is derived from the credentials, for example: A test key never uses a live connection, and a live key never uses a sandbox connection.
  3. Under API keys, create a test_… key. If this returns TEST_API_KEYS_DISABLED, test keys are not yet enabled for your deployment.
  4. Under Webhooks, set the test endpoint URL and issue the test signing secret. Test events are delivered only there, signed with the test secret; without a test endpoint no test webhook is sent. The endpoint must be a public HTTPS URL (use a tunnel for a local receiver).

​
What to test

​
Provider test data

Use the test cards and scenarios published by each provider:

​
Internal Test simulation

If your operator has enabled Internal Test for your merchant, use the synthetic card or test wallet in Test mode. The connection supports EUR, GBP and USD. Its configured scenario can simulate success, decline, a required action, pending, an unknown outcome or cancellation. Use the fixture details shown for the simulator. A pending or unknown result should leave your order open without a second charge attempt. The simulator covers sale handling within OrsunPay. Qualify each external connection separately using its own sandbox credentials and test data, including the callback from that provider.

​
Limits of test mode

  • Create test payment links through the payment-links API with your test key. Opening the link uses your merchant’s eligible sandbox connections.
  • The cabinet’s Send test webhook (test.ping) is available in live mode only.
  • Sandbox behaviour is the provider’s; for example, wallet buttons and redirect timing depend on the provider’s test environment.
  • Test and live data never mix: test transactions, customers, webhook settings and order IDs are separate from live ones.