In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 03, 2026 - 16:30 EDT
Apr 03, 2026 - 16:30 EDT
Scheduled - As part of our ongoing Centinel Data Center Migration, and as previously communicated, we are preparing to complete the Production DNS cutover that will transition remaining traffic to the Visa Data Center endpoints.
To support a smooth transition and minimize disruption, we will continue to conduct controlled Production DNS “shock treatments" in April, followed by the final Production DNS cutover in early May. Please be advised that the dates referenced herein are subject to change and should any adjustments be required, we will provide timely notice.
Below is an overview of what to expect, key dates, and any actions required on your side.
What Will Occur and When:
April - May 2026 – Production DNS Shock Treatments
These short duration activities are designed to validate client readiness and identify any remaining configuration issues prior to final cutover.
Date: April 8, 2026
Activity: Production DNS Shock Treatment #1 at 14:00 UTC
Expected Duration ~30 minutes
Date: April 22, 2026
Activity: Production DNS Shock Treatment #2 at 14:00 UTC
Expected Duration ~60 minutes
During these windows, traffic will temporarily be redirected to the new Visa endpoints (IP addresses). Clients who have not yet updated their integrations may experience brief processing interruptions during the shock treatment windows.
FINAL Date: May 6, 2026 - Full Production DNS cutover
Potential Client Actions Post Cutover (if not already completed):
1. Update all backend endpoints to use the Visa proxy domain (.cardinaltrusted.com).
2. Update IP allowlists / firewall rules to trust the new Production IP ranges.
3. Confirm your integration properly consumes response URLs returned dynamically (for DDC, Lookup, and Authenticate flows), rather than hardcoding legacy URLs.
4. Merchant Reporting Migration: Set up your Enterprise Business Center (EBC) access. Please refer to this communication for additional details: https://cardinalcommercecorporation.statuspage.io/incidents/3zvgvsh958mx
Support and Contacts
If you have questions, need assistance validating your readiness, or experience any issues during these activities please reach out to:
- Primary Support: Please reach out to support@cardinalcommerce.com and open a ticket through the Cardinal Support portal (https://support.cardinalcommerce.com.
- Contact your Cardinal/Visa Client Success or Implementation Manager.
We appreciate your partnership as we complete this important milestone in the Centinel migration. Thank you for taking the necessary steps to ensure a smooth transition.
Please do not hesitate to contact support@cardinalcommerce.com or our support site (https://support.cardinalcommerce.com) if you have any questions or concerns.
Apr 3, 2026 16:30 - May 6, 2026 19:30 EDT
To support a smooth transition and minimize disruption, we will continue to conduct controlled Production DNS “shock treatments" in April, followed by the final Production DNS cutover in early May. Please be advised that the dates referenced herein are subject to change and should any adjustments be required, we will provide timely notice.
Below is an overview of what to expect, key dates, and any actions required on your side.
What Will Occur and When:
April - May 2026 – Production DNS Shock Treatments
These short duration activities are designed to validate client readiness and identify any remaining configuration issues prior to final cutover.
Date: April 8, 2026
Activity: Production DNS Shock Treatment #1 at 14:00 UTC
Expected Duration ~30 minutes
Date: April 22, 2026
Activity: Production DNS Shock Treatment #2 at 14:00 UTC
Expected Duration ~60 minutes
During these windows, traffic will temporarily be redirected to the new Visa endpoints (IP addresses). Clients who have not yet updated their integrations may experience brief processing interruptions during the shock treatment windows.
FINAL Date: May 6, 2026 - Full Production DNS cutover
Potential Client Actions Post Cutover (if not already completed):
1. Update all backend endpoints to use the Visa proxy domain (.cardinaltrusted.com).
2. Update IP allowlists / firewall rules to trust the new Production IP ranges.
3. Confirm your integration properly consumes response URLs returned dynamically (for DDC, Lookup, and Authenticate flows), rather than hardcoding legacy URLs.
4. Merchant Reporting Migration: Set up your Enterprise Business Center (EBC) access. Please refer to this communication for additional details: https://cardinalcommercecorporation.statuspage.io/incidents/3zvgvsh958mx
Support and Contacts
If you have questions, need assistance validating your readiness, or experience any issues during these activities please reach out to:
- Primary Support: Please reach out to support@cardinalcommerce.com and open a ticket through the Cardinal Support portal (https://support.cardinalcommerce.com.
- Contact your Cardinal/Visa Client Success or Implementation Manager.
We appreciate your partnership as we complete this important milestone in the Centinel migration. Thank you for taking the necessary steps to ensure a smooth transition.
Please do not hesitate to contact support@cardinalcommerce.com or our support site (https://support.cardinalcommerce.com) if you have any questions or concerns.
Apr 3, 2026 16:30 - May 6, 2026 19:30 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 01, 2026 - 15:45 EDT
Apr 01, 2026 - 15:45 EDT
Scheduled - Mastercard Directory Server Cutover Notification
Overview: As communicated in our February 6, 2025 Visa Business News (VBN-AI14914), VCAS Status Page, and VCAS Updates email, VCAS will be migrating to the Visa U.S. data centers. In February 2026, we successfully migrated 100% of our ACS URLs at the Visa Directory Server to the new Visa ACS URL within the Visa data centers. The new VCAS ACS URL and Method URL will start sending authentication requests through the Visa data center to the CardinalCommerce data center. Since authentication requests will still be processed at the Cardinal data center as they are today, there will be no change in your connection to VCAS. This first cutover will allow us to have more control, speed, flexibility, and reduce the risk of the actual data center migration for our customers later this year.
The next milestone of this migration is to update the Mastercard Directory Server on behalf of our customers with a new ACS URL and Method URL. We have been working closely with Mastercard to test the new ACS and Method URL as well as successfully pilot with a live customer.
Other Networks Update:
In regard to the other networks that will need to be updated with the new ACS URL and Method URL, please see the following updates. These are only applicable if you have a portfolio on VCAS for these networks:
Amex – Each customer will need to request their own ACS URL and Method URL with Amex
- Action - Please reach out to your CSM to work with the VCAS Team to obtain your URLs
JCB – Each customer will need to request their own ACS URL and Method URL with JCB
- Action - Please reach out to your CSM to work with the VCAS Team to obtain your URLs
Discover/Diners – Discover is working with us to mass update their Directory Server. We are currently looking for a pilot and will share more targeted updates as we have them
- No action at this time
ELO – ELO is working with us to mass update their Directory Server. We will share a more detailed and targeted update soon.
- No action at this time
UPI – UPI is working with us to mass update their Directory Server. We are currently looking for a pilot and will share more targeted updates as we have them
- No action at this time
EFTPOS – We are in discussion with EFTPOS to determine if any customer action is needed
- No action at this time
Mastercard DS Update Schedule:
The Mastercard Directory Server ACS URL and Method URL update is scheduled for April 28, 2026. The cutover will start at 14:00 GMT and is expected to be updated in waves throughout the day with completion prior to the end of day.
Client Impact:
There is no action you need to take for the Mastercard Directory Server update.
After the Mastercard Directory Server cutover, instead of your cardholder’s authentication requests going directly to the CardinalCommerce data center, they will first go through the Visa data center (see diagram below). There is no impact on how you are integrated with VCAS today. The adjustments will take place between the Mastercard Directory Server and VCAS, changing the way transactions are initially routed to VCAS.
We are notifying you, our customer, so you can mark the date and perform additional monitoring if you would like. The Mastercard and VCAS Teams will be monitoring each of these cutovers to ensure a smooth transition. We do not expect there to be any downtime during this change. If there are any concerns, we will use our status page to communicate.
The first cutover is pointing the Directory Server through the Visa data center with a new ACS URL and Method URL. Once we start the data center migration (July 1st, 2026), we will work with you individually to move your traffic from processing at the Cardinal data center to the Visa data center.
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.
The Visa.com Opt-in to VCAS updates 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.
Reminder: Two Possible Readiness Actions Based on Your VCAS Solution
As a reminder, based on your VCAS solution, there are two potential readiness actions you need to take prior to July 1st, 2026.
Trust IP Ranges:
VCAS users that have integrated Real-time Data Exchange (RDX) or Authentication Data Exchange (ADX) APIs will need to:
Trust the following IP subnet ranges (preferred):
o 198.241.177.0/24
o 198.241.169.0/24
If the full IP ranges cannot be trusted, the below IPs should be trusted (minimum requirement):
o 198.241.177.108
o 198.241.177.109
o 198.241.169.24
o 198.241.169.34
Continue to trust current IP addresses until the migration is complete
o 198.217.252.0/24
o 198.217.253.0/24
VCAS will be conducting tests throughout the Readiness and Migration Phases to ensure our customers are trusting the new IPs. Please do not block the IPs if you see connectivity trusts.
Request a Project
VCAS users that use file transfer services (Secure File Transfer Protocol [SFTP] Reporting, File Processor or Bulk Confirmed Marking will need to request a project using the Visa Support Hub (https://visasupporthub.visaonline.com) via Visa Access (formerly Visa Online) or their Customer Success Manager (CSM).
The objective of this project is to establish connectivity between the user’s system and the Visa File Exchange Service (VFES) prior to the migration start date.
Contact Information:
Visit the Visa Support Hub (https://visasupporthub.visaonline.com) to search for answers to your questions and create a case, if needed. Otherwise:
• 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
Apr 1, 2026 15:45 - Apr 29, 2026 11:45 EDT
Overview: As communicated in our February 6, 2025 Visa Business News (VBN-AI14914), VCAS Status Page, and VCAS Updates email, VCAS will be migrating to the Visa U.S. data centers. In February 2026, we successfully migrated 100% of our ACS URLs at the Visa Directory Server to the new Visa ACS URL within the Visa data centers. The new VCAS ACS URL and Method URL will start sending authentication requests through the Visa data center to the CardinalCommerce data center. Since authentication requests will still be processed at the Cardinal data center as they are today, there will be no change in your connection to VCAS. This first cutover will allow us to have more control, speed, flexibility, and reduce the risk of the actual data center migration for our customers later this year.
The next milestone of this migration is to update the Mastercard Directory Server on behalf of our customers with a new ACS URL and Method URL. We have been working closely with Mastercard to test the new ACS and Method URL as well as successfully pilot with a live customer.
Other Networks Update:
In regard to the other networks that will need to be updated with the new ACS URL and Method URL, please see the following updates. These are only applicable if you have a portfolio on VCAS for these networks:
Amex – Each customer will need to request their own ACS URL and Method URL with Amex
- Action - Please reach out to your CSM to work with the VCAS Team to obtain your URLs
JCB – Each customer will need to request their own ACS URL and Method URL with JCB
- Action - Please reach out to your CSM to work with the VCAS Team to obtain your URLs
Discover/Diners – Discover is working with us to mass update their Directory Server. We are currently looking for a pilot and will share more targeted updates as we have them
- No action at this time
ELO – ELO is working with us to mass update their Directory Server. We will share a more detailed and targeted update soon.
- No action at this time
UPI – UPI is working with us to mass update their Directory Server. We are currently looking for a pilot and will share more targeted updates as we have them
- No action at this time
EFTPOS – We are in discussion with EFTPOS to determine if any customer action is needed
- No action at this time
Mastercard DS Update Schedule:
The Mastercard Directory Server ACS URL and Method URL update is scheduled for April 28, 2026. The cutover will start at 14:00 GMT and is expected to be updated in waves throughout the day with completion prior to the end of day.
Client Impact:
There is no action you need to take for the Mastercard Directory Server update.
After the Mastercard Directory Server cutover, instead of your cardholder’s authentication requests going directly to the CardinalCommerce data center, they will first go through the Visa data center (see diagram below). There is no impact on how you are integrated with VCAS today. The adjustments will take place between the Mastercard Directory Server and VCAS, changing the way transactions are initially routed to VCAS.
We are notifying you, our customer, so you can mark the date and perform additional monitoring if you would like. The Mastercard and VCAS Teams will be monitoring each of these cutovers to ensure a smooth transition. We do not expect there to be any downtime during this change. If there are any concerns, we will use our status page to communicate.
The first cutover is pointing the Directory Server through the Visa data center with a new ACS URL and Method URL. Once we start the data center migration (July 1st, 2026), we will work with you individually to move your traffic from processing at the Cardinal data center to the Visa data center.
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.
The Visa.com Opt-in to VCAS updates 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.
Reminder: Two Possible Readiness Actions Based on Your VCAS Solution
As a reminder, based on your VCAS solution, there are two potential readiness actions you need to take prior to July 1st, 2026.
Trust IP Ranges:
VCAS users that have integrated Real-time Data Exchange (RDX) or Authentication Data Exchange (ADX) APIs will need to:
Trust the following IP subnet ranges (preferred):
o 198.241.177.0/24
o 198.241.169.0/24
If the full IP ranges cannot be trusted, the below IPs should be trusted (minimum requirement):
o 198.241.177.108
o 198.241.177.109
o 198.241.169.24
o 198.241.169.34
Continue to trust current IP addresses until the migration is complete
o 198.217.252.0/24
o 198.217.253.0/24
VCAS will be conducting tests throughout the Readiness and Migration Phases to ensure our customers are trusting the new IPs. Please do not block the IPs if you see connectivity trusts.
Request a Project
VCAS users that use file transfer services (Secure File Transfer Protocol [SFTP] Reporting, File Processor or Bulk Confirmed Marking will need to request a project using the Visa Support Hub (https://visasupporthub.visaonline.com) via Visa Access (formerly Visa Online) or their Customer Success Manager (CSM).
The objective of this project is to establish connectivity between the user’s system and the Visa File Exchange Service (VFES) prior to the migration start date.
Contact Information:
Visit the Visa Support Hub (https://visasupporthub.visaonline.com) to search for answers to your questions and create a case, if needed. Otherwise:
• 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
Apr 1, 2026 15:45 - Apr 29, 2026 11:45 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 30, 2026 - 11:00 EDT
Mar 30, 2026 - 11:00 EDT
Scheduled - As part of our ongoing platform updates, we are transitioning transaction reporting, user access management, and key management functions to the Enterprise Business Center (EBC). The EBC is Visa’s centralized portal where your team will be able to:
- View transaction reporting
- Manage users and permissions
- Securely generate and rotate API keys following production cutover
To ensure uninterrupted access to these capabilities, action is required from your team.
What to Do:
To get started, please open a Support ticket to establish access to the Enterprise Business Center (EBC). As part of this request, you will need to designate:
EBC Admin (Name/Email) – This individual will serve as your organization’s primary administrator for EBC and will be responsible for enrolling all subsequent users and assigning permissions.
Key Custodian (Name/Email) – This individual will manage API key generation and rotation for your organization within the EBC after production cutover.
If you currently use Cardinal’s Merchant Portal, completing this setup is important so your users can continue to access transaction reporting and manage keys without disruption.
Please do not hesitate to contact support@cardinalcommerce.com or our support site (https://support.cardinalcommerce.com) if you have any questions or concerns.
Mar 30, 2026 11:00 - May 6, 2026 08:00 EDT
- View transaction reporting
- Manage users and permissions
- Securely generate and rotate API keys following production cutover
To ensure uninterrupted access to these capabilities, action is required from your team.
What to Do:
To get started, please open a Support ticket to establish access to the Enterprise Business Center (EBC). As part of this request, you will need to designate:
EBC Admin (Name/Email) – This individual will serve as your organization’s primary administrator for EBC and will be responsible for enrolling all subsequent users and assigning permissions.
Key Custodian (Name/Email) – This individual will manage API key generation and rotation for your organization within the EBC after production cutover.
If you currently use Cardinal’s Merchant Portal, completing this setup is important so your users can continue to access transaction reporting and manage keys without disruption.
Please do not hesitate to contact support@cardinalcommerce.com or our support site (https://support.cardinalcommerce.com) if you have any questions or concerns.
Mar 30, 2026 11:00 - May 6, 2026 08:00 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 24, 2026 - 16:00 EST
Feb 24, 2026 - 16:00 EST
Scheduled - This notice is to inform you of an upcoming security certificate update for certain CardinalTrusted API endpoints.
This update includes a change to the certificate trust chain (root and intermediate certificates), not just a routine certificate renewal. As a result, some customers may need to take action to ensure uninterrupted connectivity.
What is changing:
• The TLS certificate chain used by select CardinalTrusted endpoints is being updated.
• The root and intermediate certificate authorities will change as part of this update.
What you may need to do:
• If your systems validate certificates using a custom trust store (for example, pinning or explicitly trusting certificate authorities), you may need to:
• Add the new root and intermediate certificates to your trust store before the change takes effect.
If you rely on standard operating system or JVM trust stores, no action is typically required.
What is not changing:
• There are no API behavior changes.
• There are no endpoint URL changes.
• This notice is separate from other certificate expiration or renewal messages you may have received.
Timing:/
The certificate update will be deployed in stages:
• Staging: Tuesday, March 31, 2026
• Production: Thursday, April 3, 2026 at 10:00 AM ET
Need help or unsure if you are impacted?
If you are uncertain whether this change affects your integration, or if you require clarification for your specific configuration, please open a Support ticket. Our team will work directly with you to ensure a smooth transition.
EXPIRING CERTIFICATES:
STAG:
Common Name (CN): cas.mtls.api.cardinaltrusted.com
Serial Number: 06:97:e8:7f:18:d5:12:c2:cf:e3:9b:99:3f:3e:75:43
Date of Replacement: 03/31/2026
Date of Expiry: 04/14/2026
Common Name (CN): cas.api.cardinaltrusted.com
Serial Name: 0c:1f:9b:be:08:ea:3e:4e:0c:d2:bf:98:58:f2:bd:a2
Date of Replacement: 03/31/2026
Date of Expiry: 04/14/2026
PROD:
Common Name (CN): mtls.api.cardinaltrusted.com
Serial Number: 05:62:c2:17:d1:c8:cf:cd:a0:ec:6c:e5:1b:ea:c8:d5
Date of Replacement: 04/03/2026
Date of Expiry: 04/14/2026
Common Name (CN): api.cardinaltrusted.com
Serial Number: 0b:22:a2:7f:2b:78:22:7f:a4:e0:9a:9d:29:99:6b:6d
Date of Replacement: 04/03/2026
Date of Expiry: 04/14/2026
Intermediate CA:
Common Name (CN): DigiCert SHA2 Secure Server CA
Serial Number: 02:74:2e:aa:17:ca:8e:21:c7:17:bb:1f:fc:fd:0c:a0
ROOT CA:
Common Name (CN): DigiCert Global Root CA
Serial Number: 08:3b:e0:56:90:42:46:b1:a1:75:6a:c9:59:91:c7:4a
NEW CERTIFICATES:
STAG:
Common Name (CN): cas.mtls.api.cardinaltrusted.com
Serial Number: 0e:b9:f0:c0:86:41:5d:c5:8e:0d:62:3f:27:ff:3d:27
Date of Replacement: 03/31/2026
Date of Expiry: 01/27/2027
Common Name (CN): cas.api.cardinaltrusted.com
Serial Number: 0e:f5:f4:6e:29:d4:06:92:38:02:c6:60:fd:86:69:8d
Date of Replacement: 03/31/2026
Date of Expiry: 01/26/2027
PROD:
Common Name (CN): mtls.api.cardinaltrusted.com
Serial Number: 0e:27:57:03:5c:8a:ae:96:c6:99:c9:6c:f2:80:a1:0e
Date of Replacement: 04/03/2026
Date of Expiry: 02/08/2027
Common Name (CN): api.cardinaltrusted.com
Serial Number: 0b:be:7b:52:df:89:52:c2:03:2e:56:d6:fd:79:9a:97
Date of Replacement: 04/03/2026
Date of Expiry: 02/08/2027
Intermediate CA:
Common Name (CN): DigiCert Global G2 TLS RSA SHA256 2020 CA1
Serial Number: 0c:f5:bd:06:2b:56:02:f4:7a:b8:50:2c:23:cc:f0:66
Root CA:
Common Name: DigiCert Global Root G2
Serial Number: 03:3a:f1:e6:a7:11:a9:a0:bb:28:64:b1:1d:09:fa:e5
Should you have any questions or concerns regarding this notice, please reach out to our support team at Support@cardinalcommerce.com.
Feb 24, 2026 16:00 - Apr 14, 2026 10:00 EDT
This update includes a change to the certificate trust chain (root and intermediate certificates), not just a routine certificate renewal. As a result, some customers may need to take action to ensure uninterrupted connectivity.
What is changing:
• The TLS certificate chain used by select CardinalTrusted endpoints is being updated.
• The root and intermediate certificate authorities will change as part of this update.
What you may need to do:
• If your systems validate certificates using a custom trust store (for example, pinning or explicitly trusting certificate authorities), you may need to:
• Add the new root and intermediate certificates to your trust store before the change takes effect.
If you rely on standard operating system or JVM trust stores, no action is typically required.
What is not changing:
• There are no API behavior changes.
• There are no endpoint URL changes.
• This notice is separate from other certificate expiration or renewal messages you may have received.
Timing:/
The certificate update will be deployed in stages:
• Staging: Tuesday, March 31, 2026
• Production: Thursday, April 3, 2026 at 10:00 AM ET
Need help or unsure if you are impacted?
If you are uncertain whether this change affects your integration, or if you require clarification for your specific configuration, please open a Support ticket. Our team will work directly with you to ensure a smooth transition.
EXPIRING CERTIFICATES:
STAG:
Common Name (CN): cas.mtls.api.cardinaltrusted.com
Serial Number: 06:97:e8:7f:18:d5:12:c2:cf:e3:9b:99:3f:3e:75:43
Date of Replacement: 03/31/2026
Date of Expiry: 04/14/2026
Common Name (CN): cas.api.cardinaltrusted.com
Serial Name: 0c:1f:9b:be:08:ea:3e:4e:0c:d2:bf:98:58:f2:bd:a2
Date of Replacement: 03/31/2026
Date of Expiry: 04/14/2026
PROD:
Common Name (CN): mtls.api.cardinaltrusted.com
Serial Number: 05:62:c2:17:d1:c8:cf:cd:a0:ec:6c:e5:1b:ea:c8:d5
Date of Replacement: 04/03/2026
Date of Expiry: 04/14/2026
Common Name (CN): api.cardinaltrusted.com
Serial Number: 0b:22:a2:7f:2b:78:22:7f:a4:e0:9a:9d:29:99:6b:6d
Date of Replacement: 04/03/2026
Date of Expiry: 04/14/2026
Intermediate CA:
Common Name (CN): DigiCert SHA2 Secure Server CA
Serial Number: 02:74:2e:aa:17:ca:8e:21:c7:17:bb:1f:fc:fd:0c:a0
ROOT CA:
Common Name (CN): DigiCert Global Root CA
Serial Number: 08:3b:e0:56:90:42:46:b1:a1:75:6a:c9:59:91:c7:4a
NEW CERTIFICATES:
STAG:
Common Name (CN): cas.mtls.api.cardinaltrusted.com
Serial Number: 0e:b9:f0:c0:86:41:5d:c5:8e:0d:62:3f:27:ff:3d:27
Date of Replacement: 03/31/2026
Date of Expiry: 01/27/2027
Common Name (CN): cas.api.cardinaltrusted.com
Serial Number: 0e:f5:f4:6e:29:d4:06:92:38:02:c6:60:fd:86:69:8d
Date of Replacement: 03/31/2026
Date of Expiry: 01/26/2027
PROD:
Common Name (CN): mtls.api.cardinaltrusted.com
Serial Number: 0e:27:57:03:5c:8a:ae:96:c6:99:c9:6c:f2:80:a1:0e
Date of Replacement: 04/03/2026
Date of Expiry: 02/08/2027
Common Name (CN): api.cardinaltrusted.com
Serial Number: 0b:be:7b:52:df:89:52:c2:03:2e:56:d6:fd:79:9a:97
Date of Replacement: 04/03/2026
Date of Expiry: 02/08/2027
Intermediate CA:
Common Name (CN): DigiCert Global G2 TLS RSA SHA256 2020 CA1
Serial Number: 0c:f5:bd:06:2b:56:02:f4:7a:b8:50:2c:23:cc:f0:66
Root CA:
Common Name: DigiCert Global Root G2
Serial Number: 03:3a:f1:e6:a7:11:a9:a0:bb:28:64:b1:1d:09:fa:e5
Should you have any questions or concerns regarding this notice, please reach out to our support team at Support@cardinalcommerce.com.
Feb 24, 2026 16:00 - Apr 14, 2026 10:00 EDT
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)
Under Maintenance
Cardinal API
Under Maintenance
Cardinal Hybrid API
Under Maintenance
Merchant Portal
Under Maintenance
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
Under Maintenance
Status Page
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Centinel Standard Network and Database Server Maintenance Apr 13, 2026 08:00 - Apr 16, 2026 20:00 EDT
CardinalCommerce will be performing database system improvements starting at 12:00 UTC on April 13, 2026, through 23:59 UTC on April 16, 2026. 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.
We appreciate your partnership as we continue improving the stability and security of our platform. If you have questions or would like support preparing for this change, our team is here to help.
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 Mar 30, 2026 - 09:35 EDT
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.
We appreciate your partnership as we continue improving the stability and security of our platform. If you have questions or would like support preparing for this change, our team is here to help.
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 Mar 30, 2026 - 09:35 EDT
VCAS/Issuer Services Standard Network and Database Server Maintenance Apr 16, 2026 08:00 - Apr 20, 2026 08:00 EDT
CardinalCommerce will be performing network and database system maintenance starting at 12:00 UTC on April 16, 2026, through 12:00 UTC on April 20, 2026.
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 Mar 30, 2026 - 09:48 EDT
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 Mar 30, 2026 - 09:48 EDT