Skip to main content

Limitations of the Sandbox Environment

While the sandbox environment is a valuable tool for testing and development, it is important to be aware of its limitations. These constraints are designed to optimize the testing phase, but may differ from the production environment.

Limited Duration of Transactions​

A key feature of the sandbox environment is that transactions are kept for a limited period of time. This means that:

  • Transactions made in the sandbox are not permanent and can be deleted after a certain period.
  • It is recommended to perform relevant tests within a short time frame after transaction creation.

Error Scenario Coverage​

Another limitation of the sandbox environment is error simulation:

  • Not all error scenarios that may occur in the production environment are present in the sandbox.
  • The sandbox includes examples of common errors to help with development and testing, but may not cover all possible cases.
  • In production, additional errors may arise, but they will always follow the error response contracts demonstrated in the sandbox.

Implications for Testing​

  • Thorough Testing: It is essential to test the application against all common scenarios and known errors in the sandbox environment before going to production.
  • Production Readiness: Be prepared to handle unexpected errors in production and ensure that your application can respond appropriately to any situation.

By understanding these limitations, you can better plan your tests and prepare your application for a smoother transition to the production environment.

Next steps​

After completing the tests in the sandbox environment and being confident in the integration of your application, the next step is to plan the migration to the production environment, considering the differences mentioned.

Remember, the transition from sandbox to production is an important step and must be done carefully to ensure a smooth experience for end users.