(c) PCI Pal 2020. The content on this page is subject to the Disclaimer Section (found on the Introduction page)
Merchant e-Solutions Payment Gateway
This page details the inputs, secure inputs and outputs available for the Merchant e-Solutions Payment Gateway, how to complete each field, and an external link to the Merchant e-Solutions integration documentation.
PCI Pal must check any payment gateway integrations prior to going live. The documentation disclaimer (which applies throughout this guide) should be read before commencing any configuration of payment gateways.
Inputs
Input Fields
Required
Character Limits/Required Input
Description
transaction_type
Yes
D – Sale
P – Pre-Auth
U - Refund
T - Tokenization
The type of transaction
transaction_amount
Yes
12 num
Transaction amount
cardholder_street_address
19 char
First 19 characters of cardholder’s address for address verification service use
cardholder_zip
No
9 chars
Cardholder’s ZIP code for address verification use
invoice_number
Yes
17 char
Merchant-defined invoice number
tax_amount
No
12 char
Denotes the amount of tax for this transaction
moto_ecommerce_ind
Yes
Always 1
Indicates if this is a MOTO transaction
client_reference_number
No
96 char
Merchant-defined reference number
profile_id
Yes
20 num
ID issued by Merchant e-Solutions
profile_key
Yes
32 char
Key issued by Merchant e-Solutions
Secure Inputs
Inputs Fields
Required
Character Limits/Required Input
Description
card_number
Yes
19 char
Secure input of the card number
card_exp_date
Yes
4 char
Secure input of the card expiry - in the format MMYY
cvv2
Yes
3 or 4 char
Secure input of the card CVV, either three or four digits long depending on the card
Outputs
Output Fields
Description
transaction_idresp
Unique ID that confirms the transaction
error_code
3-character code summarizing the transaction response
auth_response_text
Text message describing transaction response
avs_result
Address verification response
cvv2_result
CVV2/CID verification response
auth_code
Returns the pre-paid card balance if offered by the card issuer
Further information can be found by viewing the integration documentation:
