Introduction to WSPayForm

WSPayForm integration method provides merchants with a complete solution for secure credit card authorization.
WSPayForm contains the complete functionality that satisfies technical and safety requirements:

  • Validation of customer personal and credit card data
  • Generating encrypted signature in order to prevent unwanted data exchange
  • 3D Secure authentication in accordance to 3DS 2.1
  • Secure connection through TLS 1.2 protocol
  • Compliance with the PCI DSS standards

Prerequisites

After the merchant fills in an application form and registers with WSPay, the parameters which are needed for implementation will be provided:

  • URL endpoints - list of endpoints needed for communication
  • Shop ID - unique identification of merchants shop on WSPay
  • Secret key - key used for generating signature
  • Secret key must be kept in secrecy to protect the merchants privacy.

UI Customization

WSPayForm is highly customizable.
Customization of WSPayForm can be done through:

  • WSPayForm style builder - intuitive style builder which allows customization of most UI elements available on WSPayForm
  • WSPayForm sizes - merchant can choose between multiple payment form sizes

All WSPayForm customization is done through "Styles" option inside WSPay Administration.

WSPayForm sizes

Currently available form sizes are:

  • Default/standard form
  • Form without user data
  • Card data, amount and order number
  • Card data only
  • Logo, header and card data
  • Form with user and payment type entry fields

Implementation

WSPayForm uses redirection for communication with merchants shop.
Merchant will redirect customer to WSPayForm. After successful, unsuccessful or cancelled transaction WSPayForm will, depending on the status of transaction, redirect customer back to URL defined by merchant.

To redirect customer to WSPayForm one of two methods can be used:

  • Get WSPayForm URL
  • Submit HTML form

Mandatory parameters

List of mandatory parameters that must to sent to WSPayForm.

ShopID
string
ShopID represents unique identification of merchants shop on WSPay.
ShopID is received from WSPay after signing the request for using WSPay service.

ShoppingCartID
string
ShoppingCartID represents unique identification of transaction in merchants system.
It must be unique. In case there is already a successful transaction with the same ShoppingCartID, that ID cannot be used again for future transactions.
ShoppingCartID should not contain any character different from:
  • Letters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
  • Numbers: 0123456789
  • Special characters: _-.
ShoppingCartID maximum length is 255 characters.

Version
string
Version parameter represents version of WSPay form to be used.
For successful communication 2.0 must be used.

TotalAmount
string
TotalAmount is amount for which the customer will be charged, expressed in agreed currency.
TotalAmount parameter must be formatted without dots as thousand separators.
Decimal point can only be defined as comma.
After the decimal point, only the first two digits indicating the amount will be considered.

Example 1
Number: 3.650,35
TotalAmount: 3650,35

Example 2
Number: 27.650,00
TotalAmount: 27650,00
ReturnURL
string
ReturnURL represents HTTPS address where the customer will be redirected after successful transaction.
WSPayForm redirects to page defined in ReturnURL parameter and returns parameters based on transaction.

ReturnURL maximum length is 500 characters.

ReturnErrorURL
string
ReturnErrorURL represents HTTPS address where customer will be redirected in case of communication error or when 3 unsuccessful payments on WSPayForm occures.

ReturnErrorURL maximum length is 500 characters.

CancelURL
string
Represents HTTPS address where customer will be redirected in case if customer cancelled the transaction process or in the case of the form data entrance timeout.

CancelURL maximum length is 500 characters.

Signature
string
Represents a signature created from string formatted from following values in a following order using SHA512 algorithm:

ShopID
SecretKey
ShoppingCartID
SecretKey
TotalAmount
SecretKey

Note that TotalAmount parameter must be converted into string without dots and commas.

Example 1:
TotalAmount: 7250,88
Final format of TotalAmount parameter for hashing: 725088

Example 2:
TotalAmount: 35,00
Final format of TotalAmount parameter for hashing: 3500
Signature generator, available at signature.wspay.info, can be used to test signature validity.

Redirecting customer to WSPayForm

To redirect customer to WSPayForm one of two methods can be used:

  • Get WSPayForm URL
  • Submit HTML form

Get WSPayForm URL

