×
Menu

Paymetric: XI Pay

 
This page details the inputs, secure inputs and outputs available for the Paymetric: XI Pay Logic Item, how to complete each field, and an external link to the 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 payment gateway configuration.
 

Inputs

Input Fields
Required
Character Limits/
Required Input
Description
XIID
Yes
Unique per client
Unique merchant code given by Paymetric to the client
UserName
Yes
Unique per client
Unique account username
Password
Yes
Unique per client
Unique account password
PacketOperation
Yes
2 nums
Defines whether or not the transaction will be authorisation or  capture. The following values are valid:
1 - Authorisation
17 - Capture
HD_ORDER_DESCR1
Yes
255 chars
Description for the transaction
CurrencyKey
Yes
3 chars
Three digit currency code in ISO format
Amount
Yes
15 nums
The amount of the transaction
CardType
Yes
6 chars
The card type which is being processed. The following values are valid:
VISA      (Visa)
MC        (MasterCard)
AMEX    (American Express)
DISC     (Discover)
DC        (Diners Club)
JCB       (JCB)
MAES_D    (Maestro -UK Domestic, formerly Solo/Switch)
CBLN     (Carte Blanche)
ENR       (EnRoute)
JAL        (JAL)
DLTA     (Delta, this card type should only be sent if backend processor is Global Collect)
VE         (Visa Electron)
DANK    (Dankort) 
LSR       (Laser)
CBLU     (Carte Bleue)
CSI        (Carta Si)
ENCD     (Encoded Account Number)
UATP      (UATP)
MAES_I   (Maestro Int'l)
ELO        (Elo, for Brazil)
TR_CARD_ISSUENUM
No (C)
5 chars
Only for Maestro UK Domestic Cards
TR_CARD_STARTDATE
No (C)
6 nums
Only for Maestro UK Domestic Cards
TR_CARD_CIDIND
No (C)
1 num
Card verification indicator used to indicate why a card verification value was not sent.  The field can contain one of the following values:
• 0: CV number service not requested
• 2: CV number on credit card is illegible
• 9: CV number was not imprinted on credit card
HD_SHIPTO_FNAME
No (C)
N/A
Customer shipping first name(s)
HD_SHIPTO_LNAME
No (C)
N/A
Customer shipping surname
HD_SHIPTO_ADDR
No (C)
N/A
Customer shipping address line 1
HD_SHIPTO_ADDR2
No (C)
N/A
Customer shipping address line 2 (optional)
HD_SHIPTO_ZIP
No (C)
N/A
Customer shipping postcode which follows the format of postcodes. Can include a space
HD_SHIPPING_METHOD
No (C)
10 chars
Shipping method, can be the following:
  • sameday: Courier or same-day service
  • oneday: Next day or overnight service
  • twoday: Two-day service
  • threeday: Three-day service
  • lowcost: Lowest-cost service
  • pickup: Store pick-up
  • other: Other shipping method
  • none: No shipping method because product is a service or subscription
HD_SHIPTO_CITY
No (C)
N/A
Customer shipping city
HD_SHIPTO_STATE
No (C)
N/A
Customer shipping US state codes, for example AL, MS, NY
HD_SHIPTO_CNTRY
No (C)
N/A
Customer shipping country, ISO format, for example, GB, IE, DE
CardHolderName
No (C)
N/A
Customer billing first name(s)
HD_ORDER_CUSTREFNUM
No (C)
50 chars
Customer number specific to the client
CardHolderAddress1
No (C)
N/A
Customer address line 1
CardHolderAddress2
No (C)
N/A
Customer address line 2 (optional)
HD_BUYER_HOSTNAME
No (C)
 
Customer host-name
CardHolderZip
No (C)
N/A
Customer postcode which follows the format of postcodes. Can include a space
CardHolderCity
No (C)
N/A
Customer city
CardHolderState
No (C)
N/A
Customer US state codes, for example AL, MS, NY
HD_BUYER_CNTCTPHONE
No (C)
N/A
Customer phone number
CardHolderCountry
No (C)
N/A
Customer country, ISO format, for example, GB, IE, DE
HD_BILLTO_BLDGNUMBER
No (C)
N/A
Customer building number
HD_BUYER_COMPANY
No (C)
N/A
Customer's company name
TR_TRANS_SUBSCID
No (C)
26 chars
Profile ID (previously called the subscription ID). If you are using Customer Profiles (previously called the Subscription Payment Services), you can request an authorisation and use a profile ID to reference the profile information
TransactionID
No (C)
N/A
Transaction ID given by Paymetric which is required for making a refund/credit back on a previous purchase
HD_MERCH_DATA1
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA2
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA3
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA4
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA5
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA6
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA7
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA8
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA9
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA10
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA11
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA12
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA13
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA14
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA15
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA16
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA17
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA18
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA19
No (C)
255 chars
Merchant defined fields for storing information
HD_MERCH_DATA20
No (C)
255 chars
Merchant defined fields for storing information
CardDataSource
No
1 char
Indicates Industry type.  Merchant should only provide the packet field if they wish to override the value provided in the configuration setting, 'Transaction Type'.
 
Allowed values:
M - MOTO/Direct Marketing
OrderDate
No
N/A
-
SalesDocNumber
No
30 a/n
Customer/Merchant defined data that references the transaction.
CardValidFrom
No
N/A
Additional Data Field Specified by the merchant
MerchantID
No
12 numeric
Chase Paymentech assigned merchant number. A unique merchant number is required for each physical store location.
PONumber
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_REFNUM
No
35 chars
Merchant's Order Reference Number
HD_MERCH_TERMID
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_AIICODE
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_FIICODE
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_TERMCAP
No
1 numeric
Describes the personal identification number (PIN) entry capability.
 
Allowed Values:
0 Unknown
1 Terminal can accept PINs
2 Terminal cannot accept PINs
8 Terminal pin pad is down
 
Merchant should only provide the infoitem if they wish to override the value provided in the configuration setting.
HD_MERCH_TERMCAPTURECAP
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_TERMLOC
No
2 numeric
Merchant should only provide infoitem if they wish to override the value provided in the configuration setting.
 
Indicates where the terminal was
00 – On the premises of the card acceptor
01 – On the premises of the cardholder (Home PC)
02 – No terminal used
HD_MERCH_TERMOUTPUTCAP
No
N/A
Additional Data Field Specified by the merchant
TR_CARD_DATAINPUTMODE
No
N/A
Additional Data Field Specified by the merchant
TR_CARD_MEMBERENTITY
No
N/A
Additional Data Field Specified by the merchant
TR_CARD_MEMBERMETHOD
No
N/A
Additional Data Field Specified by the merchant
TR_CARD_MEMBERPRSNTIND
No
N/A
Additional Data Field Specified by the merchant
TR_CARD_OUTPUTCAP
No
N/A
Additional Data Field Specified by the merchant
TR_CARD_PRSNTIND
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_CNTCTEMAIL
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_IPADDRESS
No
N/A
Additional Data Field Specified by the merchant
TR_FRAUD_OFFSET
No
N/A
Additional Data Field Specified by the merchant
TR_TRANS_ORDERID
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_DIVNUM
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_SKU
No
N/A
Additional Data Field Specified by the merchant
HD_ORDER_DATE
No
N/A
Additional Data Field Specified by the merchant
HD_ORDER_TIME
No
N/A
Additional Data Field Specified by the merchant
HD_SHIPPING_CARRIER
No
N/A
Additional Data Field Specified by the merchant
TR_TRANS_BILLPYMT
No
N/A
Additional Data Field Specified by the merchant
TR_TRANS_CURRCODE
No
N/A
Additional Data Field Specified by the merchant
TR_TRANS_PARTIALREDEMPTIONIND
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_EMAILTYPE
No
N/A
Additional Data Field Specified by the merchant
HD_ORDER_DESCR2
No
N/A
Additional Data Field Specified by the merchant
HD_BILLTO_ADDRINFO
No
N/A
Additional Data Field Specified by the merchant
HD_BILLTO_STATE
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_DOB
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_FAX
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_GENDER
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_LOCALE
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_TITLENAME
No
N/A
Additional Data Field Specified by the merchant
HD_INV_DATA1
No
N/A
Additional Data Field Specified by the merchant
HD_INV_DATA2
No
N/A
Additional Data Field Specified by the merchant
HD_INV_DATE
No
N/A
Additional Data Field Specified by the merchant
HD_INV_NUM
No
N/A
Additional Data Field Specified by the merchant
HD_INV_TEXT1
No
N/A
Additional Data Field Specified by the merchant
HD_INV_TEXT2
No
N/A
Additional Data Field Specified by the merchant
HD_INV_TEXT3
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_ORDERID
No
N/A
Additional Data Field Specified by the merchant
HD_SHIPTO_ADDRINFO
No
N/A
Additional Data Field Specified by the merchant
HD_SHIPTO_HOUSENBR
No
N/A
Additional Data Field Specified by the merchant
HD_SHIPTO_MNAME
No
N/A
Additional Data Field Specified by the merchant
HD_SHIPTO_STATECD
No
N/A
Additional Data Field Specified by the merchant
HD_SHIPTO_STREET
No
N/A
Additional Data Field Specified by the merchant
HD_SHIPTO_TITLENAME
No
N/A
Additional Data Field Specified by the merchant
HD_TAX_CUSTID
No
N/A
Additional Data Field Specified by the merchant
TR_TRANS_AUTHFLAG
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_CODE
No
N/A
Additional Data Field Specified by the merchant
HD_MERCH_TERMTYPE
No
N/A
Additional Data Field Specified by the merchant
HD_TRANS_SUBMETHOD
No
N/A
Additional Data Field Specified by the merchant
TR_HBC_CATTYPE
No
N/A
Additional Data Field Specified by the merchant
VISA_SDI
No
N/A
Additional Data Field Specified by the merchant
TR_TRANS_ACCTVERIFICATION
No
N/A
Additional Data Field Specified by the merchant
HD_BILLTO_ADDR
No
N/A
Additional Data Field Specified by the merchant
HD_BILLTO_CITY
No
N/A
Additional Data Field Specified by the merchant
HD_BILLTO_CNTCTPHONE
No
N/A
Additional Data Field Specified by the merchant
HD_BILLTO_COUNTRY
No
N/A
Additional Data Field Specified by the merchant
HD_BILLTO_ZIP
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_FNAME
No
N/A
Additional Data Field Specified by the merchant
HD_BUYER_LNAME
No
N/A
Additional Data Field Specified by the merchant
HD_SHIPTO_CNTCTPHONE
No
N/A
Additional Data Field Specified by the merchant
TR_FRAUD_SESSIONID
No
N/A
Additional Data Field Specified by the merchant
transactionType
No
N/A
Additional Data Field Specified by the merchant
BillingDateFlag
No
N/A
Additional Data Field Specified by the merchant
CaptureDateFlag
No
N/A
Additional Data Field Specified by the merchant
 
Secure Inputs
Input Fields
Required
Character Limits/
Required Input
Description
CardNumber
Yes
20 chars
Secure input of the card number
CardExpirationDate
Yes
4 chars
Secure input of the card expiry - in the format MMYY
CardCCV2
Yes
3 or 4 chars
Secure input of the card CVV2, either three or four digits long depending on the card type
 
Output
Output Fields
Description
count
Should come back as '1'
xipayvbresult
Will come back as either true or false
AVSAddress
This value is returned from the processor. Not all processors return the AVS address code response code
AVSCode
This value is returned from the processor. Not all processors return the AVS code response code
AVSZipCode
This value is returned from the processor. Not all processors return the AVS zip code response code
AccountingDocNumber
Returns a string value specifying the accounting document number
ActionCode
This value is returned from the processor
AdditionalInfo
The SAP Adapter populates this property
Amount
The amount of the transaction
AuthorizationCode
Specifies the type of transaction, e.g. Return
AuthorizationDate
Date time of when the authorisation took place
AuthorizationReferenceCode
Reference code of the authorisation
AuthorizationTime
Time of when the authorisation took place
AuthorizedThroughCartridge
The cartridge in which the authroisation took place, for example XiPayCartCyberSource.CyberSource.1
BankBatchID
This property is typically used in a scenario where the processor does not accept batches as large as the one submitted to XiPay. If the processor only accepts batches with a maximum size of 25 TransactionHeaders, the cartridge will break the batches down into smaller batches using the rules defined by the processor for determining the identifier for the batch
BankSubBatchID
The rules for setting this property are defined by the processor. Not all processors implement this property
BankTransactionID
The rules for setting this property are defined by the processor. Not all processors implement this property
BatchID
The value of this property is used to associate a series of ITransactionHeader objects with a single schedule
BillingDate
This should not be sent on authorization requests in the format YYYY-MM-DDTHH:MM:SS
BillingPlanItem
SAP: (FPLTR) Item for billing plan/invoice plan/payment cards - essentially the internal counter in SAP to identify the REQUEST line. For example, the first card entered is 000001; the second card entered is 000002; etc. First response to ANY card would be 900001, second response to ANY card would be 900002, etc
CaptureDate
This should not be sent on authorization requests in the format YYYY-MM-DDTHH:MM:SS
CaptureReferenceCode
Returns a string value specifying the capture reference code
CardCVV2
Card CVV2 as sent in on the request
CardDataSource
Will always be 'M' for MOTO transactions
CardExpirationDate
Card expiration date as sent in on the request
CardFollowOnNumber
Returns a string value specifying the card follow on number
CardHolderAddress1
Card holder address line 1
CardHolderAddress2
Card holder address line 2
CardHolderCity
Card holder city
CardHolderCountry
Card holder country
CardHolderDistrict
Card holder district
CardHolderName1
Card holder name(s)
CardHolderName2
Card holder name(s)
CardHolderName
Card holder name(s)
CardHolderState
Card holder state
CardHolderZip
Card holder postcode or zip code
CardNumber
Card number which has been tokenised
CardPresent
Whether or not the card holder was present for the transaction
CardType
The card type which has been processed. The following values are valid:
  • VISA      (Visa)
  • MC        (MasterCard)
  • AMEX    (American Express)
  • DISC     (Discover)
  • DC        (Diners Club)
  • JCB       (JCB)
  • MAES_D    (Maestro -UK Domestic, formerly Solo/Switch)
  • CBLN     (Carte Blanche)
  • ENR       (EnRoute)
  • JAL        (JAL)
  • DLTA     (Delta, this card type should only be sent if backend processor is Global Collect)
  • VE         (Visa Electron)
  • DANK    (Dankort) 
  • LSR       (Laser)
  • CBLU     (Carte Bleue)
  • CSI        (Carta Si)
  • ENCD     (Encoded Account Number)
  • UATP      (UATP)
  • MAES_I   (Maestro Int'l)
  • ELO        (Elo, for Brazil)
CardValidFrom
The date the card is valid from
ChargeAmount
The total amount of the transaction which has been charged
Client
This property is currently set by SAP to indicate the client used in the ITransactionHeader
CompanyCode
Returns a string value specifying the company code
CreationDate
This should not be sent on authorization requests in the format YYYY-MM-DDTHH:MM:SS
CurrencyKey
3 ISO code currency key which was sent in to the transaction request
CustTXN
This property is used to hold a customer message
CustomerNumber
Customer number if it was sent in to the transaction request
FiscalYear
Returns a string value specifying the fiscal year
GLAccount
Returns a string value specifying the general ledger account ID
LastModificationDate
Returns a string value specifying the last date the TransactionHeader was modified
LocationID
Returns a string value specifying the location ID for the TransactionHeader
MerchantID
Returns a string value specifying the merchant ID
MerchantTXN
Returns a string value specifying a merchant transaction message
MerchantTransactionID
Returns a string value specifying the merchant transaction ID
Message
This property is used to hold a message returned from the processor or from a workflow operation in XiPay
ModifiedStatus
ModifiedStatus is used to identify the modification status of the TransactionHeader. The XiPay Engine examines this property during specific workflow activities and acts accordingly.
Possible values for this property are listed in the following:
  • 0 - pmsNotModified
  • 1 - pmsModified
  • 2 -pmsDeleted
  • 3 - pmsInserted
OrderDate
Returns a string value specifying the date the order was placed. This should not be sent in on auth requests
OrderID
Returns a string value specifying the order ID
Origin
This property is used to identify the specific component in XiPay that is originating the current workflow operation XiPay is performing
PONumber
Returns a string value specifying the purchase order Number
PacketOperation
This property is used to identify the type of workflow operation that XiPay is to perform. The XiPay Engine examines this property and acts accordingly
Preauthorized
Returns a string value specifying the preauthorized value
ReferenceCode
Returns a string value specifying the reference code
ReferenceLineItem
Returns a string value specifying the reference line item
ResponseCode
Returns a string value specifying the response code
SalesDocNumber
Returns a string value specifying the sales doc number
SettlementAmount
Total amount settled for the transaction
SettlementDate
Date of the settlement for the transaction
SettlementReferenceCode
Returns a string value specifying the settlement amount
ShippingCaptureDate
Returns a string value specifying the shipping capture date. This should not be sent on auth requests
ShippingLocationID
Used internally by XiPay
ShippingMethod
Shipping method used for the transaction
StatusCode
Returns or sets a string value specifying the status code. The following values are possible to see:
  • 0 - Received Request
  • 100 - Authorised
  • 101 - Authorised and Acknowledged
  • 110 - Authorised Sale
  • 200 - Staged/Capture batch complete
  • 350 - Response received
  • 500 - voided
  • -1 - Failed
  • -2 - Aborted
  • -100 - Authorisation Error (failed cartridge data validation)
  • -101 - Authorisation Failed
  • - 101 - Error: Resubmitted for auth
  • -200 - Capture Error
  • -201 - Capture Failed
StatusTXN
Returns a string value specifying an informative status
TaxLevel1
Tax Level 1 value sent in to the transaction request
TaxLevel2
Tax Level 2 value sent in to the transaction request
TaxLevel3
Tax Level 3 value sent in to the transaction request
TaxLevel4
Tax Level 4 value sent in to the transaction request
TerminalID
Returns a string value specifying the terminal ID.
TransactionID
Unique Transaction identifier given by Paymetric for the specific transaction. When doing a refund, this value can be used in order to charge back from an original auth or capture
TransactionType
This property is used to hold a text message that describes the workflow operation of the TransactionHeader. Example: Authorization, CaptureBatch, ReturnCredit, Settlement, etc
VATNumberCustomer
Returns or sets a string value specifying the VAT number customer
VATNumberMerchant
Returns or sets a string value specifying the VAT number merchant
XIID
The XIID of the account which is linked to the transaction made to Paymetric
TR_CARD_ISSUENUM
Number of times a Maestro (UK Domestic) card has been issued to the account holder. The card might or might not have an issue number
TR_CARD_STARTDATE
Month and year of the start of the Maestro (UK Domestic) card validity period.
Do not include the field, even with a blank value, if the card is not a Maestro (UK Domestic) card.
Format: MMYYYY
TR_CARD_CIDIND
Card verification indicator used to indicate why a card verification value was not sent. The field can contain one of the following values:
• 0: CV number service not requested
• 2: CV number on credit card is illegible
• 9: CV number was not imprinted on credit card
HD_ORDER_DESCR1
Brief description of the order or any comment you wish to add to the order
TR_TRANS_SUBSCID
Profile ID (previously called the subscription ID). If you are using Customer Profiles (previously called the Subscription Payment Services), you can request an authorization and use a profile ID to reference the profile information
HD_SHIPTO_FNAME
Customer shipping first name(s)
HD_SHIPTO_LNAME
Customer shipping surname
HD_SHIPTO_ADDR
Customer shipping address line 1
HD_SHIPTO_ADDR2
Customer shipping address line 2
HD_SHIPTO_CITY
Customer shipping city
HD_SHIPTO_STATE
Customer shipping state
HD_SHIPTO_ZIP
Customer shipping postcode which follows the format of postcodes. Can include a space
HD_SHIPTO_CNTRY
Customer shipping country
HD_SHIPPING_METHOD
Customer shipping method which has been used
HD_MERCH_DATA1
Merchant defined fields for storing information
HD_MERCH_DATA2
Merchant defined fields for storing information
HD_MERCH_DATA3
Merchant defined fields for storing information
HD_MERCH_DATA4
Merchant defined fields for storing information
HD_MERCH_DATA5
Merchant defined fields for storing information
HD_MERCH_DATA6
Merchant defined fields for storing information
HD_MERCH_DATA7
Merchant defined fields for storing information
HD_MERCH_DATA8
Merchant defined fields for storing information
HD_MERCH_DATA9
Merchant defined fields for storing information
HD_MERCH_DATA10
Merchant defined fields for storing information
HD_MERCH_DATA11
Merchant defined fields for storing information
HD_MERCH_DATA12
Merchant defined fields for storing information
HD_MERCH_DATA13
Merchant defined fields for storing information
HD_MERCH_DATA14
Merchant defined fields for storing information
HD_MERCH_DATA15
Merchant defined fields for storing information
HD_MERCH_DATA16
Merchant defined fields for storing information
HD_MERCH_DATA17
Merchant defined fields for storing information
HD_MERCH_DATA18
Merchant defined fields for storing information
HD_MERCH_DATA19
Merchant defined fields for storing information
HD_MERCH_DATA20
Merchant defined fields for storing information
TR_TRANS_REQID
Identifier for the request
HD_MERCH_REFNUM
Order reference or tracking number that you provided in the request. If you included multi-byte characters in this field in the request, the returned value might contain corrupted characters
HOST_AUTH
Code given from the host sending in the address from Paymetric
TR_CARD_CIDRESPCODE
Result of processing the card verification number
TR_CARD_RAWAVSRESPCODE
AVS result code sent directly from the processor. Returned only if a value is returned by the processor
TR_CARD_RAWCIDRESPCODE
Card verification result code sent directly from the processor. Returned only if a value is returned by the processor
TR_CARD_RAWRESPCODE
For most processors, this is the error message sent directly from the bank
TR_CARD_RESPCODE
Numeric value corresponding to the result of the credit card authorization request
TR_TRANS_REQUESTTOKEN1
Request token data created by CyberSource for each reply. The field is an encoded string that contains no confidential information, such as an account or card verification number
IN_TRANS_CARDTRANSID
Request token data created by CyberSource for each reply. The field is an encoded string that contains no confidential information, such as an account or card verification number
TR_TRANS_INVALIDFIELD
Invalid fields which have been sent in to the transaction
TR_TRANS_MISSINGFIELD
Missing fields which has been sent in to the transaction
TR_TRANS_REQUESTTOKEN2
Request token data created by CyberSource for each reply. The field is an encoded string that contains no confidential information, such as an account or card verification number
TR_TRANS_REFID
Unique value generated by CyberSource
OperationType
The type of operation taken place from CyberSource, for example Authorization or Refund
errorMessage
PCI Pal specific error message.  Should any errors occur our internal error handling will respond with a message on the output of the flow
The help manual was created with Dr.Explain