Variables - names, lengths and formats

Here are the definitions of variables which are submitted to WebPay form:

Buyer's profile

name	length	format	additional info
ch_full_name	3-30	alphanumeric	buyer's full name
ch_address	3-100	alphanumeric	buyer's address
ch_city	3-30	alphanumeric	buyer's city
ch_zip	3-9	alphanumeric	buyer's zip
ch_country	2-3	alphanumeric	buyer’s country in alpha2, alpha3 letter code or 3 digit ISO numeric code
ch_phone	3-30	alphanumeric	buyer's phone
ch_email	3-100	alphanumeric	buyer's email
customer_uuid	20	alphanumeric	An id of a customer. Check documentation how to create a customer.

Order details

name	length	format	additional info
order_info	3-100	alphanumeric	short description of order being processed
order_number	1-40	alphanumeric	unique identifier
amount	3-11	integer	amount is in minor units, ie. 10.24 USD is sent as 1024
currency	predefined	alpha	possible values are USD, EUR or BAM

Processing data

name	length	format	additional info
language	predefined	alpha	used for errors localization, possible values are en, es, ba or hr
transaction_type	predefined	alpha	possible values are authorize, purchase, capture, refund, void
authenticity_token	40	alphanumeric	auto generated value for merchant account, can be found under merchant settings
digest	40	alphanumeric	SHA512 hash generated from concatenation of key, order_number, amount and currency as strings; key can be found under merchant settings
number_of_installments	1-2	integer	range 2-12
installments_disabled	predefined	boolean	possible value is true or false; missing variable is equivalent to false. If set to true - installments selection is disabled
moto	predefined	boolean	possible value is true or false; missing variable is equivalent to false

Additional info

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