Recommended way to redirect customer to WSPayForm is to get WSPayForm URL then redirect customer to given URL.
In order to get WSPayForm URL - request object in JSON format must be sent using HTTP POST to endpoint that will be provided by WSPay.

Request:

{
    "ShopID": "MYSHOP",
    "ShoppingCartID": "78",
    "Version": "2.0",
    "TotalAmount": "17,00",
    "ReturnURL": "https://myshop.com/success",
    "ReturnErrorURL": "https://myshop.com/error",
    "CancelURL": "https://myshop.com/cancel",
    "Signature": "23455eaf0029bac73613eb00d5242dcf2a5e39fa8d65b26905974dcf61bfbccdaaf0963d79dd73adae117ef108378a2b661faaba5c5ff4c33935fae13fad90a7"
}

Response:

// Successful response
{
    "TransactionId": "LTiEo4U5HEqPl8IFHHbeCA",
    "PaymentFormUrl": "https://form.wspay.biz/authorization?id=LTiEo4U5HEqPl8IFHHbeCA",
    "HasErrors": false,
    "Errors": []
}
// Unsuccessful response
{
    "TransactionId": null,
    "PaymentFormUrl": null,
    "HasErrors": true,
    "Errors": [
        {
            "Key": "E00017",
            "Message": "ReturnURL is mandatory."
        },
        { 
            "Key": "E00018",
            "Message": "CancelURL is mandatory."
        }
    ]
}
TransactionId
string
TransactionId represents a unique identification of payment form.

PaymentFormUrl
string
PaymentFormUrl represents a requested WSPayForm URL.

HasErrors
boolean
HasErrors represents a boolean value which defines is there any data in Errors parameter.

Errors
array
Errors parameter represents a list of errors. If response is successful, this list will be empty.
Key
string
Error key.

Message
string
Error message.

List of possible values can be found here.

Submit HTML form

Second way to redirect customer to WSPayForm is to submit HTML form inside HTML document to URL provided by WSPay.

<form action="[Provided by WSPay]" method="POST">
    <input type="hidden" name="ShopID" value="MYSHOP">
    <input type="hidden" name="ShoppingCartID" value="78">
    <input type="hidden" name="Version" value="2.0">
    <input type="hidden" name="TotalAmount" value="17,00">
    <input type="hidden" name="Signature" value="23455eaf0029bac73613eb00d5242dcf2a5e39fa8d65b26905974dcf61bfbccdaaf0963d79dd73adae117ef108378a2b661faaba5c5ff4c33935fae13fad90a7">
    <input type="hidden" name="ReturnURL" value="https://myshop.com/success">
    <input type="hidden" name="CancelURL" value="https://myshop.com/cancel">
    <input type="hidden" name="ReturnErrorURL" value="https://myshop.com/error">
    <input type="submit" value="Pay">
</form>

Optional parameters

Merchant can optionally send parameters to WSPayForm in order to additionaly customize WSPayForm UI or speed up buying process.

Some of the optional parameters can be changed by customer once he is on the WSPayForm. Therefore, it is not recommended to use any optional parameter as a reference in the identification process. Instead, ShoppingCartID should be used for order identification.

Lang
string
Lang value defines language that will be pre-selected as WSPayForm user interface language.

If parameter is not sent - language defined by WSPay will be used.

List of possible values can be found here.

CustomerFirstName
string
Customer first name.
WSPayForm will autofill corresponding input.

CustomerLastName
string
Customer last name.
WSPayForm will autofill corresponding input.

CustomerAddress
string
Customer street address.
WSPayForm will autofill corresponding input.

CustomerCity
string
Customer city.
WSPayForm will autofill corresponding input.

CustomerZIP
string
Customer postal code.
WSPayForm will autofill corresponding input.

CustomerCountry
string
Customer country represented in “ISO 3166-1 alpha-2” two letter country code.
WSPayForm will autofill corresponding input.

CustomerPhone
string
Customer phone number.
WSPayForm will autofill corresponding input.

CustomerEmail
string
Customer e-mail address.
WSPayForm will autofill corresponding input.

PaymentPlan
string
Value of PaymentPlan is a field that contains two subfields. Every subfield has two digits. First subfield represents number of payments, and second subfield represents the grace period.

