Cloud Connect Client Implementation Guide

Visa Cloud Connect Client Implementation Guide v0.
3
_____________________________________________________________________________________________________________________________________
Visa Cloud Connect

Client Implementation Guide
Version 0.3
Effective: January 12th, 2022
1
© 2022 Visa. All Rights Reserved. Visa Confidential
Visa Cloud Connect Client Implementation Guide v0.3
_____________________________________________________________________________________________________________________________________
Important Note on Confidentiality and Copyright
The Visa Confidential label signifies that the information in this document is confidential and proprietary to Visa
and is intended for use only by Visa Clients subject to the confidentiality and feedback provisions in the Visa
Core Rules and Visa Product and Service Rules, non-Client Third-Party Processors that have an executed and valid
VisaNet Letter of Agreement on file with Visa, and other third parties that have a current participation agreement
with Visa that covers confidentiality of the information contained herein and Visa’s use of feedback.
This document is protected by copyright restricting its use, copying, distribution, and decompilation. No part of
this document may be reproduced in any form by any means without prior written authorization of Visa.
Visa and other trademarks are trademarks or registered trademarks of Visa.
All other product names mentioned herein are the trademarks of their respective owners, used for illustrative
purposes only and don’t imply affiliation with Visa or endorsement.
THIS PUBLICATION IS PROVIDED AS IS, WITH ALL FAULTS, AND COULD INCLUDE TECHNICAL INACCURACIES
OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN: THESE
CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THE PUBLICATION. VISA MAY MAKE IMPROVEMENTS
AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY
TIME.
Visa has no insight into or control over AWS or any Client technical infrastructure components and no
responsibility or liability with respect to any acts, omissions, features or maintenance of AWS or such
components, including acts, omissions, features or maintenance that influence the Visa Cloud Connect services.
Benefits are illustrative only and depend on implementation details and business factors.
If you have technical questions or questions regarding a Visa service or questions about this document, please
contact your Visa representative.
2
_____________________________________________________________________________________________________________________________________
Contents
Additional Required Documentation ...................................................................................................................................... 4
Purpose and Audience.................................................................................................................................................................. 5
Contact Information ...................................................................................................................................................................... 5
1 Visa Cloud Connect........................................................................................................ 6

Overview ............................................................................................................................................................................................. 6
Visa Cloud Connect – G l o b a l A r c h i t e c t u r e ............................................................................................................ 6-7
Highlights of Visa Cloud Connect ............................................................................................................................... 7-8
2 Implementation and Activation Activities .................................................................. 9

The Role of Visa ............................................................................................................................................................................... 9
Implementation Support ............................................................................................................................................................. 9
Post-Implementation Support ................................................................................................................................................... 9
Connectivity ...................................................................................................................................................................................... 9
Endpoint - Visa Cloud Connect AWS Private Link Connection ......................................................................... 10
EAS-C Endpoint Connection ........................................................................................................................................... 10
Endpoint Network Requirements.................................................................................................................................. 10
Configuration Window ...................................................................................................................................................... 11
3 Participation Requirements ........................................................................................ 12

Overview ...........................................................................................................................................................................................12
Deployment and Onboarding..................................................................................................................................................12
Deployment Requirements ....................................................................................................................................... 12-13
Forms........................................................................................................................................................................................ 13
Deployment Activities ................................................................................................................................................. 13-15
4 Endpoint Network Connectivity .......................................................................... 16-20
3
_____________________________________________________________________________________________________________________________________
Additional Required Documentation

1. Extended Access Server – Centralized Client Implementation Guide
4
_____________________________________________________________________________________________________________________________________
About This Guide

This guide contains general and technical information for Visa Cloud-based Endpoints
(Endpoint) and Visa regional staff about Visa Cloud Connect and explains deployment
requirements.
In this document, the term “Endpoint” refers to Visa members, processors, and other
approved entities who have Cloud-based processing infrastructures which are directly
connected to Visa via Visa Cloud Connect for file or message processing.
Purpose and Audience

The Visa Cloud Connect - Client Implementation Guide is written for technical and
management personnel at the Visa Regions and their Endpoint customers involved in
implementing and maintaining the Visa Cloud Connect technology.
Contact Information
Visa staff members are available to assist Endpoints with implementation of Visa Cloud
Connect deployment projects. For special requirements or more information, contact your
Visa Regional Representative.
5
_____________________________________________________________________________________________________________________________________
1 Visa Cloud Connect

