BT Secure Payments Payment Gateway

This page details the inputs, secure inputs and outputs available for the BT Secure Payments Payment Gateway, how to complete each field, and an external link to the BT Secure Payments Payment Gateway 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
clientId	Yes	char	The clientId will contain the BuyNet client reference and is used to determine the merchant account that card payment amounts will be routed to.
key	Yes	char	Authorisation key provided by BT alongside the clientId
cardholderName	Yes	30 char	Name of card holder
cardType	Yes	char	Allowable Values: AMEX DINERS ELECTRON JCB MAESTRO MASTERCARD MCDEBIT VISA VISADEBIT
cardholderPostCode	No	char	Post code for the card holder
cardholderAddress	No	50 char	Address for the card holder
merchantTxnRef	Yes	20 char	Merchant provided reference for this transaction
service	Yes	char	The type of transaction or transaction method Allowable Values: 3DAuthenticate Authenticate Authorise AuthoriseAndSettle Cancel PARes Pre3DCheckedAuthorise Pre3DCheckedAuthoriseAndSettle Pre3DCheckedAuthenticate Reclaim SettleWuthAuthCode SettleWithTransId
amount	Yes	num	Transaction amount in base unit (pence). i.e 99999 represents £999.99. Max Length 9 digits
currency	Yes	3 char	ISO Currency code. E.g. GBP, USD, EUR
occurrence	Yes	1 char	Single character. Allowable Values: O, S (One-Off ; Subsequent CCRA)
origin	Yes	1 char	Denotes where the transaction originated – 1 - MOTO J - eCommerce
captureMethod	Yes	1 char	Denotes the way the payment is captured - N – Not present K - Keyed

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 YYMM format
cv2	Yes	3 or 4 chars	Secure input of the card CVV, either three or four digits long depending on the card

Outputs

Output Fields	Description
clientIdOut	The clientId, as sent in the request
responseCode	Response code returned by BT relating to the status of the request (100 for success)
cardholderNameOut	The name for the card holder, as sent in the request
maskedPAN	The masked card number, as sent in the request
expiryDateOut	The expiry date for the card, as sent in the request
cardTypeOut	The card type for the given card number
issuingCountry	Identifies the name of the country of issue of the card used for the payment.
issuingCountryCode	Numeric code of the country of issue of the card used for the payment
serviceOut	Indicates the 'Service' value that was specified in the request message
amountOut	The amount submitted for the payment transaction
currencyOut	The currency submitted for the payment transaction
merchantTxnRefOut	The Merchant’s transaction reference recorded within Buynet (derived from a combination of componentId and paymentEventIdentifier)
originOut	The origin, as sent in the request
buynetTxnRef	A reference for the transaction provided by BT. This can be used to capture an authorized transaction at a later date.
authCode	Auth code provided by BT, can be used to capture authorized funds at a later date
cscavsResponseCode	Response code relating to AVS check
terminalId
merchantId	The Merchant Identifier used by Buynet when processing the transaction with the Merchant’s acquiring bank
messageId	ID for the response, returned by BT
acquirerName	Name of the acquiring bank
transactionDateTime	The date/time value when Buynet processed the payment request

For more details, please contact support@pcipal.com, and ask for a copy of the integration documentation for BT Secure Payments.

BT Secure Payments Payment Gateway

Inputs

Secure Inputs

Outputs

The help manual was created with Dr.Explain