About paydirekt
General information about paydirekt
Paydirekt is a new online payment service for all German banks and savings banks and is as trustworthy as your own bank. At the heart of paydirekt is the trusted giro account through which the entire processing takes place.
The buyer registers for paydirekt via their own bank’s online system. Each payment is authorised by the buyer’s own bank and immediately posted to the giro account. Buyer authentication is via an adaptive authentication process. Each payment also requires an age verification.
The benefits for the merchant are simple connection of paydirekt to the shop system, highly secure transactions due to the processing of participating banks and savings banks and their credit rating, payment guarantee as soon as the posting is activated after positive payment confirmation and easy handling of returns and complaints.
|
Further information can be found on the website of paydirekt (https://www.paydirekt.de).
Process flow chart
|
paydirekt process flow
interface
Calling the paydirekt interface
A payment by paydirekt may be done in two steps, where first of all a payment for an order is initialised before you capture it separately on dispatching the goods. Alternatively the payment can be processes within one step as a sale transaction. The subsequent transactions then take place via a server-to-server connection. Hence, you can capture these payments or issue a credit in the event of a goods return.
In order to process a payment with paydirekt via a form, please use the following URL:
|
|
Parameters for payments with paydirekt
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
paydirekt oneKlick
In contrast to standard checkout the customer must register himself one-time for oneKlick. The registration is done with a separate payment (AUTHORIZE) with which cannot be used for further actions. In case of successful registration
returns a token (BillingAgreementID), that can be used for all subsequent oneKlick transactions. Moreover the customer has to confirm an E-Mail before oneKlick can be used.
Optionally an URL can be submitted, to which a notify will be send, when the customer has confirmed or revoked the eMail. This URL can be stored statically in the merchant configuration or transferred via the request parameter "URLConfirm".
For an oneKlick checkout the BillingAgreementID has to be submitted to . Instead of forwarding to paydirekt now the checkout will be finished without further customer confirmation.
oneKlick registration
The oneKlick registration can be done as a separate process or combined with a normal checkout. Separate registration is processed via a separate form. After the registration all subsequent transactions are made via a Server-to-Server connection. With oneKlick merchants can divide payments into authorisation and capture or can capture immediately (SALE).
Separate oneKlick registration as well as registration during checkout always is processed via the form with the following URL:
|
Notice: DeviceID and DeviceFingerPrint must be unique for each customer's terminal device. Paydirekt offers an SDK for iOS and Android, in order to create an unique DeviceId. For web applications libraries like Fingerprint.js ( https://github.com/Valve/fingerprintjs2 ) can be used to create an unique fingerprint.
|
Parameters for oneKlick registration with paydirekt
usageAgreement
|
Example usageAgreement as JSON string
{
"amount":{
"amount":50,
"currency":"EUR"
},
"startDate":"2019-09-01",
"recurrenceInterval":{
"intervalUnit":"WEEK",
"interval":8
}
} |
The parameter created within JSON format must be Base64 encoded.
| ||||||||||||||||||||||||||
Result parameters for URLNotify, URLSuccess and URLFailure in case of paydirekt
The following table describes the result parameters which transmits to your URLConfirm. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
| ||||||||||||||||||||||||||||||||
Result parameters for URLConfirm in case of paydirekt
Calling the paydirekt oneKlick interface
Payments with oneKlick are possible via a server-to-server connection with help of the BillingAgreementID. Payments with oneKlick can be made as authorisation which has to be captured separately or as a sale transaction with immediate capture.
To carry out a oneKlick payment for paydirekt via a Server-to-Server connection, please use the following URL:
|
|
Parameters for payments with paydirekt oneKlick
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Result parameters for URLNotify, URLSuccess and URLFailure in case of paydirekt oneKlick
Capture
Captures are possible via a Server-to-Server connection. To carry out a Capture for paydirekt via a Server-to-Server connection, please use the following URL:
|
|
Parameters for paydirekt captures
| |||||||||||||||||||||||||||||||||||
Result parameters for paydirekt captures
Credit with reference
Credits (refunds) are possible via a Server-to-Server connection. Credits are possible up to 200% of the captured amount, if this is configured by for the merchant and that payment method. To carry out a credit with a reference transaction, please use the following URL:
|
|
Parameters for credits of paydirekt payments
| ||||||||||||||||||||||||||||
Result parameters for credits of paydireckt payments
Reverse
Reversals are possible via a Server-to-Server connection. In order to reverse a paydirekt transaction, please use the following URL:
|
|
Parameters for reversals of paydirekt payments
| ||||||||||||||||
Result parameters for reversal of paydirekt payments
Batch processing via the interface
This section describes the parameters which must be transferred within the data set (Record) for executing a paydirekt payment and which information can be found within the response file about the payment status.
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 paydirekt payment within a Batch file to be submitted is the following:
|
Example for Master MID function:
|
|
Description of fields within the record for Batch files
The record area within the response file for Batch transactions looks as follows:
|
|
Description of result parameters within the record for Batch files