Overview
Visa Cloud Connect provides a secure way for financial institutions, processors, fintechs and approved third
parties who have Cloud based processing infrastructures to connect directly to VisaNet via Visa’s cloud
based access infrastructure for efficient acceptance and authorization of all types of card transactions, using
one message format.
Visa Cloud Connect provides multiple redundant connections from the Endpoint to VisaNet and the ability
to support multiple clients through a Centralized Extended Access Server (EAS-C). It accepts and routes
authorizations for all card and transaction types including non-Visa transactions to be routed by Visa to the
appropriate card association or gateway for processing. Endpoints only have to support one format - Visa
provides the message translation where necessary. In addition, endpoints can send and receive batch files
to/from VisaNet core processing systems.
Clients using Visa Cloud Connect do not need to have an Extended Access (EA) Server or Visa-owned
network equipment on their premises as it is hosted by Visa on their behalf via a Centralized Extended
Access Server (EAS-C). Visa Cloud Connect is implemented in conjunction with Visa’s hosted EAS-C and
clients must also be familiar with the EAS-C Client Implementation Guide as part of Visa Cloud Connect
deployment.
Visa Cloud Connect – Global Architecture

Visa Cloud Connect is a VisaNet connectivity option available to approved clients who have a Cloud
based processing infrastructure. At this time Visa Cloud Connect only supports client Cloud based
infrastructures hosted at the following Cloud Providers:
• Amazon AWS1
Visa has established public Internet peering locations globally with Amazon AWS. These global public
Internet peering locations with co-located datacenters enable Visa to establish optimal connectivity
globally between Amazon AWS via their Private Link service and Visa’s global private backbone
infrastructure for connectivity to VisaNet.
Visa’s global public peering Points of Presence (POPs) are associated with AWS regions as follows:
Amazon Region Visa POP
North/South America San Jose & Ashburn (March 2022)
Europe/Middle East/Africa London & Frankfurt (planned Q2 2022)
Asia Singapore & Hong Kong (planned Q3 2022)
1
“Amazon” and ”AWS” are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other
countries.
6
_____________________________________________________________________________________________________________________________________
Visa Cloud Connect’s global architecture is illustrated in

Figure 1-1 below.
Figure 1-1: Visa Cloud Connect Global Architecture
Highlights of Visa Cloud Connect

1. Clients will manage their own regional Virtual Private Cloud (VPC)
▪ Clients are expected to work with the participating Cloud provider and manage their
own VPC
2. Visa will expose it’s AWS Private Link service to approved and trusted clients and allow
interconnection to Visa’s VPC
7
_____________________________________________________________________________________________________________________________________
3. Visa’s VPCs have been established across multiple Availability Zones (AZ’s) in each AWS
region globally
4. Visa VPCs will provide approved connected clients access to a Visa hosted Centralized
Extended Access Servers (EAS-C) that enables clients to connect to VisaNet at multiple Visa
Datacenters. Clients will not be required to host their own EA Server or Visa-owned network
equipment.
5. EAS-C provides clients access to VisaNet core processing functionality of authorization,
clearing and settlement and additional value added service functions (refer to Extended Access
Server – centralized Client Implementation Guide for full details)
6. Visa plans to establish additional POPs globally in the future as demand and volumes grow in
the various geographical regions
8
_____________________________________________________________________________________________________________________________________
2 Implementation and Activation Activities

There are specific implementation and activation activities for Endpoints wanting to
establish VisaNet connectivity via Visa Cloud Connect.
The Role of Visa

Visa provides the Visa Cloud Connect environment and hosting of the EAS-C installations
and provides continuous support for these infrastructures. This support includes
configuring Endpoint access to Visa Cloud Connect and the EAS-C device and “ traffic
volumes and service options.
Implementation Support
Visa will complete all implementation activities for the Endpoint including:
• Network planning, configuration and connectivity of clients already established AWS Private
Link VPC to Visa Cloud Connect
• Provisioning the EAS-C configuration for Visa services by Endpoints
• Creating the profiles to customize the EAS-C configuration to Endpoint’s requirements.
• Activating Visa Cloud Connect and the EAS-C configuration in coordination with the
Endpoint.
Post-Implementation Support
Visa personnel support the following processes:
• Monitoring the Visa Cloud Connect AWS Private Link connection with Endpoints
• Monitoring EAS-C operation.
• Diagnosing and resolving network connectivity and software problems on the Visa side.
• Updating network and software releases.
Connectivity
Visa and the Endpoint work together to establish the AWS Private Link connection between
the client VPC and Visa’s VPC as well as to the Visa Extended Access Server – Centralized
(EAS-C) server for VisaNet message and file processing. Endpoint agrees to perform any
and all actions and provide any and all information that Visa may request for such
purposes.

