Request Intro

Notice: For security reasons,  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:

Request Intro Additional

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

(info) The following table describes the additional encrypted payment request parameters described below for "interface via form" and "interface via Server-to-Server" :

Request Intro Short

The following table describes the encrypted payment request parameters:

Response Intro

The following table describes the result parameters with which the  responds to your system

(info) pls. be prepared to receive additional parameters at any time and do not check the order of parameters

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

Response Intro URL

The following table gives the result parameters which  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:

(info) pls. be prepared to receive additional parameters at any time and do not check the order of parameters

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

KVP: Response Intro URL

In case of using Key-Value-Pair API

The following table gives the result parameters which 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:

(info) pls. be prepared to receive additional parameters at any time and do not check the order of parameters

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

REST: Response Intro URL

In case of using REST API

In case of using REST API you will always receive a link where the merchant has to redirect the consumer to complete the payment.

RESTFormatCNDDescription

"paymentId": "..."

an32M

May be "00000000000000000000000000000000" if not yet set by

"_Links.self.type": "..."an..20M

"application/json"

"_Links.redirect.href": "..."an..1024MMerchant needs to redirect consumer to this URL to complete payment
"_Links.redirect.type": "..."an..20M"text/html"

Merchant can use inquire.aspx

Response Intro Additional

The following table describes the result parameters with which the  responds to your system.

(info) these result parameters are additional to the standard parameters for "interface via form" and "interface via Server-to-Server" described below

(info) pls. be prepared to receive additional parameters at any time and do not check the order of parameters

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

Layout Intro

To adapt the layout of the SSL-page to your shop you can use the following unencrypted parameters to configure colours, fonts and images:

Credit Intro

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:

Batch Intro

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.

Batch Request Intro

The following table describes the individual fields and values used within the data set (record) in the batch file:

Batch Response Intro

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):

Request with Amount

Request with Amount + MAC

Response with MID, PayId, XID, Code, Description

Response with MID, PayId, XID, Code, Description, Status

Einzelne Parameter

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional  settlement file (CTSF) we cannot add the additional payment data.

Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...).

MerchantID, assigned by . Additionally this parameter has to be passed in plain language too.


MerchantID, assigned by 

Link (Linchpin) to Cookie-/Session

Note to Cookie-/Session-Handling

Link (Linchpin) to EMV 3DS

Note to EMV 3-D Secure

Link (Linchpin) to API Playground

API Playground