The purpose of merchant testing is to enable the merchant to test the basic success
and error conditions for each
Visa Platform Connect
service they plan to use. Merchants
integrate separately using different connectivity options.
Figure:
Merchant Testing Flow
Merchant Testing Preparation
Merchant testing is done using a Visa Acceptance Solutions simulators in a Visa
Acceptance Solutions Customer Acceptance System (CAS) environment and can occur only
after acquirer integration is complete and the service is in production or in
CAS.
A separate merchant account can be created post-production in the CAS environment for
merchant testing of card payment services using API calls, Secure Acceptance
Web/Mobile, Virtual Terminal, etc.
TCR Types
Please select the TCRs you want to receive in the Aquirer Implementation
Questionnaire. For more information about the TC 33.A Capture File, see TC 33.A Capture File.
All TCR fields are required for any selected TCRs. The TCR field list is available
upon request.
Conditional TCR records appear only when you select the TCR group to be included in
the TC-33 Capture file and when a relevant transaction is present.
