Be2Bill in Sandbox (Downstream Test Mode)
With Be2Bill in sandbox mode the payments are forwarded to Be2Bill Sandbox System.
In this mode these test data are available:
Scheme | Test PAN | Response | ExtCode | Description |
VISA | 4234603011240000 | 00000000 | 0000 | Successful operation |
VISA | 4464210935060000 | 00000000 | 0000 | Frictionless 3-D Secure |
VISA | 4464215790990001 | 00000000 | 0001 | 3-D Secure authentication required |
VISA | 4234607564194001 | 22540100 | 4001 | Transaction declined by the banking network |
VISA | 4234604810334002 | 22541884 | 4002 | Insufficient funds |
VISA | 4234606735474003 | 22540100 | 4003 | Card declined by the banking network |
VISA | 4234600140624005 | 22541527 | 4005 | Fraud suspicion |
VISA | 4234604450614010 | 22540161 | 4010 | Invalid transaction |
VISA | 4234609939944011 | 22541515 | 4011 | Duplicated transaction |
VISA | 4234604160524012 | 22540356 | 4012 | Invalid card data |
VISA | 4234608464714013 | 22540100 | 4013 | Transaction declined by banking network for this holder |
VISA | 4234607430914020 | 22540055 | 4020 | Strong customer authentication required by issuer |
VISA | 4234609090495001 | 22540055 | 5001 | Exchange protocol failure |
VISA | 4234604508525002 | 22540391 | 5002 | Banking network error |
VISA | 4234607483945004 | 22540040 | Time out, the response will be sent to the notification URL (only applicable for Visa / MasterCard direct connection) |
Source: https://developer.dalenys.com/payment-methods/bank-card.html#sandbox-test-card-numbers
Acquirer data are available – still in test mode
Real communication with your acquirer's system is already taking place – however, bookings are not yet activated and no money is transferred.
Testing is done with real cards and the available card limit is already reduced. You can release this by canceling (reverse) or wait until it is automatically released by the bank after approx. 7-14 days.
Captures and refunds are not possible – no money is transferred.
Simulation – always possible
The simulation mode is initiated by the "OrderDesc" parameter with the value "Test: <nnnn>", which also defines the result of the payment process.
The simulation mode is always available – but also requires card numbers that pass the so-called LUHN test. There is a short table below for this; You can also use real credit cards.
Scheme | Card number | Value OrderDesc | Response | Description |
VISA | 4111111111111111 | Test:<nnnn> | <nnnn> | See: A4 Error codes |
MasterCard | 5555555555554444 | Test:<nnnn> | <nnnn> | See: A4 Error codes |
AMEX | 375000000000007 | Test:<nnnn> | <nnnn> | See: A4 Error codes |
EMV 3-D Secure / 3-D Secure 2.x
Please note that
CustomerId, OrderDesc, Email are still required parameters for Be2Bill processing: Be2bill
Additionally with 3-D Secure 2.x the "Cardholder name" (parameter "CreditCardHolder") becomes mandatory. For usage with our Paygate Form Interface (payssl) the cardholder name has to be enabled by our Computop Helpdesk.
Other data (JSON Objects) are supported and improve the conversion rate with 3-D Secure 2.x
Since the "3-D Secure" option must first be configured for your payment method, please contact our Computop Helpdesk beforehand.
For switching to 3-D Secure 2.x
your account needs to be switched to 3DS2 at Be2Bill: please contact your Be2Bill customer success manager
and at Computop: please contact our Computop Helpdesk