The following is a list of services and use cases supported by the VisaNet Connect - Issuing APIs. If you need additional information, contact the product office at [email protected]
VisaNet Connect - Card Services APIs are for use by both full service and "lite" issuers
Issuers without Hardware Security Modules (HSMs) required for supporting card management tasks involving encryption management and PIN issuance activities.
Issuers that manage all card management tasks including issuing cards with chip data, managing ecryption keys, decrypting cryptograms, and issuing PINs.
Supported Use Cases:
1. In store (card-present): a broad range of point-of-sale payment methods including magnetic stripe ("swipe"), EMV1 ("dip"), and NFC2 ("tap") - both with or without PIN (Personal Identification Number).
2. Online (card-not-present): eCommerce, Mail Order/Telephone Order (MOTO), installments, recurring payments, and bill payments
3. Digital Wallets: payments through digital wallets including ApplePay, GooglePay, and SamsungPay.
4. ATM: withdrawals, deposits, balance inquiries, and balance transfers.
Key Features and Merchant Segments:
· Tokenization: approve tokenization requests through an account verification request message.
· EU PSD2: support for PSD2 requirements including Strong Customer Authentication, Delegated Authentication Service, and SCA exemptions.
· Visa “on-behalf-of” cardholder authentication: support for card and cardholder verification methods including Card Verification Value (CVV), Card Verification Value 2 (CVV2), Cardholder Authentication Verification Value (CAVV), and Address Verification Service (AVS).
· Automated Fuel Dispenser/Electric Vehicle Charging: support for additional data required to process AFD/EVC payments. Commercial/fleet support will be included at a later date.
· Travel and Entertainment (T&E): Support for additional data required for consumer airlines, car rentals, and lodging transactions.
· Visa Installment Service: Installment payment plans that allow consumers to divide a purchase over time into smaller equal payments.
· Cardholder-Initiated Transactions/Merchant-Initiated Transactions Framework
· Risk Scoring: Support for Visa Advanced Authorization (VAA) and Compromised Account Management System (CAMS) scores which can help issuers to optimize loss prevention and maximize profitability through effective risk-scoring capabilities.
· Account Name Inquiry (ANI): ANI enables the payment originator to verify that the name provided by a cardholder matches the name held by their issuing bank
1 EMV (Europay, Mastercard, and Visa) - a technical standard for smart payment cards and payment terminals
2 NFC - near-field communication
Provides the ability for issuers to request a new card generation or update existing card details for existing cardholders. Issuers can generate Primary Account Number (PAN), Card Verification Value (CVV), Card Verification Value 2 (CVV2), EMV Chip Data, Track 1, Track 2, Payment Account Reference Number (PAR), and PAN Reference Identifier (PRI) for a card all through an API request message. Issuers and approved personalization vendors can also use this API to request card details for physical card issuance.
Card Services API Endpoints:
Provides the ability for issuers to designate special processing conditions that will be applied at the cardholder level. This includes:
Start a Project
API Overview
API Reference