Examples:
"0000" - no payment plan (installments are not allowed), only payment at once.
"0600" - payment through 6 installments and without grace period.
"0602" - payment through 6 installments, first installment postponed for 2 months.

If parameter is not sent - customer will be able to pay in installments only if the merchant has agreed installment payments with the bank, and if his credit card allows him to choose installments.
CreditCardName
string
Name of card brand that must be used for this transaction. Sending this parameter blocks choosing any other card brand at WSPayForm.

List of possible values can be found here.

PaymentMethod
string
Name of payment method that must be used for this transaction. Sending this parameter blocks choosing any other payment method at WSPayForm.

List of possible values can be found here.

IntAmount
string
IntAmount and IntCurrency parameters represent an informative amount in other converted currency. For example, if TotalAmount of 750,00 HRK is sent to WSPayForm; then IntAmount could be 100,00 and IntCurrency could be EUR which will result in an informative amount shown to customer as ~100,00 EUR.

IntCurrency
string
IntAmount and IntCurrency parameters represent an informative amount in other converted currency. For example, if TotalAmount of 750,00 HRK is sent to WSPayForm; then IntAmount could be 100,00 and IntCurrency could be EUR which will result in an informative amount shown to customer as ~100,00 EUR.

ReturnMethod
string
ReturnMethod parameter will tell WSPayForm which HTTP method will be used for redirecting customer to ReturnURL, ReturnErrorURL and CancelURL.
Possible values are GET or POST.

If this parameter is not sent - WSPayForm will use GET method.

If GET method is used WSPayForm will send transaction information through query parameters. If POST method is used, then transaction information will POST form to provided URL-s.

If merchant uses a WSPayForm size without customer input entry fields and does not send customer information data, then all data sent to further processing will be shops company data.

If merchant uses a WSPayForm size without customer input entry fields and sends customer information data, then merchant should check customer data before sending to WSPayForm as credit card processors may sometimes decline payment if customer information is in invalid format.

Rules for customer information data are given in the table below:

CustomerFirstName
  • Maximum length: 50 characters
  • No special characters allowed expect: -
CustomerLastName
  • Maximum length: 50 characters
  • No special characters allowed expect: -
CustomerAddress
  • Maximum length: 100 characters
  • No special characters allowed expect: -.,()
CustomerCity
  • Maximum length: 50 characters
  • No special characters allowed expect: -,
CustomerZIP
  • Maximum length: 20 characters
  • No special characters allowed expect: -
CustomerCountry
  • “ISO 3166-1 alpha-2” two letter country code should be used
CustomerPhone
  • Maximum length: 20 characters
  • Only numeric characters
CustomerEmail
  • Maximum length: 254 characters
  • Valid e-mail address

Redirecting customer to merchant

After successful, unsuccessful or cancelled transaction - WSPayForm depending on status of transaction redirects customer to URL defined by merchant.
HTTP method that will be used for redirecting customer to ReturnURL, ReturnErrorURL and CancelURL depends on optional ReturnMethod parameter.

List of parameters that WSPayForm returns to merchant is defined below.


ReturnURL

Customer will be redirected to ReturnURL after successful transaction.

ApprovalCode, Success and Signature represent three most important parameters for successful transaction process.
If the transaction was successful - ApprovalCode parameter will not be empty, Success will be 1 and returned signature will match the signature generated on merchant side.
ShoppingCartID Unique identification of transaction in merchants system.

WsPayOrderId Unique identification of transaction in WSPay system.

ApprovalCode Transaction approval code.

Success In case of successful transaction value of Success parameter will be 1.

Amount Amount charged to customer.

DateTime Date and time of transaction.
Date format: YYYYMMDDHHmmSS

PaymentType Name of credit card brand or payment type which customer used for this transaction.

List of possible values can be found here.

CreditCardNumber Masked credit card number used for this transaction.

PaymentPlan Number of installments and deferred payments chosen by customer.

Partner Processor which has processed the transaction.

List of possible values can be found here.

STAN Alphanumeric field that indicates the sequence of transaction.

ECI Electronic Commerce Indicator - result of 3D Secure authentication.

CustomerFirstName Customer first name.

