Page History

Introduction

Therefore request and response is encrypted either with Blowfish (default) or with AES encryption (upon request at

Additionally sensitive data like MerchantId, amount and currency are hashed with a separate HMAC-password using SHA256-algrorithm.

To check your implementation we provide a tool

• to validate MAC-value (API-parameter MAC)
• to validate Len/Data value (API-parameter Len and Data)

You will find a short description how to use this tool.

Usage

The tool itself will start like this:

Image Added

Building an encrypted payment request

If you already have a

Then you start creating a basic request

• for creditcard requests using 3-D Secure 2.x with button "Set simple Call with MsgVer=2.0" (4)
• or simple payment calls (e.g. PayPal) with button "Set simple Payment Call" (5)

If you want an encrypted

If you want to use payment methods with forms or redirect you have to provide URLs, too. Some sample URLs can be added with button "" (8).

To enable simulation mode (i.e. no downstream-systems are required) pls. use button "Add Simulation (OrderDesc:0000)" (8). By using this option you can simulate all response codes just by replacing "0000" with your desired one.

To add additional parameters e.g. for recurring payments which are customer or merchant initiated

After putting a basic payment request together you may modify e.g. amount from 123 (i.e. 1,23) into another value or change the currency from EUR (i.e. USD) - depending on your paymethod setup.

if you want to use your own MerchantId pls. use the button "Put your MerchantID" and the generic test MerchantId will be replaced your yours.

you are now basically ready to go and start encrypting your request with button "Encrypt" (15).

Adding unencrypted parameters to payment request

These payment forms use unencrypted data to

• modify their background or font color
• or display a merchant logo - depending on the template
• or select the template you want to use

Adding additional JSON parameters (base64-encoded)

Mostly for credit card payments additional parameters like e.g. browser information or external 3-D Secure data may be used. These are base64-encoded and then added to the field (10) for "Plain Request".

Therefore form "Base64-encoding" (D) can be used which already provides some samples in

Base64-encoded values are also sent as key-value-pair:

• e.g.: credentialOnFile=base64('{"type": { "unscheduled": "CIT" }, "initialPayment": false }')
• will be sent as: credentialOnFile=ew0KICAgInR5cGUiOiB7DQogICAgICAgICJ1bnNjaGVkdWxlZCI6ICJDSVQiDQogICAgfSwNCiAgICAiaW5pdGlhbFBheW1lbnQiOiBmYWxzZQ0KfQ==

Using predefined MerchantId Generic3DSTest

You can simply try and use a

Encrypt and send request

After you have built your plain (unencrypted) payment request and eventually added some template parameters by using:

• button "Set simple Call with MsgVer=2.0"
• button "Add response=encrypt"
• button "Add URLs"
• button "Add Simulation (OrderDesc=Test:0000)"
• button "Set React templates HPP, CC, SDD"

Image Added

you are ready to go.

After pushing button "Encrypt" (7) the payment request is built and encrypted and shown on the next form:

Image Added

Here you will see:

• (1) plain request data which will be encrypted into Len + Data
• (2) your MerchantId - or the

  Multiexcerpt include
  SpaceWithExcerpt EN MultiExcerptName Platform-Kurz PageWithExcerpt Wording

  default one
• (3) value for parameter "Len" of encrypted request
• (4) value for parameter "Data" of encrypted request
• (5) additional request data which will not be encrypted
• (6) values that are used for HMAC-calculation
• (7) the calculated HMAC-value itself
• (8) finally a button to initiate the payment request
• (9) or a button to show a QR-code which can be scanned by your smartphone to initiate a payment request there

pls. note that the unencrypted parameters are used for templates with payment forms. The template name (here: "Template=PaymentPageDropDown_v1") needs to match the 

Samples

...