The following explanation is based on the most extensive set-up within software test production environments. Needs may differ depending on the set-up of the environments by the Merchant. Thus, it might take fewer steps to achieve an effective production environment.
For large software development environments, there’s often a Development, Testing, Acceptance, Pre-Production and Production environment, abbreviated DTA(P)P. In Dutch this is called an OTA(P)P (Ontwikkel-, Test-, Acceptatie-, Pre-Productie and Productieomgeving) environment. These stages represent the steps that are taken in a software development trajectory.
Test data is automatically archived after 4 months (124 days). All test transactions with associated billing information will be deleted after this period. For test scenarios with recurring transactions, there must therefore always be an original transaction which is not older than 4 months.
The need for interaction between the different environments differs per Merchant. The advantage of a separate test account is that developers can introduce new features in the test environment without disrupting production at any time.
Below you can see which setting involves a test transaction or a live transaction in the Payment Plaza:
|Checkout||Plaza account setting: Test||Plaza account setting: Live|
|testcheckout.buckaroo.nl||Test transaction||Test transaction1|
|checkout.buckaroo.nl||Test transaction||Live transaction|
1 Only if the following option is activated in the website URL: allow test transactions.
It is possible to start with an account in test mode and grant it a production status at the end of the building process. The Merchant can then maintain one single account containing separate website keys for the different staging environments. It is also possible to create a separate account for different staging/production environments. If required, you can make a request to Buckaroo for a separate test account.
Each account has its own security settings for message traffic. Such as a secret key, a security certificate and a separate thumbprint. These have to be configurated by Buckaroo as well as the Merchant. The Development website can be used as a guideline for the different implementations.