API Overview

Card Present Connect | Retail Integration Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Card Present Connect | Retail
- Enabling the Card Present Connect Platform
- Card-Present Transaction Types
  - EMV Transactions
  - Magnetic Stripe Transactions
  - Hand-Keyed Transactions
- Card-Present Transaction Risk Control Requirements

Retail Payment Services Using EMV and Card Data
- Retail EMV and Card Data
- Authorization with Contact EMV and Online PIN
  - Required Fields for Processing an Authorization with Contact EMV and Online PIN
    - Country-Specific Required Fields for Processing an Authorization with Contact EMV or Contactless PIN
  - REST Example: Processing an Authorization with Contact EMV and Online PIN
- Authorization with Contact EMV and Offline PIN
  - Required Fields for Processing an Authorization with Contact EMV and Offline PIN
    - Country-Specific Required Fields for Processing an Authorization with Contact EMV or Contactless PIN
  - REST Example: Processing an Authorization with Contact EMV and Offline PIN
- Authorization with Contactless EMV and Online PIN
  - Required Fields for Processing an Authorization with Contactless EMV and Online PIN
  - REST Example: Processing an Authorization with Contactless EMV and Online PIN
- Authorization with Magnetic Stripe Swipe
  - Required Fields for Processing an Authorization with Swiped Track Data
  - REST Example: Processing an Authorization with Swiped Track Data
- Authorizations with Hand-Keyed Data
  - Required Fields for Processing an Authorization with Hand-Keyed Data
  - REST Example: Processing an Authorization with Hand Keyed Data
- Authorization for Cash Advance with Credit Card
  - Required Fields for Authorization for Cash Advance with Credit Card
  - REST Example: Authorization for Cash Advance with Credit Card
- Authorization Reversal
  - Required Fields for Processing an Authorization Reversal
  - REST Example: Processing an Authorization Reversal
- Captures
  - Required Fields for Capturing an Authorization
  - REST Example: Capturing an Authorization
- Capture for Contact EMV Authorization
  - Required Fields for Capturing a Contact EMV Authorization
  - REST Example: Capturing a Contact EMV Authorization
- Stand-Alone Credit
  - Required Fields for Processing a Stand-Alone Credit
  - REST Example: Processing a Stand-Alone Credit
- Voids for a Capture or Credit
  - Required Fields for Voiding a Capture or Credit
  - REST Example: Voiding a Capture or Credit
- Timeout Void for a Capture, Sale, Refund, or Credit
  - Required Fields for Processing a Timeout Void for a Capture, Sale, Refund, or Credit
  - REST Example: Processing a Timeout Void for a Capture, Sale, Refund, or Credit

Introduction to PIN Debit Processing
- PIN Debit Integration
- PIN Debit Transactions
- PIN Debit Network Routing
- PIN Debit Processing Versus Credit Card Processing
- PIN Debit Reconciliation
- Track Data
- Terminal IDs
- Electronic Benefit Transfer

PIN Debit Optional Features
- Cash Back
- Merchant Descriptors
- Merchant-Inititated Reversals
- Partial Authorizations
- Payment Network Tokens
- Surcharge Fees

PIN Debit Services
- PIN Debit Purchase with Contactless EMV
  - Required Fields for a PIN Debit Purchase with Contactless EMV
  - REST Example: PIN Debit Purchase with Contactless EMV
- PIN Debit Purchase with Contact EMV
  - Required Fields for a PIN Debit Purchase with Contact EMV
  - REST Example: PIN Debit Purchase with Contact EMV
- PIN Debit Purchase with Contactless EMV and Cash Back
  - Required Fields for a PIN Debit Purchase with Contactless EMV and Cash Back
  - REST Example: PIN Debit Purchase with Contactless EMV and Cash Back
- PIN Debit Purchase with Swiped Track Data and Merchant Descriptors
  - Required Fields for a PIN Debit Purchase with Swiped Track Data and Merchant Descriptors
  - REST Example: PIN Debit Purchase with Swiped Track Data and Merchant Descriptors
- PIN Debit Partial Authorization with Swiped Track Data
  - Required Fields for a Swiped PIN Debit Partial Authorization
  - REST Example: PIN Debit Partial Authorization with Swiped Track Data
- PIN Debit Purchase with Contactless EMV and a Surcharge Fee
  - Required Fields for a PIN Debit Purchase with Contactless EMV and a Surcharge Fee
  - REST Example: PIN Debit Purchase with Contactless EMV and a Surcharge Fee