9
_____________________________________________________________________________________________________________________________________
Endpoint - Visa Cloud Connect AWS Private Link Connection

Visa supplies the Endpoint with the Visa Cloud Connect AWS Private Link configuration and
network configuration requirements via a questionnaire. Clients are also required to provide
their VPC and AWS Private Link configuration via the questionnaire back to Visa in order for
Visa to successfully configure the clients VPC connectivity to Visa Cloud Connect.
EAS-C Endpoint Connection

Visa provides the Endpoint with the Visa hosted EAS-C hardware and network connectivity.
Visa will provide the Endpoint with configuration details for the EAS-C via a questionnaire
and Endpoints in turn are also required to provide Visa with the relevant information
requested in the questionnaire in order to successfully setup the Endpoints parameters on
the EAS-C.
Endpoint Network Requirements

To support Endpoint connectivity to Visa Cloud Connect, among other things, the following
network requirements must be met:
• Endpoint must establish AWS Private Link service for their VPC(s) with Amazon AWS
• Endpoint must establish connectivity to Visa’s Private Links from their VPC(s) for the purpose
of connecting to two in-region Visa Cloud Connect POPs (redundant connections)
• Endpoint must configure their network environment and provide the necessary information
as stipulated in the network questionnaire shown in Appendix A
• Endpoints must adhere to the EAS-C connectivity requirements and must provide all the
necessary setup information as stipulated in the EAS-C questionnaire as shown in Appendix
A
• Endpoints are solely responsible for implementing Edit Package if this service is required as
part of Visa Cloud Connect. Visa does not provide native Cloud based Edit Package support
for Visa Cloud Connect at this time. Endpoints may virtualize Windows PC Edit Package for
usage where required, however implementation of this feature is the responsibility of the
Endpoint
• Endpoints are solely responsible for providing Hardware Security Module (HSM) capability
for their processing on Visa Cloud Connect. Visa provides a limited On-Behalf-Of (OBO)
service for HSM support at this time (contact your Visa representative for more details)
• Endpoints are required to use a private Visa CA issued client PKI certificate for TLS
connection to the EAS-C for both VIP and Clearing and Settlement processing. The EAS-C
will present a private Visa CA issued PKI server certificate upon connection with the
Endpoint. Endpoints must trust the private Visa CA root/sub root and/or EAS-C server
certificate issued by the private Visa CA in order for a successful connection to be
established between the Endpoint and the EAS-C
10
_____________________________________________________________________________________________________________________________________
Configuration Window
Endpoints must inform Visa about any proposed changes in schedule or configuration as
soon as possible. Endpoints must submit requests for configuration changes in advance for
proper planning, verification, and scheduling. The configuration changes will be scheduled
for three weeks (barring any unforeseen delays), after the request is validated and accepted.
Endpoints must ensure that all information provided is accurate and acknowledge that any
changes after submission will incur delay on the change schedule.
NOTE: Any configuration changes in the Endpoint network could impact the Visa Cloud Connect and EAS-C
connectivity to Visa. Endpoints should inform Visa about such changes with at least 1 months prior
notice.
11
_____________________________________________________________________________________________________________________________________
3 Participation Requirements
Visa Cloud Connect is available to Visa-approved Endpoints.
Overview
Visa clients, such as licensed acquirers, issuers, processors, fintechs or third parties who
want to connect to VisaNet via Visa Cloud Connect for card payment processing services
must meet the following requirements:
• Client must enter into a signed written agreement for the participation in Visa Cloud
Connect and adhere to the provisions therein.
• Visa Cloud Connect must be deployed for the approved applications only and meet the
minimum transaction volume threshold, as amended from time to time in Visa’s sole
discretion.
NOTE: For the current list of the approved applications and the minimum transaction
volume threshold, contact your regional client support representative.
• All clients must adhere to the provisions of the Visa Core Rules applicable to Visa clients
connected directly to VisaNet and their use of the Visa Cloud Connect platform.
NOTE: Clients that are not currently connected to VisaNet will be required to complete
the Visa Global Endpoint Review.
• Clients must maintain compliance with the Payment Card Industry Data Security Standard
(PCI DSS) and other security standards defined by Visa’s Account Information Security (AIS)
program. Clients must submit their Report on Compliance (RoC) on an annual basis and, in
addition, upon request to Visa. Visa will validate the client’s PCI DSS compliance prior to
initiation of the Visa Cloud Connect implementation activities.
• Clients must adhere to this Visa Cloud Connect Client Implementation Guide, as well as other
related and required documentation provided by Visa.
• Clients must adhere to all applicable laws, regulations, and other legal requirements.
Visa reserves the right to suspend or terminate a client’s participation in the Visa Cloud
Connect platform at any time without prior notice if Visa determines, at its sole discretion,
that the client is not in compliance with the above requirements or any other situation that
may warrant the service to be terminated.
Deployment and Onboarding

