QUICK START FOR PAYMENT PAGE

1. Overview

The Payment Page solution is the quickest way to seamlessly integrate Roecny’s market-leading features, using an IFrame or a full page redirect.

This online solution allows you to:

Sell products and services over the web and increases conversion rates. This achieved by uniquely identifying each customer to maximize their user experience.
Process online customer deposits and withdrawals through our Cashier Deposit and Withdrawal pages. To enhance each customer’s user experience, these pages are presented in their preferred language, currency, and displays their previous payment methods.
Customize aspects of the UI on a per-request basis, for web and mobile pages, providing an easy-to-use interface for depositing and withdrawing funds.
Use the Roecny Gateway to securely process cards and a wide range of APMs and local deposit payment methods.

Apply your own finishing touches to your Payment Page integration by using the basic customizations provided in the Page Builder menu, located in the Control Panel.
Speak to your account manager regarding more complex customizations.

Example of the Payment Page

Payment Page is the quickest way to integrate with Roecny and enjoy the benefits of this feature-rich payment solution.

Simply loading Payment Page via an IFrame or a full page redirect is all it takes to seamlessly integrate Payment Page’s features and functionality into your site.

To use the Payment Page solution, create an HTTPS request with all the relevant transaction input encoded as a query string, and use it to redirect your customer to our page (or IFrame).

Follow the steps below to integrate and use Payment Page.

Payment Page can be customized using the Theme Builder in the Control Panel.

The Payment Page product should not be confused with the Simply Connect product (checkout() method), which is an entirely different solution.

2. Prepare the Transaction Input Parameters

The transaction input parameters string is a list of all the input parameters and their values in the exact order that they are sent in the request.

Prepare the input parameters:

Calculate a total_amount for the transaction. For details, see the Total Amount Calculation topic.

Create a transaction input parameters string containing the input parameters this format: [field1]=[value1]&[field]2=[value2]&[field3]=[value3]…
These are the minimum (required) input parameters needed to process a transaction:

There are many other input parameters that you can include.

Minimum (Required) Input Parameters

Parameter	Description
merchant_id	The vendor’s unique identification number provided by Roecny.
merchant_site_id	The vendor website’s unique identification number provided by Roecny.
total_amount	The total amount of the transaction.
currency	The three-letter ISO currency code for the currency used in the transaction.
user_token_id	This parameter is a unique identifier for each customer generated by the vendor.
item_name_N	The name of the item.
item_amount_N	The price of the item number.
item_quantity	The amount of items being purchased.
time_stamp	The GMT time that the transaction took place in the following format: YYYY-MM-DD.HH:MM:SS
version	The current version of the payment page. Currently, the version is=4.0.0
notify_url	URL to which the webhook notification is sent.
checksum	The calculated checksum value.

Example Transaction Input String

merchant_id=283475&merchant_site_id=89123755&total_amount=15&currency=USD&user_token_id=test@test.com&item_name_1=item1&item_amount_1=15&item_quantity_1=1&time_stamp=2011-01-05.06:04:26&version=4.0.0&notify_url=https://notify.merchant.com

3. Prepare the Authentication Request

Include a SHA-256 encrypted checksum in your HTTPS request to help Roecny authenticate the request and avoid communication errors.
Follow these steps to create the checksum:

Create a string of the values of all the input parameters (without spaces) in the exact order that they are sent in the request, as follows:
1. Copy the transaction input parameters string and delete everything except the values of all the input parameters (without spaces).
2. Concatenate the value of your secret key to the front of the string.
  For example, assuming a secret key value of: Secret123
```
Secret1232834758912375515USDtest@test.comitem11512011-01-05.06:04:264.0.0https://notify.merchant.com
```
Generate an encrypted checksum (based on the example string above) by running the string through a SHA-256 encryption function:
```
027402ea5d3e62179bfd82ec70eae2ad16efe7802880d452214d685169ce9300
```
Use the encrypted checksum value the checksum parameter in the request:
```
checksum=fedf7e2f70006c83fa740bfa121cdcac0932a672fc7e12a55621153cb52cddf9
```

4. Submit a Request to the Payment Page

Send an HTTPS request to the Payment Page either in the GET name/value pair format or as a POST.

Create an HTTPS query string by concatenating the endpoint URL of your payment page and the transaction input parameters string:

5. Handle the Response

After Roecny attempts to process the payment, your customer is redirected to a relevant Transaction Outcome page on your site, depending on the results:

Field	Description

Field	Description
Success	When Roecny processes the transaction successfully, your customer is redirected to your pre-defined *Success page*.
Pending	Roecny redirects your customer to your pre-defined *Pending page* until a response is received.
Back	When the customer presses Back on the payment page, Roecny redirects them to your pre-defined *Back page*.
DMN	The URL of your DMN listener.

Roecny also sends you a response via an HTTPS GET, which contains transaction details such as the outcome and customer payment details.

Four sets of parameters that are sent as part of the HTTPS GET:

Parameter Set	Description

Parameter Set	Description
Transaction	These parameters include the original parameters that you sent to the payment page and define the outcome of the transaction, including the response checksum.
Payment	These parameters include the unprotected payment method information, as provided by the customer on the payment page, such as name on card, expiration date, and the credit card number.
General	These parameters contain the details of the purchase including the item and amount.
Other	These parameters are any custom fields you defined and any other miscellaneous parameters.

6. Appendix – Calculations

Response Checksum Parameter

To ensure that the HTTPS GET from Roecny is authentic, an advanceResponsechecksum parameter is included in the HTTPS GET.

Calculate the SHA-256 or MD5 encoded checksum, of a string of the concatenated values, of the following parameters:

Although MD5 encryption is supported, SHA-256 is recommended.

merchantSecretKey
totalAmount
currency
responseTimeStamp
ppp_TransactionID
status
productId

Example Response Checksum

The concatenated string is made up of the values of the above parameters (assuming the secret key value is Secret123 and an item_quantity_1 (1):

Secret123115USD2007-11-13.13:22:343453459APPROVEDYourProduct

The calculated checksum would then be:

4cf3573877655c9b84ae8040beb586d9bc69d09d33ee4f4b451027579aa3f586

Total Amount Calculation

Calculate the transaction total amount as follows:

Calculate the transaction sub-total:
The transaction sub-total is the sum of all the item amounts, including their shipping, handling, discounts, etc.
Calculate the transaction sub-total in either of these ways:
- Calculate the per-item total for each item and then sum all the per-item totals to get a transaction sub-total.
- Calculate the entire transaction total to get a transaction sub-total.
Calculate the transaction tax:
The transaction tax is calculated as a percentage of the transaction sub-total.
Add the transaction tax to the transaction sub-total to get the transaction total amount.

The parameters that can be used in the calculation include:

Item level parameters:
- item_amount_N
- item_discount_N
- item_shipping_N
- item_handling_N
- item_quantity_N
shipping
handling
discount
total_tax (this is the tax percentage to be applied to the transaction)
version

Example of a Total Amount Calculation

Calculate the transaction total amount as follows:

Either:
- Calculate the per-item totals:
  Transaction sub-total = sum((item_amount_N – item_discount_N + item_shipping_N + item_handling_N) * item_quantity_N)
- Or calculate the entire transaction total:
  Transaction sub-total = item_amount_N + shipping + handling – discount
The tax is then added to calculate the total:
calculatedTotalAmount = transaction sub-total + transaction sub-total * (total_tax / 100)

Example of a Total Amount Calculation (with values)

Input values:

Item amount = 350
Shipping = 10
Discount = -20
Total tax = 23% (0.23)
Total amount = 418.20

Either:
- Calculate the per-item totals:
  Transaction sub-total = sum((item_amount_N – item_discount_N + item_shipping_N + item_handling_N) * item_quantity_N)
  340 = 350 + 10 – 20
- Or calculate the entire transaction total (which includes shipping & handling costs and discounts):
  Transaction sub-total = item_amount_N + shipping + handling – discount
  340 = 350 + 10 – 20
The tax is then added to calculate the total:
calculatedTotalAmount = transaction sub-total + transaction sub-total * (total_tax / 100)
418.20 = 340 + ( 0.23 * 340)

If the total amount has more than two digits after the decimal, you must round the amount to the nearest hundredth.

Output Parameters

Overview

When Roecny redirects your customers to a Success, Pending, or Error page, the URL of the page includes output parameters. These contain customer, transaction, and payment data, similar to Direct Merchant Notifications (DMNs).

The tables below provide a list of the parameters sent by Roecny back to the customer’s browser, upon completing the payment process.

Transaction Parameters

Parameter	Description
status	Status of the executed transaction: Approved, Declined, etc.
totalAmount	Total transaction charge.
transactionId	A 64-bit unique integer ID generated by Roecny, used for tracking purposes.
clientUniqueId	Custom data parameter. If this parameter is not specified, the default value is the name of the merchant’s account.
errCode	The error code of a failed transaction.
exErrCode	The extended error code of a failed transaction.
authCode	The authentication code received by Roecny for the transaction.
reason	The reason for a failed transaction, where relevant.
token	The token of the credit card that was returned by Roecny. This value represents the customer's credit card number stored on Roecny's database.
reasonCode	The failed transaction’s reason’s code.
responsechecksum	Deprecated output checksum parameter.
advanceResponseChecksum	Output checksum parameter.
cardCompany	The name of the credit card company. The possible values are: Visa, Amex, Mastercard, Diners, Diners, Discover, JCB, LaserCard, Maestro, Solo, and Switch.
eci	An Electronic Commerce Indicator (ECI) value is the result of a 3DS authentication request, returned by a Directory Server ("issuer ACS") (namely Visa, Mastercard, JCB, and American Express). Possible ECI values: Visa: 5 – The cardholder was successfully authenticated. 6 – The issuer or cardholder does not participate in a 3D-Secure program. 7 – Payment authentication was not performed. Mastercard: 1 – The issuer or cardholder does not participate in a 3D-Secure program. 2 – The cardholder was successfully authenticated. 6 – Payment authentication was not performed. 7 – The cardholder was successfully authenticated for the initial MIT.

Payment Parameters

Parameter	Description

Parameter	Description
nameOnCard	The name on the credit card.
first_name*	The customer's first name.
last_name*	The customer's last name.
address1*	The address of the customer.
city*	The city of the customer.
country*	The country of the customer.
email*	The email address of the customer.
zip*	The ZIP code of the customer when available.
phone1*	The phone number of the customer.
currency	The currency used in the transaction.

* This parameter should be read from the DMN callback.

General Items

Parameter	Description

Parameter	Description
total_discount	Total discount for current order.
total_handling	Total handling for current order.
total_shipping	Total shipping for current order.
total_tax	Total tax for current order.
item_number_N	The number of item number N.
item_amount_N	The cost of item number N.
item_quantity_N	The quantity of item number N.
item_discount_N	The discount for item number N.
item_handling_N	The handling costs for item number N.
item_shipping_N	The shipping costs for item number N.
promoCode	This value is a promotional code you define that you can use to apply discounts to your products or services.

Other Parameters

Parameter	Description
customData	Custom data sent to Roecny.
merchant_unique_id	The `merchant_unique_id` value as provided by the merchant to Roecny in the HTTPS request.
merchant_site_id	The unique ID (identifier) of the Transaction in the merchant’s database as provided by the merchant to the PPP in the HTTPS request.
merchant_id	The unique merchant ID supplied by Roecny.
requestVersion	The processed Roecny request’s version.
message	A message sent from Roecny regarding the transaction.
error	An error message sent from Roecny.
instantDmnStatus	The status of the Instant DMN. This parameter is only returned when Instant DMNs are active.
ppp_TransactionId	The ID number of the transaction’s history table in the Roecny database.
userId	The UserId value transferred by the merchant in the HTTPS request.
ProductId	The purchased product’s ID as provided by the merchant in the HTTPS request.
ppp_status	The status of the transaction. OK indicates that the transaction was approved. PENDING occurs only for APM transactions in which the final status is not immediately returned. FAIL indicates that the transaction was declined or there was an error.
merchantLocale	The language and country of the user in ISO code in the following format: [language ISO]_[country ISO] For example: en_US
unknownParameters	All unknown parameters sent with the current transaction.
webMasterId	Affiliate parameter (an additional parameter that the merchant can send to PPP).
customFieldn*	The merchant can send up to 15 custom fields to Roecny to update miscellaneous data.

Input Parameters

Overview

This topic describes all the parameters that can be sent to the Cashier Deposit page via an HTTP request.

Basic Parameters

Mandatory column values:

All: Mandatory for all transaction types (every request).
No: The parameter is not mandatory.

To improve risk analysis and to ensure successful 3DS authentication, it is recommended to collect and submit as many parameters as possible, in addition to the mandatory risk fields.

Parameter	Type	Size	Mandatory	Description
merchant_id	Integer	64bits	All	The merchant’s ID provided by Roecny.
merchant_site_id	Integer	64bits	All	The merchant website’s ID provided by Roecny.
checksum	String	Char(102400)	All	A hashing of the request to secure and authenticate the request.
time_stamp	String	Char(19)	All	Current GMT time in the following format: YYY-MM-DD.HH:MM:SS.
currency	String	Char(3)	All	The currency used in the transaction.
invoice_id	String	Char(100)	No	A unique invoice identifier provided by the merchant or randomly generated.
payment_method	String	Char(256)	No	The type of payment method selected by the customer. Values: Credit Card: cc_card.
payment_method_mode	-	-	-	Value: filter This parameter filters out any payment method that is not the payment method sent in `payment_method`.
payment_methods	String	Char(256)	No	The types of payment methods selected by the customer (comma separated). For example: cc_card, ppp_GooglePay, ppp_ApplePay Values: Credit Card: cc_card.
merchantLocale	String	Char(5)	No	The language and country of the user in ISO code in the following format: [language ISO]_[country ISO] Unless specified, the default is English. The possible values of this parameter is provided below: English (US): en_US English (UK): en_UK German: de_DE Chinese: (PRC) zh_CN Hebrew: iw_IL French: fr_FR Dutch (Standard): nl_NL Indonesia: in_ID Italian: it_IT Japanese: ja_JP Korean: ko_KR Lithuanian: lt_LT Spanish: es_ES English (Canada): en_CA English (Australia): en_AU Russian: ru_RU Arabic: ar_AA Portuguese: pt_BR Swedish: sv_SE Turkish: tr_TR Slovenian: sl_SI Danish: da_DK Romanian: ro_RO Bulgarian: bg_BG Polish: pl_PL Hungarian: hu_HU Vietnamese: vi_VL
userid	String	Char(50)	No	The customer’s ID as per the merchant’s user ID.
theme_id	Integer	64bits	No	Use this field overrides
customData	String	Char(255)	No	General data about the customer provided by the merchant.
merchant_unique_id	String	Char(64)	No	The unique ID (identifier) of the transaction in the merchant’s database.
encoding	String	Char (20)	No*	The type of character encoding. Default value is ISO-8859-1. * If encoding=UTF-8, then this fields is mandatory.
webMasterId	String	Char(255)	No	This is an affiliate parameter that the merchant can send to Cashier.
allow_installments	Integer	64 bits	No	Indicates whether payment may be made in installments or not, if this feature is supported by the merchant. The possible value of this parameter is either ‘1’ (yes) or ‘0’ (no).
max_num_installments	Integer	64 bits	No	Indicates the maximum amount of installments with which the payment can be made.
processingChannel	String	Char (4)	No	Sends “MOTO” value whenever the processing channel is from MOTO type (mail or telephone order)
planId	Integer	64 bits	No	Subscription Plan ID
showMessageKeys	String	Char(5)	No	Values: True: Present the message keys in brackets. False: Do not present the message keys in brackets.
withdrawableBalance	Double	64 bits	No	The maximum amount that the merchant allows the user to withdraw on a specific transaction. Currently, this feature is not supported for currency conversion transactions. Applies only to withdraw.
current_balance	Double	64 bits	No	The Customer's account balance. Relevant only for deposit. Currently, this feature is not supported for currency conversion transactions.

Item Details

“N” represents the item count number. The first item is item_name_1 up to item_name_n.

Parameter	Type	Size	Mandatory	Description

Parameter	Type	Size	Mandatory	Description
item_name_N	String	Char(400)	Yes	The name of item number N. Currently, item names can only include ISO-8859-1 character set encoding.
item_number_N	String	Char(400)	No	The first part of the items list, the serial number. Counted from item_number_1 to item_number_N.
item_amount_N	Double	64 bits	Yes	The cost of the item numbered in the item_number_N parameter.
item_shipping_N	Double	64 bits	No	Shipping costs of the item numbered in the item_number_N parameter.
item_shipping_tax_N	Double	64 bits	No	The tax rate (percentage) of the item's shipping fee. Values: 1–100
item_handling_N	Double	64 bits	No	Handling costs of the item numbered in the item_number_N parameter.
item_discount_N	Double	64 bits	No	Discount amount of the item numbered in the item_number_N parameter.
item_quantity_N	Integer	64 bits	Yes	Number of pieces of the item numbered in the item_number_N parameter. Default value is 1.
item_open_amount_1	String	Char(5)	No	True: Allows the customer to change the default deposit amount. False (default): The customer cannot change the default amount.
item_min_amount_1	Double	64 bits	Conditional	The minimum amount that the customer can deposit. The format is a maximum of 7 digits before the decimal and 2 digits after. Mandatory if `item_open_amount_1=True`.
item_max_amount_1	Double	64 bits	Conditional	The maximum amount that the customer can deposit. The format is a maximum of 7 digits before the decimal and 2 digits after. Mandatory if `item_open_amount_1=True`.
item_tax_N	Double	64 bits	No	Item's tax rate. Values: 1–100 Default value: 0
item_tax_included_N	Integer	64 bits	No	Values: 1: Item amount includes the tax. 0: Item amount does not include the tax.
numberofitems	Double	64 bits	Conditional	Number of items to process. Default is 1. Mandatory if `numberofitems` is greater than 1.
discount	Double	64 bits	No	Additional discount amount, regardless of any discount(s) for the transaction.
shipping	Double	64 bits	No	Total shipping costs.
handling	Double	64 bits	No	Total handling costs.
total_amount	Double	64 bits	Yes	Total transaction charge.
total_tax	Double	64 bits	No	The VAT percentage to be applied to the transaction.
shipping_tax	Double	64 bits	No	The tax rate (percentage) of the cart's shipping fee. Values: 1–101
productId	String	Char(50)	No	Merchant’s product ID. If this parameter is left empty, Cashier inserts a concatenation of all item names.
promoCode	String	Char(512)	No	This value is a promotional code you define that you can use to apply discounts to your products or services. To activate this field, contact Roecny Technical Support.
nettelerAccount	String		Neteller	The customer's Neteller account number.
nettelerSecureId	String		Neteller	The customer's Neteller SecureId.
qiwi_phonenumber	String		Qiwi	The customer's phone number registered with Qiwi.
suggestedAmount1	String	64 bits	No	Pre-defined amount button that is presented on the Payment Page. `item_open_amount_1` must be True to support this field.
suggestedAmount2	String	65 bits	No	Pre-defined amount button that is presented on the Payment Page. `item_open_amount_1` must be True to support this field.
suggestedAmount3	String	66 bits	No	Pre-defined amount button that is presented on the Payment Page. `item_open_amount_1` must be True to support this field.
airline_BoardingFee	Double	64 bits	No	Paid by airlines for the use of airport facilities.
consumption_tax_amount	Double	64 bits	No	Tax on the purchase of goods or services.
tax_amount_base	Double	64 bits	No	Taxable amount as determined by the tax authority.
tip_amount	Double	64 bits	No	A sum of money customarily given by a customer in addition to the basic price of the service.

User Token

Parameter	Type	Size	Mandatory	Description

Parameter	Type	Size	Mandatory	Description
user_token	String	Char (8)	No	This parameter determines if the payment page requires existing customers to register for each transaction. register – Always register, even if registered already auto – Register only new users readonly – Cannot register new payment option, only use existing one. registeronly – Always register. Does not show existing payment options previously added by the user readonlyupo – User can select only existing specific UPO specified in userPaymentOptionId
user_token_id	String	Char (255)	Yes	ID for the user, based on which we manage the user’s payment methods.
userPaymentOptionId	String		No	This ID specifies the user payment option to use for the transaction when user_token = readonlyupo

Customer Details

Parameter	Type	Mandatory	Description
first_name	String(30)	No	Customer’s first name.
last_name	String(40)	No	Customer’s last name.
title	String(20)	No	Free text field for an honorific title before the customer's name. For example: Mr., Mrs.
email	String(100)	Yes	Customer’s email address.
address1	String(60)	No	Customer’s address.
address2	String(60)	No	Customer’s address.
city	String(30)	No	Customer’s city.
country	String(20)	Yes	Customer’s 2-letter ISO country code.
state	String(20)	No	Customer’s ISO county/province/state/territory/union territory code.
zip	String(10)	No	Customer’s ZIP code.
phone1	String(18)	Conditional	Customer’s phone1. Note: REQUIRED for 3DS Card Authentication only if `email` not provided.
phone2	String(18)	No	Customer’s phone2.
phone3	String(18)	No	Customer’s phone3.
personal_id	String(13)	No	The customer’s ID number issued by their respective country.
dateOfBirth	String(10)	No	The date of birth of the registering user. (YYYY-MM-DD)

3D-Secure v2

The Roecny payment page handles the SCA 3D-Secure v2 process for the merchant. The merchant only needs to add parameters to the call for the web cashier URL to assist in completing the SCA process.
To learn more about 3D-Secure v2, see the 3D-Secure Explained topic.

Even though most of the parameters below are optional, it is highly recommended to pass as many details as possible in the call to increase the chances of a frictionless authentication rather than invoking a challenge of the end user.

The following table displays the parameters that need to be added to fully support the 3D-Secure v2 process.

Parameter	Type	Mandatory	Description

Parameter	Type	Mandatory	Description
deliveryEmail	String (254)	No	For electronic delivery, the email address to which the merchandise is delivered. deliveryEmail@somedomain.com
deliveryTimeFrame	String (2)	No	This parameter indicates the merchandise delivery time frame. 01 = Electronic delivery 02 = Same day shipping 03 = Overnight shipping 04 = Two-day or more shipping
giftCardAmount	String (15)	No	For prepaid or gift card purchase, this represents the purchase amount total of prepaid or gift card(s) in major units (for example, USD 123.45 is 123).
giftCardCount	String (2)	No	For prepaid or gift card purchase, this represents the total count of individual prepaid or gift cards/codes purchased.
giftCardCurrency	String (3)	No
preOrderDate	String (8)	No	For a pre-ordered purchase, this represents the expected date that the merchandise is available. Format: YYYMMDD
preOrderInd	String (2)	No	This indicates whether the cardholder is placing an order for merchandise with a future availability or release date. 01 = Merchandise available 02 = Future availability
reorderItemsInd	String (2)	No	This indicates whether the cardholder is reordering previously purchased merchandise. 01 = First time ordered 02 = Reordered
shipIndicator	String (2)	No	Indicates shipping method chosen for the transaction. Merchants must choose the Shipping Indicator code that most accurately describes the cardholder’s specific transaction, not their general business. If one or more items are included in the sale, use the Shipping Indicator code for the physical goods, or if all digital goods, use the Shipping Indicator code that describes the most expensive item. 01 = Ship to cardholder’s billing address 02 = Ship to another verified address on file with merchant 03 = Ship to address that is different than the cardholder’s billing address 04 = “Ship to Store” / Pickup at local store (store address shall be populated in shipping address fields) 05 = Digital goods (includes online services, electronic gift cards and redemption codes) 06 = Travel and Event tickets, not shipped 07 = Other (for example, gaming, digital services not shipped, e-media subscriptions, etc.)
threeDSChallengeWindowSize	String (2)	No	Challenge Window Size 01 = 250 x 400 02 = 390 x 400 03 = 500 x 600 04 = 600 x 400 05 = Full screen Note: If no value is sent, the default value is 03.
accountAge	String (2)	No	Length of time that the cardholder has had the account with the 3DS Requestor. 01 = No account (guest checkout) 02 = Created during this transaction 03 = Less than 30 days 04 = 30–60 days 05 = More than 60 days
accountLastChangeDate	String (8)	No	Date that the cardholder’s account with the 3DS Requestor was last changed, including Billing or Shipping address, new payment account, or new user(s) added. Format: YYYMMDD
accountLastChangeInd	String (2)	No	Length of time since the cardholder’s account information with the 3DS Requestor was last changed, including Billing or Shipping address, new payment account, or new user(s) added. 01 = Changed during this transaction 02 = Less than 30 days 03 = 30–60 days 04 = More than 60 days
accountRegistrationDate	String (8)	No	Date that the cardholder opened the account with the 3DS Requestor. Format: YYYMMDD
accountPasswordChangeDate	String (8)	No	Date that cardholder’s account with the 3DS Requestor had a password change or account reset. Format: YYYMMDD
accountResetInd	String	No	Indicates the length of time since the cardholder’s account with the 3DS Requestor had a password change or account reset. 01 = No change 02 = Changed during this transaction 03 = Less than 30 days 04 = 30–60 days 05 = More than 60 days
accountPurchasesCount6M	String (4)	No	Number of purchases with this cardholder account during the previous six months.
accountAddCardAttempts24H	String (3)	No	Number of Add Card attempts in the last 24 hours.
accountTransactionsCount24H	String (3)	No	Number of transactions (successful and abandoned) for this cardholder account with the 3DS Requestor across all payment accounts in the previous 24 hours.
accountTransactionsCount1Y	String (3)	No	Number of transactions (successful and abandoned) for this cardholder account with the 3DS Requestor across all payment accounts in the previous year.
accountAddressFirstUseDate	String (8)	No	Date when the shipping address used for this transaction was first used with the 3DS Requestor. Format: YYYMMDD
accountAddressFirstUseInd	String (2)	No	Indicates when the shipping address used for this transaction was first used with the 3DS Requestor. 01 = This transaction 02 = Less than 30 days 03 = 30–60 days 04 = More than 60 days
accountNameInd	String (2)	No	Indicates if the Cardholder Name on the account is identical to the shipping Name used for this transaction. 01 = Account Name identical to shipping Name 02 = Account Name different than shipping Name
accountSuspiciousActivityInd	String (2)	No	Indicates whether the 3DS Requestor has experienced suspicious activity (including previous fraud) on the cardholder account. 01 = No suspicious activity has been observed 02 = Suspicious activity has been observed

Shipping Details

The following details are required whenever product shipping is involved.

Parameter	Type	Size	Mandatory	Description

Parameter	Type	Size	Mandatory	Description
shippingFirstName	String	30	No	Recipient’s first name.
shippingLastName	String	40	No	Recipient’s last name.
shippingAddress	String	60	No	Recipient’s address.
shippingCity	String	30	No	Recipient’s city.
shippingCountry	String	20	No	Recipient’s country in an ISO code
shippingZip	String	10	No	Recipient’s ZIP code.
shippingCompanyName	String	255	No	Name of the company, in case the goods are sent to a company.
shippingState	String	2	No	Customer’s shipping ISO county/province/state/territory/union territory code.
shippingStreetNumber	String	20	No	Number of the customer's house.

Parameter	Type	Size	Mandatory	Description
skip_review_tab	String	Char(5)	No	A switch (true/false) indicating whether or not to skip the Cashier’s review page.
skip_billing_tab	String	Char(5)	No	When set to True, the payment page is skipped and instead the customer is redirected to the the payment method's page, but only if a redirect payment method was provided in `payment_method`) Note: To redirect the customer to the payment method's page, the merchant must provide all data that is required by the payment method.
success_url	String	Char (2048)	No	The customer is redirected to this URL on successful transaction.
error_url	String	Char (2048)	No	The customer is redirected to this URL on error.
pending_url	String	Char (2048)	No	The customer is redirected to this URL when response is pending.
back_url	String	Char (2048)	No	The customer is redirected to this URL when user presses the ‘Back’ button.
notify_url	String	Char (2048)	No	The DMN URL.
isNative	Boolean	1	No	Possible values: 1 = Opens the redirect APM in the same window (IFrame). 0 = Opens a redirect-based APM in a new window.
quick_deposit	Boolean	1	No	For more information, please contact Roecny’s Integration Team.

If some of the payment page’s mandatory parameters are missing, the customer’s browser is redirected to the error page URL.

Merchant Custom Fields

Parameter	Type	Size	Mandatory	Description
descriptorMerchantName	String	Char(25)	No	Allows the merchant to define a dynamic descriptor for the merchant’s name.
descriptorMerchantPhone	String	Char(13)	No	Allows the merchant to define a dynamic descriptor for the merchant’s phone number.
customSiteName	String	Char(50)	No	The merchant’s site name that should replace the default MerchantSite name. This parameter is useful for merchants operating many websites that are distinguished only by name.
customField1 customField2 customField3 ... customField15	String	Char(64)	No	Custom fields for the merchant to update miscellaneous data. This is sent to the Cashier in the HTTP request and returned in its response.

QUICK START FOR PAYMENT PAGE

1. Overview

Example of the Payment Page

2. Prepare the Transaction Input Parameters

Minimum (Required) Input Parameters

Example Transaction Input String

3. Prepare the Authentication Request

4. Submit a Request to the Payment Page

5. Handle the Response

6. Appendix – Calculations

Response Checksum Parameter

Example Response Checksum

Total Amount Calculation

Example of a Total Amount Calculation

Example of a Total Amount Calculation (with values)

Output Parameters

Overview

Transaction Parameters

Payment Parameters

General Items

Other Parameters

Input Parameters

Overview

Basic Parameters

Item Details

User Token

Customer Details

3D-Secure v2

Shipping Details

Navigation Parameters

Merchant Custom Fields