CustomerSurname Customer last name.

CustomerAddress Customer street address.

CustomerCity Customer city.

CustomerZIP Customer postal code.

CustomerCountry Customer country.

CustomerPhone Customer phone number.

CustomerEmail Customer e-mail address.

Lang Language used on WSPayForm.

List of possible values can be found here.

ShopPostedPaymentPlan Original value of the PaymentPlan parameter if sent by the merchant.

ShopPostedLang Original value of the Lang parameter if sent by the merchant.

ShopPostedCreditCardName Original value of the CreditCardName parameter if sent by the merchant.

ShopPostedPaymentMethod Original value of the PaymentMethod parameter if sent by the merchant.

ErrorMessage In case of successful transaction value of ErrorMessage parameter will be empty.

Signature Represents a signature created from string formatted from following values in a following order using SHA512 algorithm:

ShopID
SecretKey
Success
SecretKey
ApprovalCode
SecretKey

Merchant must validate signature to make sure that request is originating from WSPayForm.

Signature generator, available at signature.wspay.info, can be used to test signature validity.



ReturnErrorURL

Customer will be redirected to ReturnErrorURL in case of communication error or when 3 unsuccessful payments on WSPayForm occures.

ShoppingCartID Unique identification of transaction in merchants system.

ApprovalCode Transaction approval code.
In case of unsuccessful transaction this parameter will be empty.

Success In case of unsuccessful transaction value of Success parameter will be 0.

Amount Amount that was planned to be charged to customer.

DateTime Date and time of transaction.
Date format: YYYYMMDDHHmmSS

PaymentType Name of credit card brand which customer used for this transaction.

List of possible values can be found here.

PaymentPlan Number of installments and deferred payments chosen by customer.

ECI Electronic Commerce Indicator - result of 3D Secure authentication .

CustomerFirstName Customer first name.

CustomerSurname Customer last name.

CustomerAddress Customer street address.

CustomerCity Customer city.

CustomerZIP Customer postal code.

CustomerCountry Customer country.

CustomerPhone Customer phone number.

CustomerEmail Customer e-mail address.

Lang Language used on WSPayForm.

List of possible values can be found here.

ShopPostedPaymentPlan Original value of the PaymentPlan parameter if sent by the merchant.

ShopPostedLang Original value of the Lang parameter if sent by the merchant.

ShopPostedCreditCardName Original value of the CreditCardName parameter if sent by the merchant.

ShopPostedPaymentMethod Original value of the PaymentMethod parameter if sent by the merchant.

ErrorMessage In case of unsuccessful transaction value of ErrorMessage parameter will be "ODBIJENO" or "DECLINED".

ErrorCodes ErrorCodes represent reasons why was customer redirected to ReturnErrorURL.

If multiple errors occur, then query parameters (if GET ReturnMethod is used) or key-value pairs (if POST ReturnMethod is used) will have multiple instances of ErrorCodes parameter.

List of possible values can be found here.

Signature Represents a signature created from string formatted from following values in a following order using SHA512 algorithm:

ShopID
SecretKey
ShoppingCartID
SecretKey
Success
SecretKey
ApprovalCode
SecretKey

Merchant must validate signature to make sure that request is originating from WSPayForm.

Signature generator, available at signature.wspay.info, can be used to test signature validity.



CancelURL

Customer will be redirected to CancelURL if he cancelles the transaction process or when form data entrance timeout happens.

ShoppingCartID Unique identification of transaction in merchants system.

ApprovalCode Transaction approval code.
In case of unsuccessful transaction this parameter will be empty.

Success In case of cancelled transaction value of Success parameter will be 0.

ResponseCode Code that represents reason why was customer redirected to CancelURL.

  • 15 - customer pressed cancel button
  • 16 - form data entry timeout happend
Signature Represents a signature created from string formatted from following values in a following order using SHA512 algorithm:

ShopID
SecretKey
ShoppingCartID
SecretKey
Success
SecretKey
ApprovalCode
SecretKey

Merchant must validate signature to make sure that request is originating from WSPayForm.

Signature generator, available at signature.wspay.info, can be used to test signature validity.

Tokenization

