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.
Interaction of the environments
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.
Development environment: Create a link with Buckaroo in the test account. During this phase, the most important thing is to test the message structures and the syntax of the encryption of messages. These tests are called connectivity tests.
Test environment:In a first version of the software, a link can be created with Buckaroo and a test message can be sent. Feedback (successful/failed payment) will be created within the test account. This way the Merchant can verify whether the systems react adequately to Buckaroo’s reply. During this phase the tests are called ‘the technical tests’.
Acceptance environment: The first users are being involved in and exposed to the customer expierence within the customised software. At this stage, experiences are mostly of a functional nature. Think of illogical customer service within the environment or wrong answer pages after the payment data have been entered. Tests are run with a stub or with the test credentials of the payment service provider. For banks, the latter is often not available and a stub is the sole solution. The tests during this phase are the functional tests.
Pre-Production: Such an environment is not always available. These tests could for example take place in the acceptance environment, which is being set up for end-to-end testing . The acceptors of the feature want to see the complete handling as if it was the actual production. For this purpose, the live credentials are used within the test environment or the end-to-end tests are carried out during production. Please note: Buckaroo needs to grant permission for using live credentials in a Buckaroo test account. You can request permission via the accountmanager. This environment is entirely set up for production and financial mutations take place as they would during actual production. This is often called “end-to-end testing”.
Production: Everything is interconnected and the customers are using the previously tested software in the intended payment environment.
Buckaroo Payment Plaza settings
Below you can see which setting involves a test transaction or a live transaction in the Payment Plaza:
|Checkout||Plaza account status: Test||Plaza account status: Live|
|testcheckout.buckaroo.nl||Test transaction||Test transaction*|
*Only if the following option is activated in the website settings: allow test transactions.
Points of attention
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. This support website can be used as a guideline for the different implementations.