interface

Calling the interface for a Bluecode Website payment with QR Code (Sale)

Cancellations and credits are available for Bluecode payments as described in the sections below. Only credits are available in batch mode. For point-of-sale transactions please use connection for Bluecode QR Code payment.

Use the following URL to process an Bluecode QR Code payment via redirect to the Bluecode form:

Use the following URL to process an Bluecode QR Code payment via Server-to-Server connection – you have to transform the Bluecode URL into a QR Code:

Parameters for payments with Bluecode website payment

Result parameters for URLNotify, URLSuccess and URLFailure in case of Bluecode website payment

Reversal (if a payment process has not been completed successfully)

Reversals of a payment with Bluecode QR Code payment are possible via a Server-to-Server connection. The permits reversals that reference an authorisation previously made via . If you reference a payment in a cancellation, the whole payment is cancelled. A cancellation is not possible for successful completed payment processes. To refund money to the consumer use "credit".

To carry out a Reversal for Bluecode QR Code payment via a Server-to-Server connection please use the following URL:

Parameters for reversal of Bluecode QR Code payments

Response parameters for reversal of Bluecode QR Code payments

Credit with reference

Credits for a payment with all Bluecode payment scenarios can be made via server-to-server communication. permits credits that reference on a capture previously made via . 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:

Parameters for credits of Bluecode payments

Result parameters for credits of Bluecode payments

Batch processing via the interface

This section describes the parameters which must be transferred within the data set (Record) for executing an Bluecode payment and 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 an their specialities:

Description of the possible batch versions

The structure for a Bluecode credit within a Batch file to be submitted is as follows:

HEAD,<MerchantID>,<Date>,<Version>
Bluecode,Credit,<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

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>
Bluecode,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>
FOOT,<CountRecords>,<SumAmount>

Description of result parameters within the record for Batch files

Test data

Bluecode provides a special Sandbox-App to provide test functionality. This Sandbox-App is not available in the official Appstores, but is available here:

Please note:

After installation of Bluecode Sandbox-App the Bluecode has to be connected to a bank account:

• After installation of Bluecode Sandbox-App you have to setup a PIN for the App.
• Then click on "Connect bank account" and enter "test" in the bank search.
• The entry "Activate a test user" is then displayed. A test account can be added by clicking on it.
• To do this, select the first entry "Hypo Tirol".
• A blue code for payment is then displayed.
• To scan a QR code with your smartphone, tap the QR symbol in the top left of the app to activate the camera.
• The amount is then displayed on the smartphone for confirmation. You confirm this by "swiping".

In the Bluecode Sandbox app, no "real" payments are made, they are only simulated!

Important notes when switching to live payments

itself has a certified Bluecode implementation. However, when switching from test to production mode a merchant has to ensure:

• Use URL "Bluecode.aspx" to initiate a Bluecode payment with redirect to Bluecode page containing the QR code
• Use URL "BluecodeS2S.aspx" to retrieve a Bluecode URL which has to be transformed into a QR code by the merchant system
• Values for request parameter "RefNr" are unique per payment process – duplicate values will be rejected
• Values from response parameter "TransactionID" must be printed on customer's invoice / receipt
• Values from response parameter "TransID" must be printed on customer's invoice / receipt if not empty