Über Girocard E-Commerce

E-Commerce-Zahlungen mit Girocard sind aktuell nur mit Apple Pay möglich.

Diese Seite beschreibt die Lösung für die händlereigene Entschlüsselung der Apple-Pay-Nutzlast (Token) für wiederkehrende Zahlungen.

Informationen zur standardmäßigen Apple-Pay-Integration (einschließlich Girocard) finden Sie in der Dokumentation zu Apple Pay.

Paygate-Schnittstelle: Server-zu-Server

Definitionen

Datenformate

Format	Beschreibung
a	alphabetisch
as	alphabetisch mit Sonderzeichen
n	numerisch
an	alphanumerisch
ans	alphanumerisch mit Sonderzeichen
ns	numerisch mit Sonderzeichen
bool	Bool’scher Ausdruck (true oder false)
3	feste Länge mit 3 Stellen/Zeichen
..3	variable Länge mit maximal 3 Stellen/Zeichen
enum	Aufzählung erlaubter Werte
dttm	ISODateTime (JJJJ-MM-TTThh:mm:ss)

Abkürzungen

Abkürzung	Beschreibung	Kommentar
CND	Bedingung (condition)
M	Pflicht (mandatory)	Wenn ein Parameter Pflicht ist, dann muss er vorhanden sein
O	optional	Wenn ein Parameter optional ist, dann kann er vorhanden sein, ist aber nicht erforderlich
C	bedingt (conditional)	Wenn ein Parameter bedingt ist, dann gibt es eine Bedingungsregel, die angibt, ob er Pflicht oder optional ist

Hinweis: Bitte beachten Sie, dass die Bezeichnungen der Parameter in Groß- oder Kleinbuchstaben zurückgegeben werden können.

Anfrage-Elemente

Um eine Server-zu-Server-Zahlung mit Girocard zu starten, verwenden Sie bitte folgende URL:

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

Hinweis: Aus Sicherheitsgründen lehnt das Paygate alle Zahlungsanfragen mit Formatfehlern ab. Bitte übergeben Sie deshalb bei jedem Parameter den korrekten Datentyp.

Die folgende Tabelle beschreibt die verschlüsselten Übergabeparameter:

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Key Format CND Description

MerchantID

ans..30

M

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

msgver

ans..5

M

Computop Paygate Message version. Valid values:

Value	Description
2.0	With 3-D Secure 2.x a lot of additional data were required (e.g. browser-information, billing/shipping-address, account-info, ...) to improve authentication processing. To handle these information the JSON-objects have been put in place to handle such data. To indicate that these data are used the MsgVer has been implemented.

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

RefNr

ans..30

O

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 Computop settlement file (CTSF) we cannot add the additional payment data.

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three letters DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop.

OrderDesc

ans..768

M

Description of goods and prices. Intended purpose on the statement of account

card

JSON

M

Card data, brand=girocard

Capture

an..6

OM

Determines the type and time of capture.

Capture Mode	Description
AUTO	Capturing immediately after authorisation (default value).
MANUAL	Capturing made by the merchant. Capture is normally initiated at time of delivery.
<Number>	Delay in hours until the capture (whole number; 1 to 696).

channel

a..20

O

Indicates the type of channel interface being used to initiate the transaction. Values accepted:

WEBSITE
MOBILE_APP

credentialOnFile JSON C Object specifying type and series of transactions using payment account credentials (e.g. account number or payment token) that is stored by a merchant to process future purchases for a customer. Required if applicable.

tokenData JSON M Token Data, structure: see below

MerchantIDExt ans..128 M Apple Merchant Identifier

Parameter für Girocard E-Commerce-Zahlung

Antwort-Elemente

Die folgende Tabelle beschreibt die Parameter, die das Paygate als Antwort zurückgibt:

es können jederzeit neue Parameter hinzugefügt bzw. die Reihenfolge geändert werden

die Parameter (z.B. mid, RefNr) sollten nicht auf Groß-/Kleinschreibung geprüft werden

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Key	Format	CND	Description
mid	ans..30	M	MerchantID, assigned by Computop
PayID	an32	M	ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request.
XID	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment
Code	an8	M	Error code according to Paygate Response Codes (A4 Error codes)
Status	a..20	M	Status of the transaction. Values accepted: `AUTHORIZED` `FAILED`
Description	ans..1024	M	Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)

Antwort-Parameter für Girocard E-Commerce-Zahlung

