Introduction

UrlNotify / Server-Response

Normally sends payment details to UrlNotify for Form-Payments (Hosted Payment Page, Credit Card Form, Direct Debit Form, PayPal, ....). 

For Server-2-Server requests the payment details are returned in Server-response. 

Payment details returned do depend on the paymethod that has been used.

Third-Party Notification Service (TPNS)

TPNS is used to inform a central management system with a set of basic payment details. This works for Form-Payments as well as for Server-2-Server requests and for Analytics actions. It also is used for multiple MIDs / Merchant entities.

TPNS endpoints need to be setup within . Please contact . 




Notification callback

 server will execute an HTTPS POST request directly to the web server of the Partner (URL) . To integrate with this notification, the Partner should supply with the IP address and the URL that leads to the callback entry point of the server. This is usually a small module/application, which constantly listens and waits for incoming HTTPS requests from the server. The server will send data via an HTTPS POST request to the server URL configured including all the relevant parameters in the HTTPS POST request.

The parameters will be transmitted in the HTTP Body as a Blowfish encrypted parameter string. The content type will be application/x-www-form-urlencoded; charset=iso-8859-1.

Note: Please note that the Notify-call is permitted only via Port 443 (SSL) for security reasons. The URL encoded parameters are transmitted in key-value pairs.


If one of these parameters (IP or URL) during time changes, the partner should notify to perform the related configuration changes.

For security reasons a common Blowfish Secret Key (password) will be shared between and the Partner regarding this notification process and the parameter MAC should be present in the callback request.

The calculation of the MAC value is done using SHA-256 algorithm and with the subsequent parameter values: PayID*XID*TransID*MerchantID*Status*Code.

The receiver should use the MAC SHA-256 algorithm, which nearly all programming languages support, to calculate the hash value with the HMAC key and the parameter values.


will submit a notification request via HTTP POST in order to transfer the authorization status and transaction details to the server URL as stored in the merchant configuration.

Key

Format

CND

Description

Beschreibung

Status

a..30

M

Status of the action performed: OK or FAILED

Status der ausgeführten Aktion: OK oder FAILED

Key

Format

CND

Description

Beschreibung
CCBranda..22OC

Card scheme brand (e.g. Visa, MasterCard, Maestro etc.)

Please note the spelling! According to table of credit card brands!

Bezeichnung der Kreditkartenmarke (z.B. Visa, MasterCard, Maestro etc.)

Bitte beachten Sie die Schreibweise gemäß Tabelle der Kreditkartenmarken!

MaskedPanan..19OCMasked card number (6X4). Format: 666666XXXXXX4444 (X masking digit)Maskierte Kartennummer (6X4). Format: 666666XXXXXX4444 (X maskiert eine Ziffer)

Key

Format

CND

Description

Beschreibung
TxTypeans..30M

Action name being performed which triggered the notification message.

Expected values such as:

  • Authorize
  • Capture
  • Credit
  • CreditEx
  • Increment
  • ReverseAuthorize
  • ReverseCapture
  • ReverseCredit
  • ReverseIncrement
  • ReverseSale
  • ReverseOrder

Name der ausgeführten Aktion, welche die Benachrichtigung ausgelöst hat.

Erwartete Werte wie:

  • Authorize
  • Capture
  • Credit
  • CreditEx
  • Increment
  • ReverseAuthorize
  • ReverseCapture
  • ReverseCredit
  • ReverseIncrement
  • ReverseSale
  • ReverseOrder
AQans..3OCAcquirer short code (valid for credit card payments only)Acquirer-Shortcode (nur für Kreditkartenzahlungen)
PayTypeans..30M

Showing the name of the payment type used. 

Expected values such as:

  • GICC
  • Omnipay
  • PayPal
  • etc.

Note: Please get in touch with Merchant Services team for a full list of supported payment methods.

Name der verwendeten Zahlungsart. 

Erwartete Werte wie:

  • GICC
  • Omnipay
  • PayPal
  • etc.

Hinweis: Für eine vollständige Liste der unterstützten Zahlungsmethoden wenden Sie sich bitte an den Händlerservice.

TimeStampans..20MTimestamp of the performed original TxType within format: DD.MM.YYYY HH:MM:SSZeitstempel des ausgeführten originalen TxType im Format: DD.MM.YYYY HH:MM:SS
Channelans..30M

The entry method/channel which was used for the original TxType triggering this notification.

Values like: Client, Server, Analytics, Payshow

Eingabemethode/Kanal, die für den ursprünglichen TxType verwendet wurde, der diese Benachrichtigung ausgelöst hat.

Werte wie: Client, Server, Analytics, Payshow

TerminalIDan..8CAcquirer Terminal ID (valid for credit cards only)Acquirer Terminal ID (nur für Kreditkarten)
VUNrn5..12CMerchant contract number. The length depends on the acquirer. (valid for credit cards only)Händlervertragsnummer. Die Länge hängt vom Acquirer ab. (nur für Kreditkarten)

Response parameters for Third-party notification service via socket connections


The request will be sent in real-time. If the specified URL is not accessible will retry the notification according to the following time schedule.

Repeat

Waiting time

Time after 1. Notify

0

instantly

0

1

00:01 h

00:01 h

2

00:08 h

00:09 h

3

00:27 h

00:36 h

4

01:04 h

01:40 h

5

02:05 h

03:45 h

6

03:36 h

07:21 h

7

05:43 h

13:04 h

8

08:32 h

21:36 h

If the maximum number of repeats is reached and the Partner Web Service is still not available the retries will no longer be re-attempted.