WSPayForm tokenization allows customers to save credit card information in order to have simpler checkout in the future.
Tokenized credit card is saved on merchants side where it can be used for faster checkouts or for charging customer credit card.

Getting token data

Tokenization is carried out by sending additional "IsTokenRequest" parameter along with the other WSPayForm parameters needed for redirecting customer to WSPayForm.

IsTokenRequest
string
This parameter will tell WSPayForm to tokenize credit card that will be used in transaction.

Parameter must have value: 1


After successful transaction, WSPayForm will redirect customer to ReturnURL with three additional parameters

Token Unique identifier that represents tokenized credit card.

TokenNumber Last 4 digits of the credit card.

TokenExp Credit card expiration date.
Format: YYMM

Payment using token

There are two possible ways to process payment using token after credit card has been tokenized:

  • WSPayForm payment using token
  • Direct payment using token

WSPay will provide additional ShopID that will be used for payment using token.



Who and when can use which method?

There are two main distinctions regarding payment with tokenized card: Customer Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT).

Customer Initiated Transactions are transactions where customer is the one who initiates transaction with saved card.
For example, customer chooses to pay with saved card in checkout process on merchants web shop.

Merchant Initiated Transactions are transaction where merchant submits a transaction with previously saved card without the customer participation.
For example, recurring payment, incremental payment or direct payment.


Transaction type Merchant in EEA Merchant outside EEA
CIT Must use
"WSPayForm payment using token"
May use any method
MIT Will use
"Direct payment using token"
Will use
"Direct payment using token"

We recommend using “WSPayForm payment using token” for all Customer Initiated Transactions since it provides more convenience for merchants in the means of chargeback.

Note that Maestro card requires 3D Secure authentication for every transaction so it cannot be processed using “Direct payment using token” method.



WSPayForm payment using token

WSPayForm payment using token is carried out by sending additional "Token" and "TokenNumber" parameters along with the other WSPayForm parameters needed for redirecting customer to WSPayForm.

Token
string
Unique identifier that represents tokenized credit card.
This parameter is received as a result of a previous tokenization process.

TokenNumber
string
Last 4 digits of the credit card.
This parameter is received as a result of a previous tokenization process.

Redirecting customer with these parameters will result in a WSPayForm where input fields for credit card number and expiration date will be filled and customer will have to enter CVV number.

After that, process is the same as with standard WSPayForm which means that customer will after successful, unsuccessful or cancelled transaction be redirected to URL defined by merchant.



Direct payment using token

In order to process direct payment using token - request object in JSON format must be sent using HTTP POST to endpoint that will be provided by WSPay.

Request:
{
    "Version": "2.0",
    "ShopID": "MYSHOPTOK",
    "ShoppingCartID": "78",
    "Token": "237038b3-761f-4bf7-a107-a18efa84dde0",
    "TokenNumber": "2152",
    "PaymentPlan": "0000",
    "TotalAmount": "1700",
    "DateTime": "20190722115807",
    "CustomerFirstName": "John",
    "CustomerLastName": "Doe",
    "CustomerAddress": "Address 10",
    "CustomerCity": "City",
    "CustomerZIP": "51000",
    "CustomerCountry": "HR",
    "CustomerPhone": "0911111111",
    "CustomerEmail": "john@doe.com",
    "Language": "HR",
    "Signature": "4a2b4246db90ed60eff677a60fd139f50e09c3e19d14a1503921c70780b912cf04fd44a7b3b6bd3376e4089891a2600aef5aade8979ec546a2ad2bac5d7f8daa"
}

Response:

{
    "WsPayOrderId": "dd9ec33a-0638-47d0-b17a-5de403ae3a3d",
    "ShoppingCartID": "78",
    "CustomerFirstName": "John",
    "CustomerLastName": "Doe",
    "CustomerAddress": "Address 10",
    "CustomerCity": "City",
    "CustomerZIP": "51000",
    "CustomerCountry": "HR",
    "CustomerPhone": "0911111111",
    "CustomerEmail": "john@doe.com",
    "ECI": null,
    "XID": null,
    "CAVV": null,
    "UCAF": null,
    "MaskedPan": "377500*******1234",
    "CreditCardName": "MVISA",
    "PaymentPlan": "0000",
    "ApprovalCode": "610990",
    "ErrorMessage": null,
    "Approved": "1",
    "TotalAmount": "1700",
    "STAN": "38419",
    "ActionSuccess": "1",
    "TransactionDateTime": "20181231233202",
    "Partner": "Pbz",
    "Signature": "4be89181861d5c9759a5032bbadfd4c4f07c0a90b4001155ddfbabb74512fdcb3927f9226c14d1235a9bcd9a6e4d7723289cb55d3bf2863f9519e32c28c7b3d9"
}

