(c) PCI Pal 2020. The content on this page is subject to the Disclaimer Section (found on the Introduction page)
Verifone Payment Gateway
This page details the inputs, secure inputs and outputs available for the Verifone Logic Item, how to complete each field, and an external link to the Verifone 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
SystemID
Yes
Unique per client
Allocated ID given to the client by Verifone
SystemGUID
Yes
Unique per client
Allocated GUID given to the client by Verifone
SendAttempt
Yes
0
This field should be populated with '0'
CDATAWrapping
Yes
True or false
Either set to true or false, if false then it will not be wrapped, if true, then it will. This is enabled on the PCI Pal application
ProcessingDB
Yes
15 chars
This indicates the database to use for processing a particular request
Passcode
Yes
Unique per client
Allocated Password given to the client by Verifone
accountid
Yes
Unique per client
Account reference number, supplied to the client by Verifone
txntype
Yes
2 chars
When processing a transaction, the following field must be set from this list of values:
01 - Purchase
02 - Refund
07 - Account Check
transactioncurrencycode
Yes
3 numbers
Currency code in ISO 3166 format, which is in numerical form, not alphabetical (please check page 181 onwards for the correct codes in the integration guide - link provided at the bottom of this page)
terminalcountrycode
No
3 numbers
Currency code in ISO 3166 format, which is in numerical form, not alphabetical (please check page 181 onwards for the correct codes in the integration guide - link provided at the bottom of this page)
processingidentifier
No
1 numbers
This indicates the type of processing that needs to be undertaken. Current available values are as follows:
1 – Auth and Charge
2 – Auth Only
3 – Charge Only
All refund transactions should use the ‘Charge Only’ option
tokenid
No
18 chars
Token Identifier for token transaction
avshouse
No
0 or 1
Field checked by Address Verification System (AVS) add on module, ignored if module not enabled. AVS configuration can make this field mandatory. Numerics from house name/number
avspostcode
No
0 or 1
Field checked by Address Verification System (AVS) add on module, ignored if module not enabled. AVS configuration can make this field mandatory. Numerics from postcode only
gisid
No
n/a
Reserved for future use, not applicable for now
employeeid
No
Unknown chars
Field used to add more information on the employee
vgistransaction
No
Unknown chars
Denotes if the transaction is a procurement card/VGIS transaction.Ensure the Procurement Guide Specification is utilised alongside the Web Services Integration Guide for full VGIS data requirements
tokenexpirationdate
Yes
DDMMCCYY Format
Last date on which the token can be utilised. Format of date to be: DDMMCCYY
merchantreference
No
n/a
Merchant can add a reference to cross reference responses relating to the same transaction
issuenumber
Conditional
2 numbers
1 or 2 digit card issue number as shown on the front of the card. Only required by some Switch, and Laser cards. Required only when card is keyed
startdate
Conditional
MMYY format
Card start date month and year (MMYY). Only required for Diners Club International, and some Maestro and Laser cards. Not required if Track2 data supplied
txnvalue
Yes
0.01 to 100,000.00
Transaction Value which is mandatory when the MessageType is set to TXN
cashback
No
Decimal values
Total Cash Back value for PWCB transactions. Values will be truncated (without rounding) to the number of decimal places required for the transaction currency. Positive values only
gratuity
No
Decimal values
Additional value to add to the total of the transaction, for example, a service tip
authcode
No
Chars
Only supplied for offline transaction
transactiondatetime
No
dd/mm/yyyy hh:mm:s
Date and time the transaction was started (based on GMT)
refund
Yes
0 or 1
Allows a refund of the txn type, only required for when the MessageTpe is TKI or TKI2
purchase
Yes
0 or 1
Allows a purchase of the txn type, only required for when the MessageType is TKI or TKI2
MessageType
Yes
TXN or TKI/TKI2
Sets the type of transaction, currently we support payment transactions (TXN) or token (0 value transactions of type TKI or TKI2)
Secure Inputs
Input Fields
Required
Character Limits/
Required Input
Description
pan
Yes
19 chars
Secure input of the card number
expirydate
Yes
4 chars
Secure input of the card expiry - in the format MMYY
cnn
Yes
3 or 4 chars
Secure input of the card CVN, either three or four digits long depending on the card type
Outputs
Output Fields
Description
transactionId
The merchantid used to process the transaction
resultdatetimestring
Extended date and time string in the format: YYYY-MM-DD-THH:MM:SS:sss
processingdb
Linked back to the processingfdb which has been sent in the original request
errormsg
Error message related to Verifone
merchantnumber
Unique Merchant Number
tid
Terminal ID
schemename
Card scheme name
1 – Amex
2 – Visa
3 – MasterCard/MasterCard One
4 – Maestro
5 – Diners
6 – Visa Debit
7 – JCB
8 – BT Test Host
9 – Time / TradeUK Account card
10 – Solo (ceased)
11 – Electron
21 – Visa CPC
23 – AllStar CPC
24 – EDC/Maestro (INT) / Laser
26 – LTF
27 – CAF (Charity Aids Foundation)
28 – Creation
29 – Clydesdale
31 – BHS Gold
32 – Mothercare Card
33 – Arcadia Group card
35 – BA AirPlus
36 – Amex CPC
41 – FCUK card (Style)
48 – Premier Inn Business Account card
49 – MasterCard Debit
51 – IKEA Home card (IKANO)
53 – HFC Store card
999 – Invalid Card Range
messagenumber
Transaction message number
authcode
The authorisation code which is returned by the bank. This will be blank if the transaction is declined and if the transaction value is below the floor limit
vrtel
Telephone number to be called by the operator to seek manual authorisation. Only supplied for referred transactions
txnresult
Transaction Result, will be the following:
ERROR
REFERRAL
COMMSDOWN
DECLINED
REJECTED
CHARGED
APPROVED
AUTHORISED
AUTHONLY
pcavsresult
Postcode AVS result, will be the following:
0 - Not provided
1 - Not checked
2 - Matched
4 - Not matched
8 - Partial match
ad1avsresult
Address Line 1 AVS result, will be the following:
0 - Not provided
1 - Not checked
2 - Matched
4 - Not matched
cvcresult
CVC result, will be the following:
0 - Not provided
1 - Not checked
2 - Matched
4 - Not matched
arc
Acquirer response code
iadarc
Authorisation response cryptogram
iadoad
Optional additional data
isd
Issuer script data
authorisingidentity
This indicates who performed the authorisation processing, will be the following:
0 - Not Provided
1 - Merchant
2 - Acquirer
4 - Card Scheme
8 - Issuer
tokenid
Unique identifier for registered PAN. The maximum size limit for this field is 18
cardschemename
Returns the card scheme name for the card registered for that request
errorcode
This is an error code indicating what type of error occurred, if any
merchantreference
Merchant specified reference, in order to cross reference responses to the same transaction
errormsg
Verifone specific error message
code
Verifone specific error code
msgtxt
Verifone specific error message, which will only be populated should there be an code
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
Verifone Logic Item
The Verifone Logic Item contains the following properties:
System ID
System ID allcocated by Verifone, merchant specific
For added security the Verifone endpoints have been hardcoded into the integration. Test or Live needs to be selected from the Select Endpoint drop down list, depending on the transaction being conducted.
