Resolved -
The issue affecting multiple services has now been fully resolved. Cybersource is conducting an internal review of the events to mitigate future occurrences.
Reported Start Time: 18 March 2026 at 14:23 GMT Reported End Time: 18 March 2026 at 14:35 GMT
Impact: Customers are now able to use the Cybersource service as normal.
Next Update: No further updates, issue resolved.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Update -
We are continuing to monitor for any further issues.
Mar 18, 18:09 UTC
Update -
While this incident is mitigated, there was additional impact not only to Payer Authentication, but other services called by merchants. Other services may have intermittently returned a 150 or 151 error indicating an ESYSTEM or ETIMEOUT error.
Teams are still investigating and gathering impact.
Impact: Some clients may have received an error during Payer Authentication enrollment. As a side effect to this issue a low number of other services called during this timeframe may have received errors as well.
Reported Start Time: 18 March 2026 at 14:23 GMT Reported End Time:18 March 2026 at 14:35 GMT
Next Update: As current status changes.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Monitoring -
Cybersource was aware of an issue that affected the Payer Authentication Service.
The issue affecting the Payer Authentication Service is mitigated. We are monitoring closely to ensure the issue is resolved.
Impact: Some clients may have received an error during Payer Authentication enrollment. The issue has been mitigated and customers are now able to use the Payer Authentication Service as normal.
Reported Start Time: 18 March 2026 at 14:23 GMT Reported End Time:18 March 2026 at 14:35 GMT
Next Update: As current status changes.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Resolved -
This incident has been resolved.
Mar 17, 18:20 UTC
Update -
Our ecosystem partner resolved this on their end and helped process settlement for all impacted transactions. Cybersource teams will work with our partner to synchronize reporting details to match these updates.
Impact: Customers may experience funding settlement issues.
Reported Start Time: 03 March 2026, 21:30 GMT
Next Update: As current status changes.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns. Cybersource Support Center
Incident #: INC24450589
Mar 17, 17:27 UTC
Monitoring -
We have received confirmation from our ecosystem partner that they have mitigated this issue. No further impact has been observed. We are actively preparing to proceed with downstream settlement processing.
We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is resolved.
Impact: Customers may experience funding settlement issues.
Reported Start Time: 03 March 2026, 21:30 GMT
Next Update: As current status changes.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns. Cybersource Support Center
Incident #: INC24450589
Mar 6, 11:18 UTC
Update -
We have identified the issue impacting settlement and batching for FDI Global and FDC Compass for a small number of Mastercard transactions. An ecosystem partner experienced an internal issue which caused the settlement errors. Our partner continues working to implement a mitigation. Upon confirmation of mitigation, we will proceed with downstream settlement processing.
We regret any inconvenience this may cause for our customers.
Impact: Customers may experience funding settlement issues.
Reported Start Time: 3 March 2026
Next Update: As current status changes
We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is mitigated.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Identified -
We have identified the issue impacting settlement and batching for FDI Global for a small number of Mastercard transactions. An ecosystem partner had experienced an internal issue which caused the settlement errors and is working to implement a mitigation.
Upon confirmation that the issue has been mitigated by the partner, we will proceed with downstream settlement processing.
Impact: Customers may experience funding settlement issues.
Reported Start Time: 3 March 2026
Next Update: As current status changes
We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is mitigated.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Update -
We continue to investigate the issue impacting settlement and batching for FDI Global for a small number of Mastercard transactions, and we appreciate your continued patience.
Impact: Customers may experience funding settlement issues.
Reported Start Time: 3 March 2026
Next Update: Within 60 minutes
We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is mitigated.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Investigating -
Cybersource is aware of an issue impacting settlement and batching for FDI Global for a small number of Mastercard transactions. As a result, merchants may experience transaction declines with an “Invalid Cardholder Account Number” error.
We are investigating the cause and working urgently to resolve the issue.
Impact: Customers may experience funding settlement issues.
Reported Start Time: 3 March 2026
Next Update: Within 60 minutes
We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is mitigated. Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Resolved -
The issue affecting the REST API Service has now been fully resolved. Cybersource is conducting an internal review of the events to mitigate future occurrences.
Reported Start Time:13 March 2026 Reported End Time: 16 March 2026 at ~17:47 GMT
Impact: Customers are now able to use the REST API Service as normal.
Next Update: No further updates, issue resolved.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Monitoring -
A fix has been implemented and is currently being rolled out through production. We are monitoring closely as the implementation completes.
Impact: Certain merchants may experience issues with REST API when submitting an IPv6 IP address in the "deviceInformation.ipAddress" field. Merchants may receive field validation errors resulting transaction failures.
As a workaround, merchants can submit transactions using IPv4 addresses only or leaving the "deviceInformation.ipAddress" field blank until resolved.
Reported Start Time: 13 March 2026
Next Update: As current status changes.
We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is mitigated.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Update -
We continue to investigate the cause and working urgently to resolve the issue.
Impact: Certain merchants may experience issues with REST API when submitting an IPv6 IP address in the "deviceInformation.ipAddress" field. Merchants may receive field validation errors resulting transaction failures.
As a workaround, merchants can submit transactions using IPv4 addresses only or leaving the "deviceInformation.ipAddress" field blank until resolved.
Reported Start Time: 13 March 2026
Next Update: As current status changes.
We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is mitigated.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.
Investigating -
Cybersource is aware of an issue that is currently affecting some merchants using REST API. We are investigating the cause and working urgently to resolve the issue.
Impact: Certain merchants may experience issues with REST API when submitting an IPv6 IP address in the "deviceInformation.ipAddress" field. Merchants may receive field validation errors resulting transaction failures.
As a workaround, merchants can submit transactions using IPv4 addresses only or leaving the "deviceInformation.ipAddress" field blank until resolved.
Reported Start Time: 13 March 2026
Next Update: Within 60 minutes.
We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is mitigated.
Please do not hesitate to contact the Cybersource support team if you have any questions or concerns.