Reply Fields

Table 11Reply Fields

Field

Description

Returned By

Data Type & Length

acquirerMerchantNumber

Identifier that was assigned to you by your acquirer. This value must be printed on the receipt.

This field is supported only for Cybersource integrations as described in Cybersource Integration.

ccAuthReply

ccCreditReply

String (15)

card_cardType

Three-digit value that indicates the card type. For the possible values, see Card Types.

Cybersource Integrations

This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact Cybersource Customer Support to have your account enabled to receive these fields in the credit reply message. See Cybersource Integration.

ccCreditReply

String (3)

card_suffix

Last four digits of the cardholder’s account number. This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details.

You must contact Cybersource Customer Support to have your account enabled to receive these fields in the credit reply message.

This field is supported only for Cybersource integrations as described in Cybersource Integration.

ccCreditReply

String (4)

emvReply_combinedTags

EMV data that is transmitted from the chip card to the issuer and from the issuer to the chip card. The EMV data is in the tag-length-value format and includes chip card tags, terminal tags, and transaction detail tags. See Europay, Mastercard, Visa (EMV).

For information about the individual tags, see the “Application Specification” section in the EMV 4.3 Specifications: http://emvco.com 

Information in this guide about EMV applies to payment card processing and PIN debit processing. All other information in this guide applies only to payment card processing. PIN debit processing is available only on FDC Nashville Global.

ccAuthReply

ccAuthReversalReply

pinDebitCreditReply

pinDebitPurchaseReply

pinDebitReversalReply

The PIN debit services are supported only on FDC Nashville Global.

String (999)

encryptedPayment_errorCode

Error code returned by Bluefin when the decryption fails. See Bluefin PCI P2PE Error Codes.

ccAuthReply

ccCreditReply

String (4)

encryptedPayment_referenceID

Unique transaction identifier returned by Bluefin. You can use this value for tracking and reporting. See PCI P2P Encryption with Bluefin.

ccAuthReply

ccCreditReply

Integer (25)

issuer_responseCode 

Additional authorization code that must be printed on the receipt when returned by the processor. This value is generated by the processor and is returned only for a successful transaction.

This field is supported only for Cybersource integrations as described in Cybersource Integration, but is supported only for FDC Nashville Global and SIX.

ccAuthReply

ccAuthReversalReply

Integer (6)

paymentAccountReference

Visa-generated reference number that identifies a card-present transaction for which you provided one of the following:

nVisa primary account number (PAN)

nVisa-generated token for a PAN

This reference number serves as a link to the cardholder account and to all transactions for that account.

ccAuthReply

String (32)

pos_terminalID

Terminal identifier assigned by the acquirer. This value must be printed on the receipt.

This field is supported only for Cybersource integrations as described in Cybersource Integration.

ccAuthReply

ccCreditReply

String (8)

pos_terminalIDalternate

Identifier for an alternate terminal at your retail location. You defined the value for this field in the request message. This value must be printed on the receipt.

This field is supported only for Mastercard transactions on FDC Nashville Global.

ccAuthReply

ccAuthReversalReply

String (8)

routing_networkLabel

Name of the network on which the transaction was routed.

This field is supported only on FDC Nashville Global.

ccAuthReply

String (10)

routing_networkType

Indicates whether the transaction was routed on a credit network, a debit network, or the STAR signature debit network. Possible values:

nC: Credit network

nD: Debit network (without signature)

nS: STAR signature debit network

This field is supported only on FDC Nashville Global.

ccAuthReply

String (1)

routing_signatureCVMRequired

Indicates whether you need to obtain the cardholder's signature. Possible values:

ntrue: You need to obtain the cardholder's signature.

nfalse: You do not need to obtain the cardholder's signature.

This field is supported only on FDC Nashville Global.

ccAuthReply

String (5)

salesSlipNumber

Transaction identifier.

The difference between this field and the receiptNumber field is that Cybersource generates the receipt number, and you must print the receipt number on the receipt; whereas you can generate the sales slip number, and you can choose to print the sales slip number on the receipt.

This field is supported only on JCN Gateway.

ccAuthReply

Integer (5)