(c) PCI Pal 2020. The content on this page is subject to the Disclaimer Section (found on the Introduction page)
MX Merchant Payment Gateway
This page details the inputs, secure inputs and outputs available for the MX Merchant Logic Item, how to complete each field, and an external link to the MX Merchant 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
merchantId
Yes
Unique to the merchant (string)
Id of the merchant
amount
Yes
Must not be 0. (float)
The payment amount.
tenderType
Yes
Values: Card, Check, Cash, Multiple, Loyalty, ACH (string)
The type of tender used for the transaction
cardAccount['avsStreet']
Yes (if tenderType = Card)
(string)
Billing Street Address (required if Loss Prevention Setting is turned on)
cardAccount['avsZip']
Yes (if tenderType = Card)
(string)
Billing Postal Code (required if Loss Prevention Setting is turned on)
cardAccount['alias']
No
(string)
Client provided, easy to remember name for the card
entryClass
No
(string)
Gets or sets the ACH entry class Values: CCD, PPD, TEL, WEB
cardPresent
No
(boolean)
Is the credit card is present at the time of payment?
authOnly
No
(boolean)
Indicates that this payment should NOT be added to current batch. AuthOnly payment won't be settled.
isAuth
No
(boolean)
Should this card be authorized?
isSettledFunds
No
(boolean)
Should this transaction be settled?
customerName
No
256 Char (string)
Customer Name (Does NOT associate payment to customer)
customerCode
No
(string)
Client provided customer reference number (Associates with Customer Number). Cannot be combined with invoiceId and clientReference if B2B is on