1 About Barzahlen

1.1 General information about Barzahlen

This manual describes configuring and using the First Cash Solution interface for Barzahlen:

Barzahlen is aimed at customers in Germany who do not want to enter sensitive data online, and those who do not use credit cards or online banking. An alternative to cash on delivery, Barzahlen is quicker and less expensive. Customers pay the amount to an associated retailer, on the basis of a payment form; the retailer transmits a payment confirmation in real time to the online shop so that the goods can be dispatched quickly.

Barzahlen is a payment provider for cash transactions. Customers use cash to pay for online purchases, travel bookings or diverse invoices. It is also possible to pay by cash to one’s own giro account.

The customer receives a barcode via email, SMS or Post to process the payment. This barcode is then scanned at the checkout of an individual partner branch and the customer pays with cash or another permitted payment method. The supplier is notified about payment in real time by the checkout system once the customer has paid. The payment service is carried out by Greensill Bank AG from Bremen.

Currently cash payments are made throughout Germany in over 10,000 branches of the REWE markets, dm-drogerie markets, PENNY markets, real,- supermarkets, Telekom Shops, mobilcom-debitel branches and with Budni chemists and in branches of the Dr. Eckert group.

Cash payments offer users who prefer cash, the option to buy, gamble or to book travel online without entering sensitive financial data. This cash option, means it is the only payment system available to every German without restriction. 68% of Germans over 18 years have no credit card (Deutsche Bundesbank 2015) and 51% do not use online banking (Bundesverband deutscher Banken 2014).

Further information can be found on the webpage of Barzahlen (https://www.barzahlen.de/de/).

1.2 Process flow chart

Barzahlen process flow

2 Configuration for Barzahlen

Merchants need to initially setup an account with Barzahlen on their webpage: https://controlcenter.barzahlen.de/#/account/signin

You start configuration once you have logged on.

In the cash payment Control Center you need to enter the following URLs under Settings / Divisions (https://controlcenter.barzahlen.de/#/settings/divisions).

Notification URL: https://www.computop-paygate.com/BarzahlenComplete.aspx

Sandbox notification URL: https://www.computop-paygate.com/BarzahlenComplete.aspx

You must send the division-ID together with the payment key to the First Cash Solution Support at support@1cs.de, in order to activate this payment method within your MID on the 1cs Online Payment System.

3 1cs Online Payment System interface

3.1 Definitions

3.1.1 Data formats

3.1.2 Abbreviations

Notice: Please note that the names of parameters can be returned in upper or lower case.

3.2 Call of interface for Bezahlen

To carry out a Barzahlen payment via a Server-to-Server connection, call the following URL:

https://www.computop-paygate.com/barzahlen.aspx

Notice: For security reasons, the 1cs Online Payment System 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 payments with Barzahlen

The following table gives the result parameters with which the 1cs Online Payment System 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. MerchantId, RefNr) should not be checked case-sentive

Response parameters for payments with Barzahlen

The following table gives the result parameters which the 1cs Online Payment System transfers to your URLNotify:

Response parameters for URLNotify with Barzahlen

The merchant has to implement the following code on his page in order to display the Barzahlen checkout page.

<!-- Barzahlen Checkout -->
<script src=https://cdn.barzahlen.de/js/v2/checkout.js
        class="bz-checkout"
        data-token="CHECKOUT_TOKEN">
</script>
<!-- End Barzahlen Checkout -->

The value of the Checkout_Token is transferred by First Cash Solution in the TokenExt parameter.

The src value must contain the following values for test and productive transactions:

Test: https://cdn.barzahlen.de/js/v2/checkout-sandbox.js\
Productive: https://cdn.barzahlen.de/js/v2/checkout.js

3.3 Updating a payment

To update a Barzahlen payment via a Server-to-Server connection, call the following URL:

https://www.computop-paygate.com/barzahlenUpdate.aspx

Notice: For security reasons, the 1cs Online Payment System rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.

Parameters for updating a payment with Barzahlen

The following table describes the result parameters with which the 1cs online payment system responds to your system

• be prepared to receive additional parameters at any time and do not check the order of parameters

• the parameters (e.g. MerchantId, RefNr) should not be checked case-sentive

Response parameters for updating of Barzahlen

3.4 Credit with reference

Credits (refunds) are possible via a Server-to-Server connection. 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, the 1cs Online Payment System 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 credits of Barzahlen payments

The following table gives the result parameters with which the 1cs Online Payment System 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. MerchantId, RefNr) should not be checked case-sentive

Result parameters for credits of Barzahlen payments

3.5 Reversal

In order to cancel a Barzahlen payment via a server-to-server communication, please go to the following URL:

https://www.computop-paygate.com/reverse.aspx

Notice: Reverse.aspx does not only reverse authorisations, but any LAST TRANSACTION STAGE! If the last transaction was a capture, Reverse.aspx initiates the reverse, e.g. a credit. Therefore, the utmost caution is urged. Use is at your own risk. We recommend checking the transaction status with Inquire.aspx before using Reverse.aspx.

Notice: For security reasons, the 1cs Online Payment System rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.

The following tables describe the encrypted payment request parameters:

Parameters for reversals of Barzahlen payments

The following table gives the result parameters with which the 1cs Online Payment System 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. MerchantId, RefNr) should not be checked case-sentive

Result parameters for reversals of Barzahlen payments

4 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 reversals or credits with Barzahlen 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 Barzahlen payment within a Batch file to be submitted is the following:

HEAD,<MerchantID>,<Date>,<Version>

Barzahlen,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>

Barzahlen,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>

FOOT,>CountRecords>, >SumAmount>

Example for Master MID Funktion:

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 the following way:

HEAD,<MerchantID>,<Date>,<Version>

Barzahlen,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>

Barzahlen,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