WSPayForm inside iframe

WSPayForm can be integrated inside HTML iframe element. This will allow merchants to include WSPayForm inside their website without the need of PCI DSS complience on their website.

Before loading WSPayForm URL inside iframe element merchant must send additional "Iframe" parameter along with other WSPayForm parameters needed for redirecting customer to WSPayForm.

Iframe
string
This parameter will tell WSPayForm that it is loaded inside HTML iframe element so it can act accordingly.

Parameter must have value: 1

IframeResponseTarget
string
This parameter will tell WSPayForm how customer will be redirected to ReturnURL, ReturnErrorURL and CancelURL.
Possible values are TOP or SELF.

If parameter is not sent - WSPayForm will use TOP.

If TOP is used, WSPayForm will redirect to ReturnURL, ReturnErrorURL or CancelURL in the full body of the window.

If SELF is used, WSPayForm will redirect to ReturnURL, ReturnErrorURL or CancelURL inside iframe that loaded WSPayForm.
It is important to note that some card processors may not allow FULL 3DS authentication inside iframe. When that is the case WSPayForm will use TOP as a value of IframeResponseTarget parameter.

WSPayForm is compatible with open-source library iFrame Resizer that enables the automatic resizing of iframe to fit their contained content.
In order for merchant to use this functionality they must include iframeResizer.min.js javascript file and call iFrameResize function.
For WSPayForm to work properly inside iframe, option checkOrigin needs to be set to false.

<iframe id="wspayform-iframe" style="width: 100%"></iframe>

<script>
    iFrameResize({ checkOrigin: false }, '#wspayform-iframe');
</script>

Error codes

