|
Field |
Description |
Used By: |
Data Type & Length |
|
ccAuthService_cardholderVerificationMethod |
Method that was used to verify the cardholder's identity. See Europay, Mastercard, Visa (EMV). Possible values: n0: No verification n1: Signature n2: PIN This field is supported only for Cybersource integrations as described in Cybersource Integration. |
ccAuthService (R for successful EMV transactions and EMV fallback transactions) |
Integer (1) |
|
emvRequest_cardSequenceNumber |
Number assigned to a specific card when two or more cards are associated with the same primary account number. This value enables issuers to distinguish among multiple cards that are linked to the same account. This value can also act as a tracking tool when the issuer reissues cards. When this value is available, it is provided by the chip reader. When the chip reader does not provide this value, do not include this field in your request. See Europay, Mastercard, Visa (EMV). 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. |
ccAuthService (O) pinDebitCreditService (O) pinDebitPurchase The PIN debit services are supported only on FDC Nashville Global. |
American Express Direct: All other processors: String with numbers only (3) |
|
emvRequest_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 Important The following tags contain sensitive information and must not be included in this field: n56: Track 1 equivalent data n57: Track 2 equivalent data n5A: Application PAN n5F20: Cardholder name n5F24: Application expiration date n99: Transaction PIN n9F0B: Cardholder name (extended) n9F1F: Track 1 discretionary data n9F20: Track 2 discretionary data For information about the individual tags, see the “Application Specification” section in the EMV 4.3 Specifications: http://emvco.com For captures, this field is required for contact EMV transactions. Otherwise, it is optional. For credits, this field is required for contact EMV stand-alone credits and contactless EMV stand-alone credits. Otherwise, it is optional. Important For contact EMV captures, contact EMV stand-alone credits, and contactless EMV stand-alone credits, you must include the following tags in this field. For all other types of EMV transactions, the following tags are optional. n95: Terminal verification results n9F10: Issuer application data n9F26: Application cryptogram 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.
|
ccAuthService (O) ccAuthReversalService (O) ccCaptureService (See description) ccCreditService (See description) pinDebitCreditService (O) pinDebitPurchase pinDebitReversal The PIN debit services are supported only on FDC Nashville Global. |
JCN Gateway: 199 bytes All other processors: String (999) |
|
|
JCN Gateway The following tags must be included: n4F: Application identifier n84: Dedicated file name |
|
|
|
emvRequest_fallback |
Indicates that a fallback method was used to enter payment card information into the POS terminal. When a technical problem prevents a successful exchange of information between a chip card and a chip-capable terminal: 1Swipe the card or key the payment card information into the POS terminal. 2Use the pos_entryMode field to indicate whether the information was swiped or keyed. See Europay, Mastercard, Visa (EMV). Possible values: ntrue: Fallback method was used. nfalse (default): Fallback method was not used. This field is supported only on American Express Direct, Chase Paymentech Solutions, FDC Nashville Global, GPN, JCN Gateway, OmniPay Direct, and SIX. |
ccAuthService (O) ccCreditService (O) |
String (5) |
|
emvRequest_fallbackCondition |
Reason for the EMV fallback transaction. An EMV fallback transaction occurs when an EMV transaction fails for one of these reasons: nTechnical failure: the EMV terminal or EMV card cannot read and process chip data. nEmpty candidate list failure: the EMV terminal does not have any applications in common with the EMV card. EMV terminals are coded to determine whether the terminal and EMV card have any applications in common. EMV terminals provide this information to you. See Europay, Mastercard, Visa (EMV). Possible values: n1: Transaction was initiated with information from a magnetic stripe, and the previous transaction at the EMV terminal either used information from a successful chip read or it was not a chip transaction. n2: Transaction was initiated with information from a magnetic stripe, and the previous transaction at the EMV terminal was an EMV fallback transaction because the attempted chip read was unsuccessful. This field is supported only on GPN and JCN Gateway. |
ccAuthService (R with all card types for an EMV fallback transaction that occurs when an EMV transaction fails for a technical reason; otherwise, not used.) ccCaptureService (R for a forced capture with Visa for an EMV fallback transaction that occurs when an EMV transaction fails for a technical reason; otherwise, not used.) ccCreditService (R for a stand-alone credit with Visa for an EMV fallback transaction that occurs when an EMV transaction fails for a technical reason; otherwise, not used.) Do not include this field when the EMV terminal does not have any applications in common with the EMV card. |
String (1) |
|
pinDataEncryptedPIN |
Encrypted PIN. The entity that injected the PIN encryption keys into the terminal creates this value. This field is supported only for Cybersource integrations as described in Cybersource Integration, and only for processors that support chip and online PIN transactions as indicated in Table 4 , Processor Support for CVMs. |
ccAuthService (R for online PIN transactions) |
String (16) |
|
pinDataKeySerialNumber |
Combination of the POS terminal's unique identifier and a transaction counter that is used when decrypting the encrypted PIN. The entity that injected the PIN encryption keys into the terminal decrypts the encrypted PIN and creates this value. This field is supported only for Cybersource integrations as described in Cybersource Integration, and only for processors that support chip and online PIN transactions as indicated in Table 4 , Processor Support for CVMs. |
ccAuthService (R for online PIN transactions) |
String (20) |
|
pinDataPINblockEncodingFormat |
Format that is used to encode the PIN block. Possible values: n0: ISO 9564 format 0 n1: ISO 9564 format 1 n2: ISO 9564 format 2 n3: ISO 9564 format 3 This field is supported only for Cybersource integrations as described in Cybersource Integration, and only for processors that support chip and online PIN transactions as indicated in Table 4 , Processor Support for CVMs. |
ccAuthService (R for online PIN transactions) |
Integer (1) |
|
pos_environment |
Operating environment. Possible values for all card types except Mastercard: n0: No terminal used or unknown environment. n1: On merchant premises, attended. n2: On merchant premises, unattended. Examples: oil, kiosks, self-checkout, mobile telephone, personal digital assistant (PDA). n3: Off merchant premises, attended. Examples: portable POS devices at trade shows, at service calls, or in taxis. n4: Off merchant premises, unattended. Examples: vending machines, home computer, mobile telephone, PDA. n5: On premises of cardholder, unattended. n9: Unknown delivery mode. nS: Electronic delivery of product. Examples: music, software, or eTickets that are downloaded over the internet. nT: Physical delivery of product. Examples: music or software that is delivered by mail or by a courier. Possible values for Mastercard: n2: On merchant premises, unattended. Examples: oil, kiosks, self-checkout. n4: Off merchant premises, unattended, or cardholder terminal. Examples: vending machines. This field is supported only on American Express Direct.
|
ccAuthService (O) |
String (1) |