×
Menu

Adflex Payment Gateway

 
This page details the inputs, secure inputs and outputs available for the Adyen Logic Item, how to complete each field, and an external link to the Adyen 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
20 char
Adflex provided Gateway login user code
Password
Yes
20 char
Adflex provided Gateway login user password
PSPID
Yes
10 char
Adflex provided Gateway login account code
CardHolderName
No
50 char
Card holders name. As it appears on card
Add1
No
50 char
Card holders address line 1
Add2
No
50 char
Card holders address line 2
Add3
No
50 char
Card holders address line 3
Add4
No
50 char
Card holders address line 4
Add5
No
50 char
Card holders address line 5
Postcode
No
20 char
Card holder’s postcode
TransactionRef
Yes
6 to 12 char
Transaction reference e.g. invoice number. Must be unique and between 6-12 characters
Amount
Yes
Decimal
Card Amount to authorise. In the range of 0.10 to 999,999.99 and formatted to 2 decimal places. The actual maximum allowable amount is determined by the acquiring bank used
TransactionType
Yes
1 – Sale, 4 – ContinuousAuthority, 13 – 3DSSale, 7 - Refund
The type of transaction
Currency
Yes
3 char
Three character ISO 4217 transaction currency code e.g. GBP,EUR
ProcessMode
Yes
0 – standard settlement
1 – offline authorization
2 – on hold
How the transaction is processed.
TID
No
8 char
Adflex assigned Terminal ID (TID). Leave blank for automatic assignment
CustomRef
No
20 char
Customer Reference
RequestType
Yes
createToken, authorise, tokenPayment
 
tokenIn
Yes (C)
40 char
Card Token in GUID format
cardlast4
Yes (C)
4 char
Last 4 digits of card number
 
(C) - Required if the RequestType is set to 'tokenPayment'.
 

Secure Inputs

 
Inputs Fields
Required
Character Limits/Required Input
Description
PAN
Yes
19 num
Secure input of the card number
ExpiryDate
Yes
4 num
Secure input of the card expiry - in the format MMYY
CSC
Yes
3 or 4 num
Secure input of the card CVV, either three or four digits long depending on the card
 
 

Outputs

 
Output Fields
Description
ErrorCode
Adflex ErrorCode If Error=50001(None) then processing was successful
ErrorMessage
Adflex Error Message
TxRefGUID
Unique transaction reference in GUID format
CardIssuer
Name of card issuing bank. If known
CardScheme
Card scheme name. e.g. VISA, MasterCard etc
CardType
Card Type (1 – Credit Card, 2 – Debit Card, 3 – Pre-Paid Card)
TIDrsp
Terminal ID (TID) used for the transaction
MessageNo
Authorisation message number 0000-9999. Incremented by 1 for each transaction for MID and resets to 0000 once 9999 is reached.
AuthStatus
Transaction status code.
8 = Authorised
9 = Declined
19 = Error
20 = Referral A
21 = Referral F
27 = Reversal
CSCAVSResponse
AVS Response, please refer to the AdFlex documentation for further information
AuthCode
If AuthStatus equals 'Authorised', then Authorisation Code as returned by acquiring bank, otherwise blank
TransactionRef
Transaction reference e.g. invoice number. Must be unique and between 6-12 characters
ResponseMsg
Authorisation response message from Acquiring Bank
ReferralPhoneNo
If AuthStatus is referral, then the telephone number of referrals helpline
TxDate
Transaction datetime, formatted as YYYY-MM-DD hh:mm:ss.sss
MerchantNo
Merchant Identification ID (MID) used for transaction. Assigned by the merchant's acquiring bank
Amountrsp
Amount as sent in the request
Currencyrsp
Three character ISO 4217 transaction currency code e.g. GBP,EUR
MaskedCardNo
Masked card number
CardToken
Card Token in GUID format
ProcessSeconds
No longer returned
ProcessStatus
No longer returned
 
Further information can be found by viewing the integration documentation: Adflex Integration Documentation
The help manual was created with Dr.Explain