Salesforce incident
Further investigation confirmed that SOAP API and SOAP Web Service calls to third-party payment gateways are failing, resulting in the current impact. We’re evaluating the best rollback approach while
Salesforce is currently experiencing a minor incident affecting POD253 and POD256 and 1 more component, which began 2h ago. The vendor's full update timeline is below.
Affected components
Update timeline
- identified May 14, 2026, 09:55 AM UTC
Degradation Started: featureServiceDisruption
- monitoring May 14, 2026, 10:06 AM UTC
We are investigating an issue impacting Commerce Cloud customers using a specific third-party payment service provider to process payments. As a result, the orders are not completing. We believe the trigger may be related to this recent release. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring May 14, 2026, 10:38 AM UTC
We’ve analyzed further and it’s confirmed that the recent release is the cause. A rollback of this release is being discussed as to whether it involves any further disruption to the service as this involves a complex configuration change. Also, the impact radius is broader than initially understood. We have updated the posting to reflect the additional PODs experiencing impact, and customers will receive communication. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring May 14, 2026, 11:18 AM UTC
Further investigation confirmed that SOAP API and SOAP Web Service calls to third-party payment gateways are failing, resulting in the current impact. We’re evaluating the best rollback approach while also exploring alternative mitigation options to minimize any additional risk. We'll provide an update in 30 minutes or sooner if additional information becomes available.