Introduction
The DIBS gateway has a feature called “Test Mode”. When Test Mode is not activated, no tests may be performed on this merchant account.
Test Mode is activated in DIBS Manager under General > Test Mode. After you have activated Test Mode, it will stay active for a short time period. Currently the default value is 3 days, but this is subject to change at any time with no prior warning.
Only if you have activated Test Mode, you will be able to use the Test Acquirer and the Test Purchase feature in DIBS Manager.
Test acquirer
Before you start using a real acquirer you can test credit card payments by using the “cc.test” method parameter. The test acquirer will fake real acquirer answers depending on the card number being used.
Once the method “cc.test” is used, the transaction will not be sent to a real acquirer, but will instead be handled by the test acquirer. When a test transaction is carried out, it can be seen in DIBS Manager, where the transaction can also be settled, reversed or refunded. Test transactions can also be settled, reversed or refunded using the Server Solution APIs.
In DIBS Manager, test transactions can be distinguished from actual transactions, since test transactions are shown on a grey background instead of a white background. Also, the displayed name of the acquirer for test transactions is “TestAcquirer”. Test transactions will not be included in accounting and payment reports.
The Test Acquirer is set up so that certain card numbers give certain replies. If a card number, contrary to those described below, is inadvertently sent, the authorization reply will be resultCode “200” and resultText “verification_denied”. For more examples see the tables below.
Please note that test payments can never be sent to a real acquirer. When going live, make sure that you are not using the “cc.test” method.
The test cards which can be used along with the test acquirer can be found on the testing page in the toolbox section.