Following table lists all card brands that can be uses via

Following table lists all card brands that can be uses via the Hosted Payment Page. When submitting the value CC in parameter PayTypes all brands are displayed that are configured for a certain merchant. Selecting specific brands can be done by submitting a string of the desired brand names separated by pipe signs.

Process of payment

To make payments via the Hosted Payment Page you send a request to following URL with HTTPS GET or HTTPS POST:

All details required for payment processing are forwarded as parameters. The parameters are encrypted with Blowfish to ensure that neither the customer nor a third party can manipulate the data.

When calling the form

After the payment has been made

Calling the Hosted Payment Page

Calling the Hosted Payment Page starts with the correct composition of the parameters which consist of a key and a value and which are separated by an equals sign (=):

All parameters are assembled in a character string and separated by the character &:

Notice: Since the characters "=" and "&" are used as separating characters, these characters cannot be transmitted as values. All values which you transmit without BlowFish-encryption must be URL-Encoded.

A correct parameter character string for

The Data parameter contains the sensitive payment details such as amount and currency. The encrypted bytes are Hex-encoded and completed to two characters from the left with a zero. Encryption is via Blowfish ECB and is available to you as source-code and components.

The Len parameter is very important for encryption because it contains the length of the unencrypted(!) character string in the Data parameter. Since the data quantity to be encrypted is increased by a multiple of 8 in the case of the Blowfish encryption, the correct length of the character string must be known for decryption. Otherwise accidental characters emerge at the end of the character string.

The parameters are transmitted via HTTPS POST or HTTPS GET. The recommended transmit method is HTTPS POST because the parameter character string in the case of GET is attached to the URL, which is limited to 2048 bytes depending on the browser.

Notice: Please note that the maximum length of a payment request is limited to 5120 characters. If you require longer strings please contact

The following listings show the development of a payment request. The first listing is the unencrypted parameter character string:

Notice: Please note that a value is to be assigned to each parameter. Do not transmit empty parameters, as this can cause the payment to fail.

This character string is encrypted and transmitted as the Data parameter. The HTTPS GET request for the Hosted Payment Page looks like this:

Notice: Please note that parameters like Language or URLBack are transmitted unencrypted. A table with all possible unencrypted parameters can be found also witihn this document.

Multiexcerpt include
SpaceWithExcerpt

EN MultiExcerptName Platform-Kurz PageWithExcerpt Wording

interface

Parameters of the Hosted Payment Page

These parameters are mandatory for all payment methods and has to be submitted Blowfish-encrypted within the Data parameter to the Hosted Payment Page.

Notice: Please take all further parameters specifically for a payment method from the manual of that respective payment method.

The following table describes the encrypted payment request parameters:

MerchantID

ans..30

M

TransID

ans..64

M

TransactionID which should be unique for each payment

RefNr

ns..30

O

Unique reference number

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent)

Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217

OrderDesc

ans..384

M

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm

UserData

ans..1024

O

URLSuccess

ans..256

M

false hideColumns true sparkName Sparkline hidePane true datepattern dd M yy id 1622197488766_-1462250635 worklog 365|5|8|y w d h m|y w d h m isOR AND separator Point (.) order 0

Multiexcerpt MultiExcerptName HPP_request Table Transformer dateFormat dd M yy export-word false show-source false export-csv false id 1622197488771_-163318905 transpose false worklog 365|5|8|y w d h m|y w d h m separator . export-pdf false sql SELECT * FROM T* Multiexcerpt include SpaceWithExcerpt EN MultiExcerptName Request_AmountMac DisableCaching true PageWithExcerpt Reuse API Table Excerpt Include static true name TransID page TransID type page Key Format CND Description Beschreibung RefNr ns..30 O Unique reference number exact format depends on the available paymethods for your MerchantId. Please choose your format in that way that all paymethods are covered. eindeutige Referenznummer das genaue Format hängt von den Zahlarten Ihrer MerchantId ab. Wählen Sie das Format so, dass alle möglichen Zahlarten kompatibel sind. OrderDesc ans..384 M Description of purchased goods, unit prices etc. Please note: The first 27 characters appear on the customer-account statement. You can view the full data in

URLFailure

ans..256

M

Parameters for Hosted Payment Page

Following parameters are optional and can be submitted unencrypted to the Hosted Payment Page:

Response

a7

