Sandbox Constraint Limitations

The sandbox environment is a secure, low-threshold testing environment provided by PingPong for developers. The sandbox provides support with limited functionality range for open products, covering most of the product's core workflows and integration logic, facilitating developer development and debugging. Therefore, there will be some functional limitation constraints during use.

• Not 100% authentic: Need to be aware that the sandbox environment is not 100% consistent with the production environment. Please refer to the production environment for the actual response logic of interfaces. After development and debugging in the sandbox environment, testing and acceptance are still required in the production environment.
• Data isolation, do not mix: The sandbox environment has a completely independent data system. Data returned in the sandbox environment (such as order numbers) is only for use in the sandbox environment. Developers must not mix data returned from the sandbox environment with data from the production environment.
• Limited functionality: Not all payment methods can test successful scenarios, such as MyBank, NeverPay; some payment methods mock calls will redirect to channel blocking pages, such as Trustly, Bancontact, Boost, etc., which can simulate success states.

Note

The sandbox simulation environment is used by developers for interface development and debugging. To ensure the stability of the sandbox environment services, please do not perform stress testing or security attacks casually. If needed, please contact PP staff first to report and apply, otherwise the PP operations and security team has the right to disable requests from abnormal applications or IPs to ensure service stability.

Previous pageSandbox Registration Guide

Next pageAcceptance Test Scenarios