Testing different scenarios in Billwerk+Optimize can be done using our Test Payment Gateway and a number of test cards. The test cards are fixed but a number of predefined CVV codes and amounts can be used to trigger different scenarios. Any expiration date can be used as long as it is the current month or in the future.
Test cards
| Type | Id | Number |
|---|---|---|
| Visa | visa | 4111 1111 1111 1111 |
| Visa-DK | visa_dk | 4571 9940 0006 2336 |
| Dankort | dankort | 5019 1000 0000 0006 |
| Visa Electron | visa_elec | 4026 1111 1111 1115 |
| Mastercard | mc | 5500 0000 0000 0004 |
| American Express | amex | 3400 000000 00009 |
| JCB | jcb | 3530 1113 3330 0000 |
| Maestro | maestro | 6759 0000 0000 0000 |
| Diners | diners | 3000 0000 0000 04 |
| Discover | discover | 6011 1111 1111 1117 |
| China Union Pay | china_union_pay | 6240 0086 3140 1148 |
| Forbrugsforeningen | ffk | 6007 2200 0000 0004 |
Recurring token create errors
Errors in the authorization process of adding a recurring card payment method can triggered by the following CVV codes. To trigger additional errors for one-time charging see "Charging errors" below.
| CVV | Scenario |
|---|---|
001 | The credit card is declined with due to credit card expired |
002 | The credit card is declined by the acquirer |
003 | The credit card is declined due to insufficient funds |
004 | The authorization is declined due to errors at the acquirer |
005 | The authorization is declined due to communication problems with the acquirer |
006 | The authorization is declined due to communication problems with the acquirer (60 second processing time) |
Subsequent subscription billing errors
All CVV codes, except the ones above, will result in a successful card authorization. The CVV codes below can be used to trigger different scenarios for subsequent payments. Declines are separated into recoverable and irrecoverable declines. Irrecoverable declines indicates that a payment will never be possible for the card again, e.g. an expired or blocked card. Recoverable declines indicates that successful payments for the card could be possible in the future. This could for example be due to insufficient funds. Billwerk+Optimize will start dunning for recoverable declines, but will regularly try to process payments using the card, as long as a new payment method has not been added.
| CVV | Scenario |
|---|---|
100 | The first payment is declined with an irrecoverable error (credit card expired) |
101 | The first payment is declined with an irrecoverable error (declined by acquirer) |
102 | The first payment is declined with an recoverable error (insufficient funds) |
200 | The second payment is declined with an irrecoverable error (credit card expired) |
201 | The second payment is declined with an irrecoverable error (declined by acquirer) |
202 | The second payment is declined with an recoverable error (insufficient funds) |
300 | With a probability of 50% the payment is declined with an irrecoverable error (credit card expired) |
301 | With a probability of 50% the payment is declined with an irrecoverable error (declined by acquirer) |
302 | With a probability of 50% the payment is declined with an recoverable error (insufficient funds) |
Charging errors
To trigger errors in the process of creating charges and settling authorized charges the cvv 888 can be used in combination with a number of amounts. E.g. a successful authorization can be performed and then a specific amount can be used for the settlement that will result in an error. To trigger the scenarios when charging a saved card the card should be saved with cvv 888. The table below shows the amounts to be used with cvv 888 to trigger errors.
| Amount | Error state | Error code |
|---|---|---|
1000 | success | |
1001 | processing_error | acquirer_communication_error |
1002 | processing_error | acquirer_error |
1003 | processing_error | acquirer_integration_error |
1004 | processing_error | acquirer_authentication_error |
1005 | processing_error | acquirer_configuration_error |
1006 | processing_error | acquirer_rejected_error |
2001 | soft_declined | insufficient_funds |
2002 | soft_declined | settle_blocked |
3001 | hard_declined | credit_card_expired |
3002 | hard_declined | declined_by_acquirer |
3003 | hard_declined | credit_card_lost_or_stolen |
3004 | hard_declined | credit_card_suspected_fraud |
3005 | hard_declined | authorization_expired |
3006 | hard_declined | authorization_amount_exceeded |
3007 | hard_declined | authorization_voided |
1337 | hard_declined | sca_required (Error for non-SCA payments to mimic PSD2 behaviour) |
Payout errors
Payout errors can be triggered by performing payout on cards created with the following CVV codes.
| CVV | Scenario |
|---|---|
501 | The credit card is declined with due to credit card expired |
502 | The credit card is declined by the acquirer |
503 | The credit card is declined due to insufficient funds |
504 | The authorization is declined due to errors at the acquirer |
505 | The authorization is declined due to communication problems with the acquirer |
506 | The authorization is declined due to communication problems with the acquirer (60 second processing time) |
Test data retention
Old test data will automatically be deleted by Billwerk+Optimize. Customers, and all customer releated data e.g. subscriptions and invoices, will be deleted for customers created more than three months ago.
Mail sending limits
For test accounts there is a limit of 100 mails per day. In addition, there is a limit of 10 unique recipients. Mails passing threshold will still be created and shown for invoice and subscriptions, but with a "not allowed" state.
Resending and preview functionality for test accounts are limited to 10 requests per day.