All Systems Operational

About This Site

Welcome to the CardinalCommerce status page. We use this page to communicate any issues with our products including planned and unplanned outages.

Securing your transactions is our top priority.

Cardinal Consumer Authentication (3DS) ? Operational
Cardinal API ? Operational
Cardinal Hybrid API ? Operational
Merchant Portal ? Operational
VCAS Issuer Services ? Operational
The Real-time Data Exchange (RDX) ? Operational
File Processor ? Operational
Authentication Data Exchange (ADX) ? Operational
Reporting Extract ? Operational
VCAS Portal ? Operational
PayPal Operational
Status Page ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Centinel and Max Standard Network and Database Server Maintenance Jul 7, 2025 08:00 - Jul 10, 2025 20:00 EDT

CardinalCommerce will be performing database system improvements starting at 12:00 UTC on July 7, 2025, through 23:59 UTC on July 10, 2025. During this time, we will apply the most recent network and database patches as well as targeted security enhancements to prevent new exploits from being used against our systems.

We perform monitoring and testing of the updates during Cardinal business hours, while we are fully staffed from a support and network operations standpoint.

This is being performed in a high availability mode and should have no impact to transaction processing. While no transaction impact is anticipated during this maintenance you may experience a few periods of network latency.

Please do not hesitate to contact support@cardinalcommerce.com or our support site (https://support.cardinalcommerce.com) if you have any questions or concerns.
Posted on Jun 24, 2025 - 17:23 EDT

VCAS/Issuer Services Standard Network and Database Server Maintenance Jul 10, 2025 08:00 - Jul 14, 2025 08:00 EDT

CardinalCommerce will be performing network and database system maintenance starting at 12:00 UTC on July 10, 2025 through 12:00 UTC on July 14, 2025.

During this window we will apply the most recent network and database updates for optimal performance and to prevent new exploits from being used against our VCAS systems.

This is being performed in high availability mode and should have no impact to transaction processing. While no transaction impact is anticipated during this maintenance you may experience a few periods of network latency. During this time, we will be fully staffed from a support and network operations standpoint to perform monitoring and testing.

Please do not hesitate to contact your Local VISA support if you have any questions or concerns.

VISA Local Support Channels by Region

Global and LAC - VISA Support Hub Portal (https://visasupporthub.visaonline.com)
AP - Isupport@visa.com
CEMEA - csupport@visa.com
EU - customersupport@visa.com
NA - esupport@visa.com
Posted on Jun 24, 2025 - 17:25 EDT
Jul 5, 2025

No incidents reported today.

Jul 4, 2025

No incidents reported.

Jul 3, 2025

No incidents reported.

Jul 2, 2025

No incidents reported.

Jul 1, 2025
Visa Consumer Authentication Service (VCAS) Data Center Migration- Action Required!
Completed - The scheduled maintenance has been completed.
Jul 1, 09:30 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 6, 11:30 EST
Scheduled - The Visa Consumer Authentication Service (VCAS) will be migrated to Visa data centers in a phased approach beginning 1 July 2025 and ending 31 March 2026. VCAS users will need to take specific actions to complete the migration depending on the VCAS features and functionality they use today.

Visa will begin a phased migration of VCAS to Visa data centers beginning 1 July 2025 and ending 31 March 2026 to improve security, performance and resiliency by maximizing Visa's global scale and infrastructure.
The specific actions needed to complete the migration will depend on which VCAS features and functionality are being used today. See the Client Impact and Required Actions section below for a summary of the current actions required based on the VCAS solution being used.

Key Dates
• 1 July 2025: Start of phased VCAS customer migration
• 31 March 2026: End of phased VCAS customer migration

VCAS Background

Visa acquired CardinalCommerce in 2017, and since then has built VCAS into a robust, state-of-the-art authentication solution.

The VCAS team is committed to handling the majority of the requirements in order to reduce the effort and resources needed for VCAS users to complete the migration. Visa will provide additional details in future communications on the migration plan and how VCAS users will be migrated in the most efficient and effective way possible.

Client Impact and Required Actions:

Trust new IP Ranges
Continue to trust current IP addresses until the migration is complete

VCAS users that have integrated Real-time Data Exchange (RDX) or Authentication Data Exchange (ADX) APIs will need to trust new IP ranges. Please visit the Visa Support Hub (https://visasupporthub.visaonline.com/) and reference the Knowledge Article titled "VCAS Customer Data Center Migration" for the IP's and additional information.

Request a Project

VCAS users that utilize file transfer services (Secure File Transfer Protocol [SFTP] Reporting, File Processor or Bulk Confirmed Marking) will need to open a case using the Visa Support Hub under VCAS (https://visasupporthub.visaonline.com) via Visa Access (formerly Visa Online) or engage their Customer Success Manager (CSM) by 1 July 2025.

The objective of this project is to establish connectivity between the user’s system and the Visa File Exchange Service (VFES). A secondary project will be needed to complete the actual data center migration; this secondary project will include testing the files before sending traffic to the Visa data center. Prior to requesting a project, users should have the information listed below, as it is required to create a new Visa Access ID for VFES.

Account Owner (the person responsible for file transfer services in the user’s organization) and Manager (backup contact):

o Organization Name
o Visa Business Identification (BID) number
o Full Name (file delivery contact)
o Job Title
o Email Address
o Business Address
o Phone Number

Secure Shell (SSH) Keys:

o VFES requires SSH keys for authentication and securing communication.
o If VCAS currently hosts the SFTP folders, users will need to create a public and private key pair per environment (Staging and Production).
o If you currently host the SFTP folders, Visa will provide the SSH public key during your project.

Sign Up for Future Data Center Migration Updates
Visa will use the following channels to communicate data center migration updates, and strongly recommends VCAS users subscribe to ensure receipt of migration-related communications and notifications.

VCAS Status Page / CardinalCommerce Status (https://cardinalcommercecorporation.statuspage.io): This status page is primarily used to communicate planned and unplanned events that may impact operational status.

Subscribe for updates to one or more of the following based on your VCAS solution:
-VCAS Issuer Services
-The Real-time Data Exchange (RDX)
-File Processor
-Authentication Data Exchange (ADX)
-Reporting Extract
-VCAS Portal

The visa.com Opt-in to VCAS updates today page (https://globalclient.visa.com/Opt-inToVCASUpdatesToday). This is primarily for new VCAS product information, updates and educational opportunities. Visa will also use this channel to communicate data center migration updates via email.

Please do not hesitate to contact your Local VISA support if you have any questions or concerns.

VISA Local Support Channels by Region

Global and LAC - VISA Support Hub Portal (https://visasupporthub.visaonline.com)
AP - Isupport@visa.com
CEMEA - csupport@visa.com
EU - customersupport@visa.com
NA - esupport@visa.com
Feb 6, 11:27 EST
Jun 30, 2025

No incidents reported.

Jun 29, 2025

No incidents reported.

Jun 28, 2025

No incidents reported.

Jun 27, 2025

No incidents reported.

Jun 26, 2025

No incidents reported.

Jun 25, 2025

No incidents reported.

Jun 24, 2025

No incidents reported.

Jun 23, 2025

No incidents reported.

Jun 22, 2025

No incidents reported.

Jun 21, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage