Variables - names, lengths and formats
Here are the definitions of variables which are submitted to WebPay form:
Buyer's profile
name | length (min - max) |
format | additional info | mandatory? | required by |
---|---|---|---|---|---|
ch_full_name |
3-30 | alphanumeric | buyer's full name | Strongly recommended * | 3DS check |
ch_address |
3-100 | alphanumeric | buyer's address | Strongly recommended * | 3DS check |
ch_city |
3-30 | alphanumeric | buyer's city | Strongly recommended * | 3DS check |
ch_zip |
3-9 | alphanumeric | buyer's zip | Strongly recommended * | 3DS check |
ch_country |
2-3 | alphanumeric | buyer’s country in alpha2, alpha3 letter code or 3 digit ISO numeric code | yes | 3DS check |
ch_phone |
3-30 | alphanumeric | buyer's phone | Strongly recommended * | 3DS check |
ch_email |
3-100 | alphanumeric | buyer's email | Strongly recommended * | 3DS check |
customer_uuid |
20 | alphanumeric | An id of a customer. Check documentation how to create a customer. | no | Monri system |
Order details
name | length | format | additional info | mandatory? | required by |
---|---|---|---|---|---|
order_info |
3-100 | alphanumeric | short description of order being processed | yes | Monri system |
order_number |
1-40 | alphanumeric | unique identifier | yes | Monri system |
amount |
3-11 | integer | amount is in minor units, ie. 10,24 EUR is sent as 1024 | yes | all ** |
currency |
predefined | alpha | some possible values are: EUR, BAM, RSD, MKD, RON and USD Complete list find here LINK |
yes | all ** |
Processing data
name | length | format | additional info | mandatory? | required by |
---|---|---|---|---|---|
language |
predefined | alpha-2 | used for error localization, possible values are en, es, ba or hr | yes | Monri system |
transaction_type |
predefined | alpha | possible values are authorize, purchase, capture, refund, void | yes | all ** |
authenticity_token |
40 | alphanumeric | auto generated value for merchant account, can be found under merchant settings | yes | Monri system |
digest |
40 | alphanumeric | SHA512 hash generated from concatenation of key, order_number, amount and currency as strings; key can be found under merchant settings | yes | Monri system |
number_of_installments |
1-2 | integer | range 2-36 | no | Acquiring bank |
installments_disabled |
predefined | boolean | possible value is true or false; missing parameter is equivalent to false. If set to true - installments selection is disabled | no | Monri system |
moto |
predefined | boolean | possible value is true or false; missing parameter in request is equivalent to false | no | all ** |
Additional info
Note: The parameters listed in this section are optional and relate to additional features provided by the Monri Online system.
name | length | format | additional info |
---|---|---|---|
tokenize_pan_offered |
predefined | boolean | if true and merchant has secure vault active (tokenization enabled) then save card for future payments will be shown to customer. If customer decided to save the card and transaction is approved we’ll provide pan_token which you can store on your side. |
supported_payment_methods |
predefined | comma separated payment methods | provide this value if customer decides to pay with previously saved card(s) or with new card. If this value is provided and valid (card not expired, token valid etc) then only cvv input will be shown on the payment form. All other information (masked pan, expiry date etc) will be pre filled. Multiple tokens can be sent (separated by comma). In that case, the user will have an option which payment method to use. |
tokenize_pan |
predefined | boolean | tokenize pan without prompting the user |
tokenize_brands |
predefined | comma separated list of card brands | provide this value if you want to limit card tokenization to card brand(s). Multiple brands can be sent (separated by comma). Refer to tokenize brands section below. |
supported_cc_issuers |
predefined | comma separated card issuers | provide this value if you want to limit payment to the card to certain issuer(s) *** |
rules |
predefined | comma separated rules | provide this value if you want to apply custom rules |
force_installments |
predefined | boolean | provide this value if you want to force payment on installments. For more details refer to the force_installments documentation |
custom_attributes |
predefined | valid JSON string | provide this value if you want to customize form behaviour. Refer to the custom attributes section below for more details. |
success_url_override |
predefined | valid HTTPS URL | provide this value if you want to override success URL |
cancel_url_override |
predefined | valid HTTPS URL | provide this value if you want to override cancel URL |
callback_url_override |
predefined | valid HTTPS URL | provide this value if you want to override callback URL |
Footnote
* Strongly recommended: While submitting this data is mandatory, the accuracy and completeness of the information are not strictly enforced. However, we strongly recommend providing accurate and detailed information beyond the minimum requirements.
Inaccurate or incomplete data may result in transaction declines by the issuing bank due to impaired risk assessment, fraud detection, or failed 3D Secure (3DS) authentication.
** All: This indicates a mandatory parameter for all stakeholders involved in the authorization and authentication process. These stakeholders include: Monri (as the IPSP), the Acquiring bank, the Issuing bank, and Directory Servers.
*** For a list of Monri-supported issuers, please contact helpdesk@monri.com.