In order to test the payment connector the following section contain test data. For some tests special instructions have to follow. Some test data may produce a negative result. We indicate when the test data should lead to a transaction failure or decline.
The issues can be simulated by entering ISSUE-CLAIM-CODE as a family name, where CODE can have one of the following values:
| Code | Description |
|---|---|
| 0 | The payer's bank wasn't in a position to pay the Direct Debit. Probably due to an insufficient funds on a payer's account. |
| 1 | The Direct Debit Instruction is cancelled by payer. |
| 2 | The payer is deceased. |
| 3 | The payer's Direct Debit Instruction has been transferred to a new bank account and the direct debit payment has been submitted to old account. |
| 4 | The payer has disputed having been notified of this Direct Debit. |
| 5 | The payer has provided an invalid account number or the account type is wrong (e.g. savings account). |
| 6 | The payer doesn't have a Direct Debit Instruction set up with you or the Direct Debit Instruction is cancelled by payer. |
| 7 | The payer has disputed that the amount taken, differs from the amount they were notified of. |
| 8 | The amount is not yet due. The payment has been submitted for collection before the planned execution date. |
| 9 | The payment has been submitted for collection after the planned execution date. |
| A | The merchant's details don't match the details on the payer's Direct Debit Instruction. |
| B | The payer's account is closed. |