Deployment and onboarding of clients on the Visa Cloud Connect platform will require
different implementation tasks for Visa and VisaNet connected clients.
Deployment Requirements
Requirements for deploying on the Visa Cloud Connect platform vary based on application
eligibility criteria, transaction volume, and participation eligibility. Table 3-1 summarizes the
requirements.
12
_____________________________________________________________________________________________________________________________________
Table 3-1: Deployment Requirements
Deployment/Participation Licensed Existing VisaNet Sponsored

Requirement Issuer/Acquirer Endpoint Processor/Merchant
Visa Sponsorship Not Required Required Required
Approved Application/Product Required Required Required
Volume - over 5M trn/month (for Required Required Required

approved application/product)
Visa Approval Required Required Required
Endpoint Review Not Required Not Required Required
NOTE : Global Endpoint Review is not required for clients with existing VisaNet endpoint connections.
Forms
Clients must complete enrollment and implementation forms to deploy on the Visa Cloud
Connect platform.
Table 3-2: Forms
Form Requirements
Visa Cloud Connect Service Request Mandatory

Form
Acquirers and issuers must complete this form and receive prior approval for each
sponsored payment technology provider prior to initiating any implementation
activities.
Visa reserves the right to suspend or terminate a client’s participation on the Visa
Cloud Connect platform at any time without prior notice if Visa determines, at its
sole discretion, that the client is not in compliance with Visa’s requirements.
Deployment Activities
The following table details the steps and activities required for acquirer, issuer or VisaNet
processor to implement Visa Cloud Connect.
Table 3-3: Steps for Participation
13
_____________________________________________________________________________________________________________________________________
Step Details
1. Create a project plan Acquirers, issuers and VisaNet processors should work with their Visa Regional
Implementation Manager (VRIM) to create a project plan for deploying Visa Cloud
Connect.
The project plan should include tasks for internal departments, including but not
limited to any anticipated coding changes to a client’s systems and their internal
procedures.
To complete a project plan, the appropriate internal business and technology areas
should first be contacted to form a project task force.
Clients should request any Visa documentation needed from their VRIM and distribute
it to the task force.
Because each client’s internal system and business needs are unique, the task force
must determine the activities that will be required for participation and include them
in the project plan.
Once the project plan is complete, it should be shared with their VRIM.
2. Ensure internal systems Prior to go live, clients must ensure readiness of their systems, including, but not
requirements limited to Cloud based processing infrastructure, ISO8583 messaging and File Services
application.
3. Request required forms Clients must request the required forms and any supporting Visa documentation
needed from their VRIM.
4. Complete and submit the A VRIM will assist clients as needed in completing the required forms.
required enrollment and
After the forms have been completed, they should be sent to your VRIM for
implementation forms
processing.
Additional discussion with Visa staff may be required after the forms have been
completed and submitted.
NOTE: Clients that are not existing VisaNet Endpoints must submit a Visa Global
Endpoint Questionnaire to Visa to initiate a risk and business reviews. Business review
approval is required prior to proceeding with the implementation activities.
5. Complete internal system Clients must ensure their infrastructure and systems are modified to connect with Visa
updates Cloud Connect and EAS-C
14
_____________________________________________________________________________________________________________________________________
6. Complete connectivity testing A VRIM may assist clients in developing a detailed test plan that is tailored to their
individual needs.
NOTE: Clients will be able to conduct connectivity testing only. It is expected that
clients will complete all necessary testing and certification of their applications prior to
deploying in the Visa Cloud Connect platform production environment.
7. Establish a production go-live After the EAS-C connectivity testing is complete, clients should contact their VRIM to
date confirm their production go-live date.
Visa will target the originally agreed upon go-live date unless a client requests a
change. Visa requires at least 15 business days advance notice prior to an agreed upon
production go-live date to change the date.
NOTE: Clients that are new VisaNet Endpoints must receive Visa Global Endpoint
Review approval, including risk, compliance, and business review approval before
proceeding with production implementation.
8. Monitor production activity Clients should confirm with their VRIM that after their Visa Cloud Connect
implementation goes live, Visa will monitor and verify that the production
environment setup is correct.
15
_____________________________________________________________________________________________________________________________________
4 Endpoint Network Connectivity

