With the connection of the French acquirer be2bill, merchants who are active in France have a powerful alternative for the selection of acquirer. As well as VISA and Mastercard credit cards, also handles payments made with the extremely widespread Cartes Bancaires via this partner. Be2bill offers online merchants a “3-in-1” solution for the management of its online payments including bank and payment services, internet-based marketing and solutions for increasing customer loyalty.
Credit card payments via be2bill can be made with or without 3D-Secure. For 3DS transactions, be2bill offers its own fraud prevention service which determines whether 3D authentication is needed. Along with one-off payments, be2bill also offers payment by instalment, recurring payments and one-click payments.
|
|
Be2bill process flow via the form interface
Be2bill process flow via server-to-server-communication
To set up Be2bill the merchant needs to save the required interface URLs in the backend. Each of these is a “Transaction feedback URL”:
Be2billComplete.aspx
and for “Redirection URL after payment form or 3DSECURE processing” and “Redireciton URL after payment form cancelling” respectively:
cbBe2bill.aspx
Payments with Be2bill are made via the standard form interface for credit card payments. In order to execute an SSL credit card payment with Be2bill via a form, visit the following URL:
payssl.aspx |
|
Parameters for credit card payments with Be2bill
To adapt the layout of the SSL-page to your shop you can use the following unencrypted parameters to configure colours, fonts and images.
|
Layout parameters for forms for credit card payments with Be2bill
|
Return parameters for URLSuccess, URLFailure and URLNotify with Be2bill
In order to execute an SSL credit card payment with Be2bill via a server-to-server connection, call the following URL:
direct.aspx |
|
Parameters for credit card payments with Be2bill via socket connection
|
Results parameters for socket connection for Be2bill
Captures are possible via a Server-to-Server connection. To carry out a Capture for a Be2bill credit card payment via a Server-to-Server connection please use the following URL:
capture.aspx |
|
Parameters for captures of Be2bill via socket connections
|
Response parameters for captures of Be2bill via socket connections
credit.aspx |
|
Parameters for credit payments with Be2bill via socket connection
|
Response parameters for credits of Be2bill via socket connections
Reversals of an instalment payment are possible via a Server-to-Server connection. The permits only reversals that reference on a capture previously made via . Only instalment payments can be cancelled. The reversal of a simple authorization is not possible.
To carry out a reversal with a reference transaction, please use the following URL:
reverse.aspx |
|
Parameters for reversals with Be2bill via socket connection
|
Response parameters for reversals of Be2bill via socket connections
This section describes the parameters which must be transferred within the data set (Record) for executing payments / credits with Be2bill and which information can be found within the response file about the payment status.
For Batch calls there must be considered batch versions, from which optional parameters depend. All version designations starting with „2.“ pertain calls for a group of enterprises. That means within a batch file for a particular MerchantID can be transferred transactions for other merchants with a separate Sub-MID.
Following table gives an overview of all batch versions that are possible for a specific action and their specialities:
|
Description of the possible batch versions
The structure for a Be2bill payment within a Batch file to be submitted is the following:
|
Example for Master MID function:
|
|
Description of fields within the record for Batch files
The record area within the response file for Batch transactions looks as follows:
|
|
Description of result parameters within the record for Batch files
Be2bill provides specific Sandbox test data: Test Be2Bill Sandbox