JSON-Objekt tokenData

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Key	Format	CND	Description
tokenCryptogram	string	M	Cryptogram as received from Tokenization Service.
eci	string	M	Payment system specific Electronic Commerce Indicator. For MasterCard, if not received in payload, use value "2".
tokenRequestor	string	M	Token Requestor. Possible values: applePay googlePay merchantTokenization
tokenRequestorID	string	C	Token Requestor ID assigned by the card scheme. Required for MasterCard merchant tokenization.

Schema

BASEURL= https://www.computop-paygate.com/schemas

Schema

{
    "$schema": "http://json-schema.org/draft-07/schema#",
    "$id": "BASEURL/tokenData.json",
    "title": "tokenData",
    "description": "Token Data",
    "type": "object",
    "properties": {
        "tokenCryptogram": {
            "type": "string",
            "description": "Token cryptogram."
        },
        "eci": {
            "type": "string",
            "description": "Electronic Commerce Indicator."
        },
        "tokenRequestor": {
            "type": "string",
            "description": "Token requestor."
        },
        "tokenRequestorID": {
            "type": "string",
            "description": "Token requestor ID."
        }
    },
    "required": ["tokenCryptogram", "tokenRequestor, "eci"],
    "additionalProperties": false
}

Beispiel

Sample

{
    "tokenCryptogram": "YwAAErsAAcll8GEDuiS4gFlgAgA=",
    "eci": "7",
    "tokenRequestor": "merchantTokenization",
    "tokenRequestorID": "50129390584"
}

Wiederkehrende Zahlungen

Girocard E-Commerce bietet die Möglichkeit wiederkehrender Zahlungen, die sich immer auf die über Apple Pay getätigte Erstzahlung beziehen müssen.

Diese wiederkehrenden Zahlungen werden bei der ausgebenden Bank nicht online autorisiert, sondern nur in die Clearing-Datei aufgenommen.

Beachten Sie bitte, dass das Konto möglicherweise nicht über ausreichende Deckung verfügt oder nicht existiert, da zum Zeitpunkt der wiederkehrenden Zahlung keine Online-Autorisierung (Validierung) erfolgt.

Anfrage-Elemente

Um eine Server-zu-Server-Zahlung mit Girocard zu starten, verwenden Sie bitte folgende URL:

https://www.computop-paygate.com/girocard.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:

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Key

Format

CND

Description

MerchantID

ans..30

M

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

msgver

ans..5

M

Computop Paygate Message version. Valid values:

Value	Description
2.0	With 3-D Secure 2.x a lot of additional data were required (e.g. browser-information, billing/shipping-address, account-info, ...) to improve authentication processing. To handle these information the JSON-objects have been put in place to handle such data. To indicate that these data are used the MsgVer has been implemented.

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

RefNr

ans..30

O

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 Computop settlement file (CTSF) we cannot add the additional payment data.

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three letters DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop.

OrderDesc

ans..768

M

Description of goods and prices. Intended purpose on the statement of account

Capture

an..6

OM

Determines the type and time of capture.

Capture Mode	Description
AUTO	Capturing immediately after authorisation (default value).
MANUAL	Capturing made by the merchant. Capture is normally initiated at time of delivery.
<Number>	Delay in hours until the capture (whole number; 1 to 696).

credentialOnFile

JSON

M

Object specifying type and series of transactions using payment account credentials (e.g. account number or payment token) that is stored by a merchant to process future purchases for a customer.

Please note that only type : recurring, initial payment : false is allowed to be sent.

InitialPayID

an32

M

PayID received in Paygate response from initial Girocard Apple Pay payment.

Parameter für wiederkehrende Zahlungen

Antwort-Elemente

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

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Key	Format	CND	Description
mid	ans..30	M	MerchantID, assigned by Computop
PayID	an32	M	ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request.
XID	an32	M	ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate
TransID	ans..64	M	TransactionID provided by you which should be unique for each payment
Code	an8	M	Error code according to Paygate Response Codes (A4 Error codes)
Status	a..20	M	Status of the transaction. Values accepted: `AUTHORIZED` `FAILED`
Description	ans..1024	M	Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!
UserData	ans..1024	O	If specified at request, Paygate forwards the parameter with the payment result to the shop.
MAC	an64	M	Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here: HMAC Authentication (Request) HMAC Authentication (Notify)

Antwort-Parameter für wiederkehrende Zahlungen

Space shortcuts

Page tree

Über Girocard E-Commerce

Paygate-Schnittstelle: Server-zu-Server

Definitionen

Datenformate

Abkürzungen

Anfrage-Elemente

Antwort-Elemente

JSON-Objekt tokenData

Schema

Beispiel

Wiederkehrende Zahlungen

Anfrage-Elemente

Antwort-Elemente

Paygate

Computop

Help

Intranet Tools