- PIN Debit Balance Inquiry with Contactless EMV
  - Required Fields for a PIN Debit Balance Inquiry with Contactless EMV
  - REST Example: PIN Debit Balance Inquiry with Contactless EMV
- PIN Debit Balance Inquiry with Swiped Track Data
  - Required Fields for a PIN Debit Balance Inquiry with Swiped Track Data
  - REST Example: PIN Debit Balance Inquiry with Swiped Track Data
- PIN Debit Credit with Swiped Track Data
  - Required Fields for a PIN Debit Credit with Swiped Track Data
  - REST Example: PIN Debit Credit with Swiped Track Data
- PIN Debit Credit with Contactless EMV
  - Required Fields for a PIN Debit Credit with Contactless EMV
  - REST Example: PIN Debit Credit with Contactless EMV
- Reverse a PIN Debit Purchase or Credit
  - Required Fields to Reverse a PIN Debit Purchase or Credit
  - REST Example: Reverse a PIN Debit Purchase or Credit
- PIN Debit EBT Purchase with a SNAP Voucher
  - Required Fields for a PIN Debit EBT Purchase with a SNAP Voucher
  - REST Example: PIN Debit EBT Purchase with a SNAP Voucher
- PIN Debit EBT Purchase with SNAP Account Swiped Track Data
  - Required Fields for a PIN Debit EBT Purchase with SNAP Account Swiped Track Data
  - REST Example: PIN Debit EBT Purchase with SNAP Account Swiped Track Data
- PIN Debit EBT Purchase with SNAP Account Swiped Track Data and Balance Inquiry
  - Required Fields for a PIN Debit EBT Purchase with SNAP Account Swiped Track Data and Balance Inquiry
  - REST Example: PIN Debit EBT Purchase with SNAP Account Swiped Track Data and Balance Inquiry
- PIN Debit EBT Purchase with a Cash Benefits Account Swiped Track Data and Cash Back
  - Required Fields for a PIN Debit EBT Purchase with a Cash Benefits Account Swiped Track Data and Cash Back
  - REST Example: PIN Debit EBT Purchase with a Cash Benefits Account Swiped Track Data and Cash Back
- Credit a PIN Debit EBT Purchase with SNAP Account
  - Required Fields to Credit a PIN Debit EBT Purchase with SNAP Account
  - REST Example: Credit a PIN Debit EBT Purchase with SNAP Account
- Reverse a PIN Debit EBT Purchase
  - Required Fields to Reverse a PIN Debit EBT Purchase
  - REST Example: Reverse a PIN Debit EBT Purchase

Mobile Point-of-Sale Payment Services
- Supported Mobile Point-of-Sale Solutions
- Authorization with an mPOS Using an Embedded Reader and Software PIN Entry
  - Required Fields for Processing an Authorization with an mPOS Using an Embedded Reader and Software PIN Entry
  - REST Example: Processing an Authorization with an mPOS Using an Embedded Reader and Software PIN Entry for Mastercard
  - REST Example: Processing an Authorization with an mPOS Using an Embedded Reader and Software PIN Entry for Visa
- Authorization with an mPOS Using an Embedded Reader and Software with No PIN Entry
  - Required Fields for Processing an Authorization with an mPOS Using an Embedded Reader and Software with No PIN Entry
  - REST Example: Processing an Authorization with an mPOS Using an Embedded Reader and Software with No PIN Entry for Mastercard
  - REST Example: Processing an Authorization with an mPOS Using an Embedded Reader and Software with No PIN Entry for Visa
- Authorization with an mPOS Using an External, Contact-Only Reader with No PIN Entry
  - Required Fields for Processing an Authorization with an mPOS Using an External, Contact-Only Reader with No PIN Entry
  - REST Example: Processing an Authorization with an mPOS Using an External, Contact-Only Reader with No PIN Entry for Mastercard
  - REST Example: Processing an Authorization with an mPOS Using an External, Contact-Only Reader with No PIN Entry for Visa
- Authorization with an mPOS Using an External Reader and Hardware PIN Entry
  - Required Fields for Processing an Authorization with an mPOS Using an External Reader and Hardware PIN Entry
  - REST Example: Processing an Authorization with an mPOS Using an External Reader and Hardware PIN Entry for Mastercard
  - REST Example: Processing an Authorization with an mPOS Using an External Reader and Hardware PIN Entry for Visa
