×
Menu

Pay360 Payment Gateway

 
This page details the inputs, secure inputs and outputs available for the Pay360 payment gateway, how to complete each field, and an external link to the Pay360 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
currency
Yes
3 chars
The currency of the transaction. Use the 3 character ISO-4217 code.
amount
Yes
num
The amount of the transaction.
description
No
255 char
The description of the transaction.
merchantRef
No
255 char
Mrchant reference for the Customer. Not required if registered is set to false, mandatory otherwise.
commerceType
Yes
Possible Values: ECOM, MOTO, CA.
The commerce type for the transaction.
channel
Yes
Possible Values: WEB, MOBILE, SMS, RETAIL, MOTO, IVR, OTHER.
 The sales channel for the transaction.
startDate
Yes
4 char
The start date for the card. Provide as MMYY.
cardType
Yes
Possible Values: ELECTRON, MAESTRO, MC_DEBIT, SWITCH, SOLO, MC_CREDIT, VISA_DEBIT, VISA_CREDIT. AMEX, JCB, LASER, DISCOVER, DINERS
The type of the card
card_nickname
No
255 char
The name the Customer provides for their card to allow easy selection where they register multiple cards.
cardHolderName
No
255 car
The name printed on the card.
defaultCard
No
bool
Indicates if the card being used should become the Customer’s default card.
billingAddress_line1
No
255 char
Line 1 of the card holders address.
billingAddress_line2
No
255 char
Line 2 of the card holders address.
billingAddress_line3
No
255 char
Line 3 of the card holders address.
billingAddress_line4
No
255 char
Line 4 of the Customer’s address.
billingAddress_city
No
255 char
City of the Customer’s address.
billingAddress_region
No
255 char
Region of the Customer’s address.
billingAddress_postcode
No
255 char
Post Code of the Customer’s address.
billingAddress_countrycode
No
3 chars
The 3 character ISO-3166-1 code for the Customer’s address country
 

Secure Inputs

Input Fields
Required
Character Limits/Required Input
Description
pan
Yes
19 chars
 
Secure input of the card number
cv2
Yes
3 or 4 chars
 
Secure input of the card CVV, either three or four digits long depending on the card
expiryDate
Yes
4 chars
Secure input of the card expiry - in the format MMYY
 

Outputs

Output Fields
Description
statusCode
The code for the status received from the authoriser, if applicable.
acquirerName
Name of the authoriser, if applicable.
message
The message received from the authoriser, if applicable.
authCode
The code received from the authoriser, if applicable.
gatewayReference
The reference received from the processing engine.
gatewayCode
The code for the status received from the processing engine.
gatewayMessage
The message received from the processing engine.
cv2Check
Possible Values: NOT_CHECKED, MATCHED, NOT_MATCHED
Results for the CV2 Verification checks, if applicable.
status
Possible Values: AUTHORISED, DECLINED, REVERSED, REVERSE_FAILED, ERROR
The status received from the authoriser, if applicable.
route
The name of the processing engine your transaction was submitted to.
registered
Indicates that the customer choose to register this card payment method. This field will not be present for non-card payment methods.
cardFingerprint
An identifier for the card number. If multiple customers register cards with the same PAN they will get different card tokens, but the card fingerprint will be the same for them all.
new
Indicates if this is a new card
resp_cardType
The type of card. Eg. MC_DEBIT, VISA_CREDIT, AMEX.
cardUsageType
The usage type of card. Eg. DEBIT, CREDIT.
cardScheme
The scheme of card. Eg. VISA, MASTERCARD, AMEX.
maskedPan
The masked card number. eg. 123456******1234
resp_expiryDate
The expiry date of the card. Formatted as MMYY.
issuer
The Issuer of the card.
issuerCountry
The country of the card Issuer.
resp_cardHolderName
The Cardholder’s name.
resp_cardNickname
The name the Customer provided for their Card to allow easy selection where they registered multiple cards.
resp_billingAddress_line1
Line 1 of the Customer’s billing address.
resp_billingAddress_line2
Line 2 of the Customer’s billing address.
resp_billingAddress_line3
Line 3 of the Customer’s billing address.
resp_billingAddress_line4
Line 4 of the Customer’s billing address.
resp_billingAddress_city
City of the Customer’s billing address.
resp_billingAddress_region
Region of the Customer’s billing address.
resp_billingAddress_postcode
Post Code of the Customer’s billing address.
resp_billingAddress_country
Country name of the Customer’s billing address.
resp_billingAddress_countryCode
The 3 character ISO-3166-1 code for the Customer’s billing address country.
paymentClass
The classification of payment method used. Eg. Card, Cash, PayPal
transactionId
Pay360s ID for the transaction.
resp_merchantRef
Your reference for the transaction, as sent in the request
merchantDescription
The description of the transaction provided in the request.
transaction_status
Possible Values: SUCCESS, FAILED, PENDING, EXPIRED, CANCELLED, VOIDED
The current state of the transaction.
stage
Stage for the transaction
type
Possible Values: PAYMENT, PREAUTH, PAYOUT, REFUND, CAPTURE, CANCEL, REPEAT, CASH_ISSUE, CASH_PAYMENT
Indicates the type of the transaction.
resp_amount
Indicates the requested amount of the transaction.
consumerSpend
Indicates the actual amount of the transaction. This will be zero for any type of INITIALIZE transaction, deferred transactions, and rejected transactions.
resp_currency
Indicates the currency of the transaction. Uses the 3 character ISO-4217 code.
transactionTime
The date and time we processed the transaction in ISO-8601 format.
receivedTime
The date and time Pay360 received the transaction in ISO-8601 format.
resp_channel
Possible Values: WEB, MOBILE, SMS, RETAIL, MOTO, IVR, OTHER
The Sales Channel of the transaction.
customerInitiated
 
validDate
The valid from date of the card. Formatted as MMYY.
storage
Indicates if the card details are stored for later use
fruadGuard_score
The score assigned by FraudGuard. Refer to FraudGuard documentation for further details.
attemptsOnCard
How many transaction requests have used this card in the last 24 hours.
againstAddress
Measure of identity morphing against the address.
againstEmail
Measure of identity morphing against the email address.
againstCard
Measure of identity morphing against the card details.
againstIp
Measure of identity morphing against the IP address.
outcome_status
Possible Values: SUCCESS, FAILED The overall outcome of the request.
outcome_reasonCode
A code indicating the overall outcome of the request. Refer to Errors for more information.
outcome_reasonMessage
A message indicating the overall outcome of the request. This is where we’ll provide detailed reasons for any errors. In the case of a decline this message can be very general. There can be useful guidance to the cause of the decline in processing.authResponse.gatewayMessage.
trace
ID for the response
link_rel
descriptor for link_href
link_href
URL for the receipt
 
Further information can be found by viewing the integration documentation:
 
The help manual was created with Dr.Explain