O

URLNotify

ans..256

M

Parameters for Hosted Payment Page

Following parameters are optional and can be submitted unencrypted to the Hosted Payment Page:

Parameter

Format

CND

Description

Template

ans..20

O

CCTemplate

ans..20

O

SDDTemplate

ans..20

O

Language

a2 (enum)

O

Language code: <de> German, <al> Albanian, <at> Austrian, <cz/cs> Czech, <dk> Danish, <en> English, <fi> Finish, <fr> French, <gr> Greek, <hu> Hungarian, <it> Italian, <jp> Japanese,  <nl> Dutch, <no> Norwegian, <pl> Polish, <pt> Portuguese, <ro> Romanian, <ru> Russian, <es> Spanish, <se> Swedish, <sk> Slovakian, <sl> Slovenian, <tr> Turkey, <zh> Simplified Chinese.

No details means the language is German.

Take the possible values from the column PayType within the table of payment methods given above.

Optional parameters for Hosted Payment Page

Corporate PaymentPage: XSLT layout for forms

You can change the parameter Template to create an individual layout for your Hosted Payment Page form which exactly matches the shop layout To this end your graphic designer can design an HTML-template in the shop-design based on XSLT (Extensible Stylesheet Language Transformation). 

The XSLT templates for the Hosted Payment Page form have several advantages:

1. Merchants can bypass the costly PCI-security authorisation
2. The Hosted Payment Page is responsive, i.e. it works on Smartphones, Tablets or on the Laptop

For general information about XSLT see www.w3.org.

The subsequent conventions apply for the use of the Corporate Paypage with XSLT:

File names

A XSL file designed by you defines your individual layout. The associated XML file contains the texts that are to be displayed on the form. Hence, multilingualism is easy. Always use your MerchantID in the names of the files.

In order not to receive safety notices, please ensure that external image sources are retrieved via SSL.

In order to call the individual layout, use the ‘Template’ parameter with your MerchantID and attach it unencrypted to the call of the form of Hosted Payment Page, for example:

Hidden Fields

The following hidden fields must be implemented so that the values can be passed on when sending the form:

Language selection

The language selection on the Hosted Payment Page form occurs automatically depending on the parameter Language. Other language areas are filtered out. If you wish to access the field of another language area e.g. with JavaScript, you can do so via the following path: paygate/language/@name.

XML structure

The ‘Language’ parameter controls which section of the XML text file is read out. German ‘de’ is always used as standard.

The XML file should have the following basic structure:

<?xml version="1.0" encoding="utf-16"?>

      </languages>

            <language name="de">

                  <title>Zahlung</title>

                  ...

            </language>

                  <title>Zahlung</title>
                  ...
            </language>
            <language name="en">

                  <title>Payment</title>

                  ...

            </language>

                  <title>Payment</title>
                  ...
            </language>
      </languages>

‘UTF-8’ is also possible for the codingencoding.

With <xsl:variablename=““ select=“paygate/language/@name”/> you can directly address an XML language section from the XSL file.

For an overview of which parameters are rendered by the Hosted Payment Page, please examine the following structure (XSL file is rendered against the following XML string):

following XML string):

strXML = "<?xml version='1.0' encoding='windows-1252'?>" & _

<paygate>

<paygate>
      <merchantID>...</merchantID>

      <len>257</len>

      <data>E98D4...F7065</data>

      <template>

      <template>
      <urlBack><![CDATA[http://www.google.de]]></

      <paymentMethods>

urlBack>
      <paymentMethods>
            <VISA type="CC" displayName="Visa"/>

            <MasterCard type="CC" displayName=

"MasterCard"/>
            <AMEX type="CC" displayName="American Express"/>

            <DINERS type="CC" displayName="Diners Club International"/>

            <Discover type="CC"

 displayName="Discover"/>
            <JCB type="CC" displayName="JCB"/>

            <EDD lowercase="edd">

            <PayPal lowercase=="paypal">

            <iDEAL lowercase=="ideal">

      </paymentMethods>

      <language name="de">

            <title>Zahlung</title>

            ...

      </language>

</paygate>

JavaScript

You can find individual JavaScript methods either in the HEAD section of your XSL file or within the file main.js that can be found in the images folder at Templates/imagesMerchantID_PaymentPage/js.

Notice: Please do not use any external links to your JavaScript!