Possible error codes in ReturnErrorURL:

  • E00001 - IPG code is not valid (internal error in the application).
  • E00002 - Application is unable to parse original request data because the data is missing or invalid.
  • E00003 - Payment form implementation version is missing.
  • E00004 - Transaction creation date and time is not set by the application (internal error in the application).
  • E00005 - Transaction previous status is not valid.
  • E00006 - Transaction new status is not valid.
  • E00007 - Transaction doesn't exist in the system.
  • E00008 - Shop ID is mandatory.
  • E00009 - Shop ID length is greater than maximum allowed (20 characters).
  • E00010 - Shopping cart ID is mandatory.
  • E00011 - Shopping cart ID length is greater than maximum allowed (255 characters).
  • E00012 - Successfully completed transaction, with the same shopping cart ID, already exists in the system.
  • E00013 - Total amount is mandatory
  • E00014 - Total amount must be greater than zero.
  • E00015 - Signature is mandatory.
  • E00016 - Signature is not valid.
  • E00017 - ReturnURL is mandatory.
  • E00018 - CancelURL is mandatory.
  • E00019 - ReturnErrorURL is mandatory.
  • E00020 - Language is not valid.
  • E00021 - Payment plan length is not valid.
  • E00022 - Payment plan contains non digits.
  • E00023 - Payment plan number of installments is not valid.
  • E00024 - Payment plan grace period is not valid.
  • E00025 - Recurring cycle type is not valid.
  • E00026 - Recurring cycle type is undefined, but other recurring values are present.
  • E00027 - Recurring cycle type and payment plan are mutually exclusive. You can't specify both at the same time.
  • E00028 - Recurring cycle type is not supported for the given credit card.
  • E00029 - Recurring interval is mandatory.
  • E00030 - Recurring interval must be greater than zero.
  • E00031 - Recurring number of payments is mandatory.
  • E00032 - Recurring number of payments must be greater than one.
  • E00033 - Shop doesn't support recurring payments.
  • E00034 - Shop configuration does not exist.
  • E00035 - Shop configuration is temporarily unavailable.
  • E00036 - Payment form session timeout is expired.
  • E00037 - Shop doesn't support payment with given payment method.
  • E00038 - Shop doesn't support payment with given credit card.
  • E00039 - Current transaction doesn't support payment with given credit card.
  • E00040 - Current transaction doesn't support payment with given payment method.
  • E00041 - Shop doesn't support payment with given payment plan/credit card combination.
  • E00042 - There are no applicable payment types for the current transaction.
  • E00043 - Tokenized credit card information doesn't exist.
  • E00044 - Credit card tokenization and payment with tokenized credit card are mutually exclusive.
  • E00045 - Payment with predefined credit card type and payment with tokenized credit card are mutually exclusive.
  • E00046 - Customer first name is mandatory.
  • E00047 - Customer first name length is greater than maximum allowed (50 characters).
  • E00048 - Customer last name is mandatory.
  • E00049 - Customer last name length is greater than maximum allowed (50 characters).
  • E00050 - Customer address is mandatory.
  • E00051 - Customer street address length is greater than maximum allowed (100 characters).
  • E00052 - Customer city is mandatory.
  • E00053 - Customer city length is greater than maximum allowed (50 characters).
  • E00054 - Customer zip code is mandatory.
  • E00055 - Customer zip code length is greater than maximum allowed (20 characters).
  • E00056 - Customer country is mandatory.
  • E00057 - Customer country length is greater than maximum allowed (60 characters).
  • E00058 - Customer phone is mandatory.
  • E00059 - Customer phone length is greater than maximum allowed (20 characters).
  • E00060 - Customer email is mandatory.
  • E00061 - Customer email address length is greater than maximum allowed (254 characters).
  • E00062 - Additional merchant data length is greater than maximum allowed (4000 characters).
  • E00063 - Credit card number is not valid.
  • E00064 - Credit card expiration date is not valid.
  • E00065 - Credit card verification data is not valid.
  • E00066 - There were some errors during credit card payment process. Please, try again.
  • E00067 - PayPal transaction setup failed.
  • E00068 - There were some errors during PayPal payment process. Please, try again.
  • E00069 - Unsuccessful payment.
  • E00070 - You've already reached maximum number of payment attempts.
  • E00071 - Successful payment is missing approval code.
  • E00072 - Successful payment is missing valid communication signature.
  • E00073 - Pay by link payment item doesn't exist.
  • E00074 - Pay by link payment item is temporarily unavailable.
  • E00075 - Pay by link payment item is expired.
  • E00076 - IPS transaction setup failed.
  • E00077 - IPS transaction status check is not possible, since it was not previously defined.
  • E00078 - IPS payment is not supported.
  • E00079 - Signature length is greater than maximum allowed (128 characters).
  • E00080 - ReturnURL length is greater than maximum allowed (500 characters).
  • E00081 - ReturnErrorURL length is greater than maximum allowed (500 characters).
  • E00082 - CancelURL length is greater than maximum allowed (500 characters).
  • E00083 - Aircash transaction setup failed.
  • E00084 - Aircash transaction status check is not possible, since it was not previously defined.
  • E00085 - Aircash payment is not supported.
  • E00086 - Iframe response target is not valid.
  • E00087 - Return success url is not valid.
  • E00088 - Return error url is not valid.
  • E00089 - Return cancel url is not valid.
  • E00090 - VALÚ transaction setup failed.
  • E00091 - VALÚ transaction status check is not possible, since it was not previously defined.
  • E00092 - VALÚ payment is not supported.
  • E00093 - Mobile device operating system is not valid.
  • E00094 - Mobile device callback interface name is mandatory.
  • E00095 - Mobile device callback interface name length is greater than maximum allowed (100 characters).
  • E00096 - KEKS Pay transaction setup failed.
  • E00097 - KEKS Pay transaction status check is not possible, since it was not previously defined.
  • E00098 - KEKS Pay payment is not supported.
  • E00099 - PayCek transaction setup failed.
  • E00100 - PayCek transaction status check is not possible, since it was not previously defined.
  • E00101 - PayCek payment is not supported.