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:

Marke / SchemeTest PANAntwort / ResponseExtCodeDescription
VISA4234603011240000000000000000Successful operation
VISA4464210935060000000000000000Frictionless 3-D Secure
VISA44642157909900010000000000013-D Secure authentication required
VISA4234607564194001225401004001Transaction declined by the banking network
VISA4234604810334002225418844002Insufficient funds
VISA4234606735474003225401004003Card declined by the banking network
VISA4234600140624005225415274005Fraud suspicion
VISA4234604450614010225401614010Invalid transaction
VISA4234609939944011225415154011Duplicated transaction
VISA4234604160524012225403564012Invalid card data
VISA4234608464714013225401004013Transaction declined by banking network for this holder
VISA4234607430914020225400554020Strong customer authentication required by issuer
VISA4234609090495001225400555001Exchange protocol failure
VISA4234604508525002225403915002Banking network error
VISA423460748394500422540040
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.

Marke / SchemeKartennummer / Card numberWert / Value OrderDescAntwort / ResponseBeschreibung / Description
VISA4111111111111111Test:<nnnn><nnnn>Siehe / see: A4 Error codes
MasterCard5555555555554444Test:<nnnn><nnnn>Siehe / see: A4 Error codes
AMEX375000000000007Test:<nnnn><nnnn>Siehe / 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



  • No labels