- Authorization with an mPOS Using an External Reader and Software PIN Entry
  - Required Fields for Processing an Authorization with an mPOS Using an External Reader and Software PIN Entry
  - REST Example: Processing an Authorization with an mPOS Using an External Reader and Software PIN Entry for Mastercard
  - REST Example: Processing an Authorization with an mPOS Using an External Reader and Software PIN Entry for Visa
- Sale with an mPOS Using an Embedded Reader and Software PIN Entry
  - Required Fields for Processing a Sale with an mPOS Using an Embedded Reader and Software PIN Entry
  - REST Example: Processing a Sale with an mPOS Using an Embedded Reader and Software PIN Entry for Mastercard
  - REST Example: Processing a Sale with an mPOS Using an Embedded Reader and Software PIN Entry for Visa
- Sale with an mPOS Using an Embedded Reader and Software with No PIN Entry
  - Required Fields for Processing a Sale with an mPOS Using an Embedded Reader and Software with No PIN Entry
  - REST Example: Processing a Sale with an mPOS Using an Embedded Reader and Software with No PIN Entry for Mastercard
  - REST Example: Processing a Sale with an mPOS Using an Embedded Reader and Software with No PIN Entry for Visa
- Sale with an mPOS Using an External, Contact-Only Reader with No PIN Entry
  - Required Fields for Processing a Sale with an mPOS Using an External, Contact-Only Reader with No PIN Entry
  - REST Example: Processing a Sale with an mPOS Using an External, Contact-Only Reader with No PIN Entry for Mastercard
  - REST Example: Processing a Sale with an mPOS Using an External, Contact-Only Reader with No PIN Entry for Visa
- Sale with an mPOS Using an External Reader and Hardware PIN Entry
  - Required Fields for Processing a Sale with an mPOS Using an External Reader and Hardware PIN Entry
  - REST Example: Processing a Sale with an mPOS Using an External Reader and Hardware PIN Entry for Mastercard
  - REST Example: Processing a Sale with an mPOS Using an External Reader and Hardware PIN Entry for Visa
- Sale with an mPOS Using an External Reader and Software PIN Entry
  - Required Fields for Processing a Sale with an mPOS Using an External Reader and Software PIN Entry
  - REST Example: Processing a Sale with an mPOS Using an External Reader and Software PIN Entry for Mastercard
  - REST Example: Processing a Sale with an mPOS Using an External Reader and Software PIN Entry for Visa

Dynamic Currency Conversion Payment Services
- Authorization with Dynamic Currency Conversion
  - Required Fields for Authorization with Dynamic Currency Conversion
  - Optional Fields for Authorization with Dynamic Currency Conversion
  - REST Example: Authorization with Dynamic Currency Conversion
- Capture with Dynamic Currency Conversion
  - Required Fields for Capture with Dynamic Currency Conversion
  - REST Example: Capture with Dynamic Currency Conversion
- Sale with Dynamic Currency Conversion
  - Required Fields for Sale with Dynamic Currency Conversion
  - Optional Fields for Sale with Dynamic Currency Conversion
  - REST Example: Sale with Dynamic Currency Conversion
- Stand-Alone Credit with Dynamic Currency Conversion
  - Required Fields for Stand-Alone Credit with Dynamic Currency Conversion
  - REST Example: Stand-Alone Credit with Dynamic Currency Conversion

Retail Message-Level Validation Test Cases

On This Page

Required Fields for a PIN Debit Purchase with Contact EMV

clientReferenceInformation.code
clientReferenceInformation.partner.thirdPartyCertificationNumber: Cybersource provides the value for this field.
clientReferenceInformation.transactionId
orderInformation.amountDetails.currency
orderInformation.amountDetails.totalAmount
paymentInformation.card.sourceAccountType: Set this field to
UA
.
paymentInformation.card.useAs: Leave this field blank.
paymentInformation.paymentType.name: Set this field to
CARD
.
paymentInformation.paymentType.subTypeName: Set this field to
DEBIT
.
pointOfSaleInformation.emv.cardSequenceNumber: Required only when the card has a sequence number configured on the EMV chip.
pointOfSaleInformation.emv.tags
pointOfSaleInformation.encryptedKeySerialNumber
pointOfSaleInformation.encryptedPin
pointOfSaleInformation.entryMode: Set this field to
contactless
.
pointOfSaleInformation.pinBlockEncodingFormat: Set this field to
1
.
pointOfSaleInformation.terminalCapability
pointOfSaleInformation.trackData
processingInformation.commerceIndicator: Set this field to
retail
.

Back to top