How to create an API call
Building an API call to Pay-Jet Cockpit always follows the same sequence:
Libraries for HMAC and Blowfish
Here are some libraries supporting you with HMAC calculation and Blowfish-Encryption: Implementation Sources
Merchant credentials
You will receive your merchant credentials after signing up the contract.
The merchant credentials consist of:
- MerchantId: Your MerchantId on Pay-Jet Cockpit
- HMAC-password: A password to calculate the MAC-value to protect specific values in the request (e.g. amount, currency) or response (e.g. status, code)
- Blowfish-password: A password to encrypt your request to Pay-Jet Cockpit and its response.
You may receive a multiple set of MerchantId's and password's as a MerchantId is used to unite a set of configurations (e.g. paymethods, currencies, services).
Example
We would like to create a payment for 12,34 EUR with english language for the hosted payment page with additional template parameters.
3-D Secure 2.x shall be used in case that the customer selects credit cards (e.g. Mastercard, VISA, American Express), but also other paymethods like PayPal, Direct Debit, Sofort, ... can be selected.
Therefore we need:
- MAC calculation to secure amount and currency
- put API parameters together - unencrypted
- encrypt all API parameters → by this we will get "Data" + "Len" for the API request
- add plain parameters to customize Hosted Payment Page using (HPP) with a template, e.g. language="en" for using the HPP with preselected english language
- send the API request to the desired endpoint.
MAC calculation
The MAC is calculated always like this: HmacSHA256("PayId*TransID*MerchantID*Amount*Currency", "YourHmacPassword") where:
| Key | Value | Comments |
|---|---|---|
| PayId | Referenced PayId | May be empty, e.g. for creating an initial payment process or risk management request; is used with subsequent requests like capture/refund. |
| TransId | Your transactionId to reference / identify your request | Your own reference to identify each request / payment process. |
| MerchantId | Your MerchantId | Your MerchantId assigned to you by Pay-Jet identifiying this request. |
| Amount | Amount in smallest unit of currency, e.g. 123=1,23 (EUR) | Amount of this request; may be empty if not used, e.g. for status inquiries. |
| Currency | Currency of payment process in ISO 4217, e.g. EUR, USD, GBP | Currency of this request; may be empty if not used, e.g. for status inquiries. |
| YourHmacPasswort | Your HMAC-password assigned to you by Pay-Jet | Your HMAC-password assigned to a specific MID; if you have different MIDs you will have different HMAC passwords, too. |
Notes:
- in case that a value is not present just leave it empty, e.g.:
- with amount/currency, without PayId to initiate a new payment - like in this example:
HmacSHA256("*TID-4453732122167114558*yourMerchantId*1234*EUR", "mySecret") - with amount/currency, without PayId, without TransId:
HmacSHA256("**yourMerchantId*1234*EUR", "mySecret") - with PayId, without amount/currency:
HmacSHA256("fe3f002e19814eea8aa733ec4fdacafe*TID-4453732122167114558*yourMerchantId**", "mySecret")
- with amount/currency, without PayId to initiate a new payment - like in this example:
you will find more details for HMAC-calculation
for requests: HMAC Authentication (Request)
- for responses/notify: HMAC Authentication (Notify)
Raw parameters before encryption
The raw parameters define basic settings for this payment call, e.g. your MerchantId, amount, currency, your reference and URLs for success, failure and notify:
| Key-Value | Comments |
|---|---|
| MerchantID=yourMerchantId | Your MerchantId to identify your request at Pay-Jet Cockpit |
MsgVer=2.0 | Indicate that 3-D Secure 2.x shall be used; Specially for 3-D Secure 2.x it is useful to provide additional data (like billing- and shipping-address) to improve frictionless processing (i.e.: payment is authenticated without challenge). These additional data are provided in JSON-structure. |
TransID=TID-18724420542167170812 | Your request identifier |
| RefNr=RG123-2021 | Your payment process reference |
| Amount=1234 | The desired amount in smallest currency unit, e.g. 1234 + EUR → 12,34 EUR |
| Currency=EUR | and currency |
| URLSuccess, URLFailure, URLBack | URLs for forwarding the customer in case of success, failure, cancel |
| URLNotify | URL to receive Pay-Jet Cockpit notifies |
| Response=encrypt | Pay-Jet Cockpit shall respond with encrypted data |
| Language=en | Customer wants english language |
MerchantID=yourMerchantId&MsgVer=2.0&TransID=TID-18724420542167170812&RefNr=RG123-2021&Amount=1234&Currency=EUR&URLSuccess=https://www.yourshop.info/success.php&URLFailure=https://www.yourshop.info/failure.php&URLNotify=https://www.yourshop.info/notify.php&Response=encrypt&MAC=ca3c75eaf2120dfd15de77af2398b1561d8473f647b72aa7270fde94df7756d6&Language=en
As "=" and "&" are used for building key-value-pairs these characters must not be part of any value.
Do not send empty values, but only keys which are required and really having values.
For credit card processing with 3-D Secure 2.x (EMV 3DS) you must add "MsgVers=2.0"
Hosted Payment Page works like a proxy for the other payment forms (i.e. Credit Card Form (PaySSL), Direct Debit Form (PaySDD), paymethod specific forms (e.g. PayPal))
- so you have to add "MsgVers=2.0" to enable 3-D Secure 2.x for Credit Card Form (PaySSL)
- you may supply other key-values for other paymethods (e.g. PayPal)
Encryt parameters into Data/Len
The raw parameters need to be encrypted via Blowfish ECB and then hex-encoded. We provide you predefined functions in our toolkits for a quick start. The above shown and unencrypted data will be encrypted into:
Len=342& Data=550a705ffb8fb2d59f72a116a55b26ef97d92d6ebec45ea10efe79b05d93f6fd6a69e8f810509d7e754899153e459f05cfd2c9bd9e71f92acda33e453f329a641328b32411b5c08ded80711c13d64e01d2cbae26a884f8c8781db17f31434fe34032ec5ef961dfb53006add8abc7f9cfa39d582962f3a70af105eb1f2240376e358d7cf8a7dadfef6afeac3bf0f043f578f5040995a7b29ca23fbcc0f84f5e416fe1ef60c3ff58028b3aa017b2fb50715fc3ef42b3947cc89f2639f61f6dbd8fea1f0b17716115676b2762ea14f0ca8d6fe1ef60c3ff58028b3aa017b2fb50715fc3ef42b3947cc86f80ef28614f1f739345550e4a0fc83bc7ca605f8477fcb5fa93da00daa0bddf9faace1829eeea32c8ffd87cffaf85930479d79b121d2662172cd81022e35232777bedb997aeb1deba02dc2fc4af5297802ace7338757a9058e220fd1c0abb8b2f3d8309b9d7375cae9897dc2aeda201
Notes:
To ease your integration we provide predefined functions to help you with Blowfish ECB:
| Your language | Where to find |
|---|---|
| ASP | txmsCrypto.dll // txmsCrypto.BlowFish |
| ASP.NET | CompuTop.Core.Crypto.dll // CompuTop.Core.Crypto.BlowFish |
| Java | Blowfish.java |
| PHP | function.inc.php ctHMAC ctEncrypt ctDecrypt |
The value for "Len" is the string length of the unencrypted parameter string built in the step before.
Sending the API request
A request can be sent either via GET or POST. We recommend to use POST for two reasons:
with GET the parameter length is restricted to 2048 bytes depending on the browser, while with POST the request length is limited to 5120 bytes; If you require longer strings please contact Pay-Jet Support
via GET the parameters are attached to the URL which can be easily manipulated by a customer - therefore Backoffice prevents manipulation using Blowfish encryption
Checking the Cockpit response
Server-2-server response
With server-2-server requests a request will respond with a direct response containing
- a status indicating success or failure of transaction
- a code (response code) explaining details of transaction along with a description
- other data like PayId for each payment process
- and other data depending on the type transaction
Payment page / ansynchronous notification
In case of a redirect payment an ansynchronous notification is sent to your system indicated by a URLnotification.
The response can be either encrypted or in plain text - we recommend an encrypted response.
Common
Please check:
- just checking whether "URLFailed" or "URLSuccess" has been called is not sufficient and can easily misused
- Response code: only "code=00000000" indicates a successful and completed action
- HMAC in Backoffice response is valid - to ensure that the message is not manipulated
Some tips on Cockpit responses
Some tips on responses
| Result | Description |
|---|---|
| Unexpected exception | Cockpit response not containing "code" and "status" a very likely reason is that you simply used
|
| Cockpit detected some error in request and a payment process has not been created. These payment processes can not be found in Backoffice. An overview of response codes can be found here: Response codes |
| A payment process with PayId has been created but the subsequent systems detected an error. An overview of response codes can be found here: Response codes |
| The amount is the first parameter which is checked. The amount must be given in numbers without decimals. But you may also simply have mixed up your MIDs and Blowfish-keys - just doublecheck. |
| Payment / process successful and completed |
| Payment / process pending |
A few URL calls to play with
Please find some test data to play here: Test Guide. However, the payments may result in error to prevent abuse.