| merchantID |
Your 7 digits merchant number - ####### |
7 |
Yes |
trans_amount
|
Amount to be charge
(example: 199.95)
|
20 |
Yes |
trans_currency
|
Supported Currencies can be found Here, in Server to Server mode you must send the Currency ID.
|
3 |
Yes |
| trans_type |
0 = Debit Transaction (Default when field is empty)
|
1 |
Yes |
| trans_installments |
Number of installments, 1 for regular transaction
|
2 |
Yes |
| trans_refNum |
Unique text used to defer one transaction from another |
100 |
Optional |
| trans_comment |
Optional text used mainly to describe the transaction |
255 |
Optional |
| trans_storePm |
Send value of 1 to save the payment method for future use if the transaction success |
1 |
Optional |
| disp_payFor |
Text shown to buyer in payment window, Usually description of purchase (Cart description, Product name) |
40 |
Optional |
| disp_paymentType |
List of payment types that are available to the client.
Available values are can be found Here.
Please use the abbreviation field from the list.
If more than one, use comma to separate the values.
(example: CC,ED)
|
80 |
Optional |
| disp_lng |
The default language for the UI text in the window.
If omitted, language is taken from user's browser settings.
Available values are:
he-IL = עברית (ישראל)
en-US = English (United States)
fr-FR = français (France)
es-ES = español (España, alfabetización internacional)
lt-LT= lietuvių (Lietuva)
ru-RU = русский (Россия)
de-DE = Deutsch (Deutschland)
zh = 中文
|
5 |
Optional |
| disp_lngList |
Specifies the language(s) available to user in the Language Selector in the window.
Available values are:
all = all languages are available (default if the field is empty or omitted)
hide = the language selector is hidden
comma-separated list of codes for enabling specific language(s).
For example, disp_lngList=en-us,it-it
will allow user to switch between English and Italian, and disp_lngList=en-us will show English only.
The available languages are listed in the disp_lng field description.
|
5 |
Optional |
| disp_recurring |
Specifies the deviations from the standard display of the recurring charges.
Available values are:
0 = standard display (default if the field is empty or omitted)
1 = hide the number of charges in the last stage of the recurring series
|
3 |
Optional |
notification_url
|
The URL for notifying your system with the transaction result.
Must include http:// or https://.
|
255 |
Optional |
url_redirect
|
The URL to which the buyer’s browser is redirected to after completing the payment
Must include http:// or https://.
|
255 |
Optional |
| PLID |
Platform user ID - A unique identifier for the user on the platform |
100 |
Optional |
| client_fullName
|
Cardholder full name |
50 |
Optional |
| client_email
|
Cardholder Email address |
50 |
Optional |
| client_phoneNum
|
Cardholder phone number |
15 |
Optional |
| client_idNum
|
Government issued ID number |
9 |
Optional |
|
| client_billAddress1
|
Client billing address line 1 |
50 |
Optional |
| client_billAddress2
|
Client billing address line 2 |
50 |
Optional |
| client_billCity
|
Client billing city |
20 |
Optional |
| client_billZipcode
|
Client billing zip code |
20 |
Optional |
| client_billState |
Client billing state in 2 char ISO code |
2 |
Optional |
| client_billCountry |
Client billing country in 2 char ISO code |
2 |
Optional |
| OPCountry |
Client billing country in 2 char ISO code - this will preselect the bank country on the payment page |
2 |
Optional |
| terms_url |
Send the link to your terms and conditions and it will be presented to the payer during the transaction |
100 |
Optional |
| show_edit |
Sending "false" will hide the Edit button and the payer wont be able to able the personal details that were sent as part of the transaction |
10 |
Optional |
| show_marketing |
Sending "false" will hide the Marketing concent button and the payer wont see the marketing concent text |
10 |
Optional |
| signature |
Signature for verifying the authenticity of the request parameters.
Field values to use: All parameters in the order they appear in the request, first GET then POST + PersonalHashKey.
more information can be found at the Signature section in this page
|
30 |
Yes |