This chapter describes the network connection that the Visa Extended Access Server –
Centralized (EAS-C) server supports for Visa Cloud Connect and the Endpoint’s connection
requirements and options.
Overview
The Visa Extended Access Server – Centralized (EAS-C) server is located at a POP with
Endpoints connecting via the network topology described previously in this document, as
shown in Figure 4-1.
Figure 4-1: EAS-C Physical Network Connection
Visa POP AWS
Visa
Applications
Visa Network Private Link Endpoint VPC
(VIP,APF)
Visa Network
Equipment and
Extended Access
Server - Centralized
Visa coordinates and assists Endpoints with their EAS-C provisioning by supplying the
required communications interface and Private Link to connect to the EAS-C server that, in
turn, connects to Visa’s core systems.
Redundant VIP Connections
Endpoints are required to establish redundant and concurrent connections to 2 POPs for VIP
processing utilizing separate host stations for all PCRs so that in the event of an outage to a
single POP traffic will continue under each PCR to the other POP.
Geographical Redundancy
Visa requires that Endpoints connect to two POPs, each hosting EAS-C servers in a failover
pair, to ensure a viable failover in the event of scheduled maintenance or an unforeseen
outage.
Geographical Failover is described in the section Geographical Failover.

16
_____________________________________________________________________________________________________________________________________
Relevant Protocol Publications

The TCP/IP and related protocols that the EAS-C server supports are specified in RFCs
(Requests for Comment) published by industry-standard organizations. These documents
and other industry-standard information can be found at these sites:
• http://www.ietf.org/
• http://www.w3.org/
The following RFCs are relevant:
• TCP/IP and FTPS support:
- RFC 791 Internet Protocol
- RFC 792 Internet Control Message Protocol
- RFC 793 Transmission Control Protocol
- RFC 959 File Transfer Protocol
- RFC 4217 Securing FTP with TLS
• Ethernet support:
- RFC 894 Standard for the Transmission of IP Datagrams over Ethernet Networks
- RFC 1042 Standard for the Transmission of IP Datagrams over IEEE 802 Networks
Background information relating to socket implementation can be found in Berkeley ver.

7.13, April 20, 1991 for the TCP/IP sockets implementation.
Visa cannot predict the results of unsupported commands and cannot guarantee that the
EAS-C will accept or reject such commands.
Server-to-Endpoint Network Connections
This section provides information to configure TCP/IP and establish a network connection
between the Endpoint and the EAS-C server.
Endpoints should follow the industry-standard recommendations reflected in the following
tables.
Endpoint Communications Protocol Requirements

Endpoint hardware and software requirements to connect with the EAS-C server are listed
in Table 4-1.
Table 4-1: Message Processing Protocol and Host Requirements
EAS-C Service Network Access Layer Internet Host-to-Host Endpoint Application

Layer Layer Software
Message IEEE 802.3 (Ethernet) IPv4 TCP Endpoint-supplied socket

Processing program
17
_____________________________________________________________________________________________________________________________________
Protocol Overview
The protocol layers that make up the network protocol and TCP/IP exchange are shown in
Table 4-2, from the bottom layer up.
Table 4-2: TCP/IP Layers
TCP/IP Layer Service
Application Layer Messaging Service (socket) with optional encryption (TLS)
File Services (FTPS)
Host-to-Host Layer TCP
The transmission control protocol (TCP) is used in packet- switching computer

communication networks and in interconnected systems of such networks. TCP is
an end-to-end protocol designed to fit into a layered hierarchy of protocols that
support multi-network applications. TCP provides:
Basic data transfer
Flow control
Multiplexing
Connection management
Precedence
Internet Layer IP
The Internet Protocol (IP) is used in interconnected systems of packet-switching
computer communication networks to transmit data blocks (datagrams) from
sources to destinations, which are hosts identified by fixed-length addresses.
ICMP
The EAS-C responds to Internet Control Message Protocol (ICMP) “ping”
messages. Endpoints may choose to permit ICMP packets between their systems
and the EAS-C to facilitate connectivity troubleshooting.
Network Access Layer Ethernet (standard physical connector is RJ-45)
This layer provides the means for the system to deliver data to other systems
directly attached to the network.
18
_____________________________________________________________________________________________________________________________________
Data Encoding Requirements

