About Be2bill
General information about Be2bill
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, Paygate 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.
| Logo |
|
|---|---|
| Info | Be2bill is specially optimized for the “Cartes Bancaires” credit cards which is widely used in France. |
| Type | Payments by Credit Card |
| Card Scheme |
|---|
| VISA |
| MasterCard |
| Cartes Bancaires |
Process flow charts
Configuration for Be2bill
To set up Be2bill the merchant needs to save the required Paygate interface URLs in the backend. Each of these is a “Transaction feedback URL”:
https://www.computop-paygate.com/Be2billComplete.aspx
and for “Redirection URL after payment form or 3DSECURE processing” and “Redireciton URL after payment form cancelling” respectively:
https://www.computop-paygate.com/cbBe2bill.aspx
Paygate interface
Format Description a alphabetical as alphabetical with special characters n numeric an alphanumeric ans alphanumeric with special characters ns numeric with special characters bool boolean expression (true or false) 3 fixed length with 3 digits/characters ..3 variable length with maximum 3 digits/characters enum enumeration of allowed values dttm ISODateTime (YYYY-MM-DDThh:mm:ss) Abbreviation Description CND condition M mandatory O optional C conditional Notice: Please note that the names of parameters can be returned in upper or lower case.Definitions
Data formats
Abbreviations
Comment If a parameter is mandatory, then it must be present If a parameter is optional, then it can be present, but it is not required If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional
Credit card payment with Be2bill via Paygate form interface
Payments with Be2bill are made via the standard Paygate form interface for credit card payments. In order to execute an SSL credit card payment with Be2bill via a Paygate form, visit the following URL:
https://www.computop-paygate.com/payssl.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
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 Paygate forms for credit card payments with Be2bill
The following table gives the result parameters which Computop Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
Return parameters for URLSuccess, URLFailure and URLNotify with Be2bill
Credit card payment via Server-to-Server connection
In order to execute an SSL credit card payment with Be2bill via a server-to-server connection, call the following URL:
https://www.computop-paygate.com/direct.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for credit card payments with Be2bill via socket connection
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
Results parameters for socket connection for Be2bill
Capture of a credit card payment with 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:
https://www.computop-paygate.com/capture.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for captures of Be2bill via socket connections
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
Response parameters for captures of Be2bill via socket connections
Credit with reference
Credits (refunds) are possible via a Server-to-Server connection. For a Credit with reference to a capture the amount of the Credit is limited to the amount of the previous capture. To carry out a credit with a reference transaction, please use the following URL:
https://www.computop-paygate.com/credit.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for credit payments with Be2bill via socket connection
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
Response parameters for credits of Be2bill via socket connections
Reversal
Reversals of an instalment payment are possible via a Server-to-Server connection. The Paygate permits only reversals that reference on a capture previously made via Paygate. 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:
https://www.computop-paygate.com/reverse.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for reversals with Be2bill via socket connection
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
Response parameters for reversals of Be2bill via socket connections
Batch processing via the interface
Basic information about using Batch files and about their structure can be found in the Batch Manager manual. Within batch processing not alle functions are available which are usually available for the online interface.
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:
HEAD,<MerchantID>,<Date>,<Version> CC,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> CC,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> CC,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> FOOT,<CountRecords>,<SumAmount>
Example for Master MID function:
HEAD,[Master]MerchantID,Date,2.x Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action) FOOT,CountRecords,SumAmount
The following table describes the individual fields and values used within the data set (record) in the batch file:
Description of fields within the record for Batch files
The record area within the response file for Batch transactions looks as follows:
HEAD,<MerchantID>,<Date>,<Version> CC,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code> CC,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code> CC,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code> FOOT,<CountRecords>,<SumAmount>
The following table describes the response parameters which the Batch Manager saves in the Record area for each transaction (standard parameters not explained here, such as <TransID> or <RefNR> and request parameters are returned unchanged and correspond to the call as specified before):
Description of result parameters within the record for Batch files
Test data
Be2bill provides specific Sandbox test data: Test Be2Bill Sandbox