ML Consumer/Opening - Authorize.net Funding Errors

Update timeline

1. investigating Jul 23, 2026, 02:51 PM UTC

   We are currently investigating reports of Authorize.net funding errors. Clients are reporting that they receive Failed to fund: Response is nothing when trying to process DA app funding.

2. identified Jul 23, 2026, 03:47 PM UTC

   We are actively working with our cloud provider to restore network connectivity to parts of our service.

3. identified Jul 23, 2026, 04:14 PM UTC

   We are continuing to investigate reports of Authorize.net Funding Errors affecting Meridianlink Opening. Our teams remain actively engaged and are working to identify the underlying cause and fully understand the scope of impact. At this time, there is no change in status, but investigation efforts with our cloud provider remain a high priority. We will continue to share updates as additional information becomes available.

4. identified Jul 23, 2026, 04:29 PM UTC

   Microsoft is investigating an issue affecting connectivity to Azure services for a subset of customers in the West US region. Impacted customers may experience intermittent issues when accessing Azure services. We will provide more information as it becomes available. If you want to be notified about emerging issues where you haven't yet been confirmed as an impacted customer, you can consume the RSS feed from the Azure Status Page: https://azure.status.microsoft/en-us/status

5. identified Jul 23, 2026, 05:28 PM UTC

   We're currently experiencing a service disruption caused by an issue with Microsoft's infrastructure. Microsoft has identified the potential source of the problem and is actively working to resolve it by rerouting traffic to healthy systems and monitoring recovery in real time. They will continue to evaluate the effectiveness of mitigation, assess customer impact, and investigate contributing factors, and will provide additional information as soon as it becomes available. We're staying close to Microsoft's response to bring services back to full availability as quickly as possible. We'll share updates here as new information becomes available.

6. monitoring Jul 23, 2026, 09:25 PM UTC

   This issue has been resolved. Our engineering team identified the root cause as a validation error introduced by a recent code change, which was corrected. Functionality with Authorize.net has been fully restored. We apologize for the disruption and appreciate your patience while we worked through this.

7. resolved Jul 23, 2026, 10:35 PM UTC

   This incident has been resolved.