(c) PCI Pal 2020. The content on this page is subject to the Disclaimer Section (found on the Introduction page)
IPSI Payment Gateway
This page details the inputs, secure inputs and outputs available for the IPSI Payment Gateway, how to complete each field, and an external link to the IPSI 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
userName
Yes
N/A
IPSI provided username
password
Yes
N/A
IPSI provided password
cardHolderName
No
200 char
The card holders name
tokenFormat
No
20 char
Pre-defined token generation formats. If not present the user default setting will be used
tokenLifeTime
No
200 char
Token life time in minutes from creation. If 0 token will not expire.
tokenExpiryDate
No
10 char
Token Expiry date in yyyy-mm-ddThh:mm:ssz format and UTC time zone.
EG: 2017-11-16T02:55:20
tokenUsageLimit
No
200 char
The number of requests a token can be used for, before being deleted
alias
No
200 char
A unique customer defined token Id to be used for future reference to this token.
division
No
200 char
Free-text field for use with miscellaneous data
channel
No
200 char
Free-text field for use with miscellaneous data
Secure Inputs
Input Fields
Required
Character Limits/
Required Input
Description
pan
Yes
19 num
Secure input of the card number
cardExpiryDate
Yes
2 num
Secure input of the card expiry - in the format MM
Outputs
Output Fields
Description
maskedPAN
MASKED Pan
cardHolderName-out
Card Holder Name, should echo the request value
cardExpiryDate
Card expiration date
tokenCallsLeft
Number of times the token can be used
channel-out
Free-text field for use with miscellaneous data
divison-out
Free-text field for use with miscellaneous data
cardToken
Tokenized card value
alias-out
A unique customer defined token Id to be used for future reference to this token.
tokenSilo
The Silo name which the token belongs to.
cardSchema
Are payment networks linked to payment credit cards, typically banks or eligible financial institution
creatorUserName
Account used to create the Token.
creatorHierarchy
The hierarchy associated with the account used to create the Token.
customerId
Unique customer id associated with the username and password provided.
errors
Error message provided by IPSI in case of a failed tokenisation
responseCode
Response code given from IPSI
Further information can be found by contacting support@pcipal.com.