All data is transmitted in 8-bit binary code with no special or control characters.
Geographic Failover
EAS-C is designed to operate for extended periods between normal, planned maintenance.
The geographic failover capability of CCDC and EAS-C is designed to ensure that in the
event of planned or unplanned maintenance, the connections intended EAS-C land at an
alternate POP. Sockets must be re-established by the endpoint after geographic failover
occurs.
Redundant VIP connections are designed to ensure that there is no complete outage to VIP
processing while failover occurs.
Endpoints are strongly encouraged to initiate the HeartBeat message and incorporate
automatic traffic redistribution to other stations and/or reconnection logic in the event no
response to a HeartBeat is received to minimize down-time.
Endpoints must respond to HeartBeat requests generated by EAS-C.
The effective network path during normal operation and after a geographical failover is
shown in Figure 4-1 and Figure 4-2.
Figure 4-1: Normal Network Path
Normal network path

EA Server
Endpoint VPC
Primary POP
Private Link Endpoint
VPC
EA Server
Secondary POP
19
_____________________________________________________________________________________________________________________________________
Figure 4-2: After Geographical Failover
EA Server
Primary POP
Private Link Endpoint
VPC
EA Server
Network path after
geopraphic failover
Secondary POP
20

Cloud Connect Client Implementation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cloud Connect Client Implementation Guide

Uploaded by

Copyright:

Available Formats

Visa Cloud Connect Client Implementation Guide v0.

Visa Cloud Connect

Important Note on Confidentiality and Copyright

Visa and other trademarks are trademarks or registered trademarks of Visa.

Purpose and Audience.................................................................................................................................................................. 5

Contact Information ...................................................................................................................................................................... 5

1 Visa Cloud Connect........................................................................................................ 6

Visa Cloud Connect – G l o b a l A r c h i t e c t u r e ............................................................................................................ 6-7

Highlights of Visa Cloud Connect ............................................................................................................................... 7-8

2 Implementation and Activation Activities .................................................................. 9

Implementation Support ............................................................................................................................................................. 9

Post-Implementation Support ................................................................................................................................................... 9

Endpoint - Visa Cloud Connect AWS Private Link Connection ......................................................................... 10

EAS-C Endpoint Connection ........................................................................................................................................... 10

Endpoint Network Requirements.................................................................................................................................. 10

Configuration Window ...................................................................................................................................................... 11

3 Participation Requirements ........................................................................................ 12

Deployment and Onboarding..................................................................................................................................................12

Deployment Requirements ....................................................................................................................................... 12-13

Deployment Activities ................................................................................................................................................. 13-15

4 Endpoint Network Connectivity .......................................................................... 16-20

Additional Required Documentation

About This Guide

Purpose and Audience

1 Visa Cloud Connect

Visa Cloud Connect – Global Architecture

Visa Cloud Connect’s global architecture is illustrated in

Highlights of Visa Cloud Connect

2 Implementation and Activation Activities

The Role of Visa

© 2022 Visa. All Rights Reserved. Visa Confidential

Endpoint - Visa Cloud Connect AWS Private Link Connection

EAS-C Endpoint Connection

Endpoint Network Requirements

Deployment and Onboarding

Table 3-1: Deployment Requirements

Deployment/Participation Licensed Existing VisaNet Sponsored

Visa Sponsorship Not Required Required Required

Approved Application/Product Required Required Required

Volume - over 5M trn/month (for Required Required Required

Visa Approval Required Required Required

Endpoint Review Not Required Not Required Required

Visa Cloud Connect Service Request Mandatory

Table 3-3: Steps for Participation

4 Endpoint Network Connectivity

Figure 4-1: EAS-C Physical Network Connection

Visa POP AWS

© 2022 Visa. All Rights Reserved. Visa Confidential

Relevant Protocol Publications

Background information relating to socket implementation can be found in Berkeley ver.

Endpoint Communications Protocol Requirements

EAS-C Service Network Access Layer Internet Host-to-Host Endpoint Application

Message IEEE 802.3 (Ethernet) IPv4 TCP Endpoint-supplied socket

TCP/IP Layer Service

Application Layer Messaging Service (socket) with optional encryption (TLS)

File Services (FTPS)

Host-to-Host Layer TCP

The transmission control protocol (TCP) is used in packet- switching computer

Basic data transfer

Network Access Layer Ethernet (standard physical connector is RJ-45)

Data Encoding Requirements

Normal network path

Figure 4-2: After Geographical Failover