API Overview

Payments Acquirer Implementation Guide
- Pilot Release
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Payments Acquirer Implementation
- Authorization and Capture Service Data Flow
- Merchant Services
- Processing Data Flow

Primary Service Features
- TC 33.A Capture File
- Edit Package
- File Delivery Options

Implementation Tasks
- Task 1: Create an Internal Project Plan
- Task 2: Fulfill Internal System Requirements
- Task 3: Establish Merchant Relationships
- Task 4: Request and Complete Forms
- Task 5: Complete Internal Systems Updates
- Task 6: Finish Testing
- Task 7: Establish a Go-Live Date
- Task 8: Manage Merchant Boarding
- Task 9: Monitor Production Activity

Merchant Set-Up Tasks
- Task 1: Register the Merchant
- Task 2: Choose an Integration Method
- Task 3: Download Documentation
- Task 4: Create Encryption Key
- Task 5: Merchant Codes and Test
- Task 6: Submit Quote and Contract(s)
- Task 7: Configure Merchant Banking
- Task 8: Product Configuration
- Task 9: Going Live

Testing Support
- Acquirer Testing
- Merchant Testing

Reference Information
- Enhanced Capture File Specifications
- Reject and Response Codes

Capture File Best Practices

On This Page

Reject and Response Codes

This section contains these reject and response codes:

Reject codes that the Edit Package uses to communicate invalid contents in a BIN field in the TC 33.A Capture File.

Response codes that a

Visa Platform Connect

acquirer must use to communicate to Visa that the acquirer either encountered or did not encounter errors when processing the TC 33.A Capture File.

Edit Package Reject Codes

Edit Package Reject Codes
Reject Code	Description	File
V1181	Source BIN must be 481222 for TC 33 capture transactions.	TC 33 Capture File

Back to top