Is Check down?

We are aware of some payees not receiving direct deposits this morning and are actively investigating.

So far we've seen no evidence of failed transactions.  We are currently investigating what appears to be delays with specific receiving institutions.

We have not seen any evidence of failed transactions and have traced the delays to two specific receiving banks — UMB and The Bancorp Bank, N.A. Many consumer banking providers (e.g., Chime uses Bancorp; Fidelity uses UMB) sit on top of these banks, which is why impact appears spread across multiple employers and "banks". What we know: * We have reviewed the affected transactions and have found no evidence of failed or delayed processing on Check’s side. All reported payments were sent on time and are confirmed as completed by our payment processor. * The delays appear to be occurring after the funds reached the receiving banks and before they are made available in employee accounts. * Employees whose accounts are not serviced by UMB or The Bancorp Bank appear to be unaffected. We have seen third-party reports of similar delays affecting non-Check users, but neither receiving bank has published an official outage incident. At this time, affected employees should contact their bank directly for additional information about when the funds will be made available. We will continue monitoring the situation and will share additional updates as they become available.

UMB has confirmed they are experiencing settlement delays. They have not confirmed expected settlement timelines at this point.

Deposits to UMB accounts are beginning to post, with multiple confirmed cases. Chime has confirmed they are experiencing delays and will notify affected users once the deposits post.

We've received reports that impacted banks have been successfully posting deposits. If an employee has not received their funds at this point, we advise them to contact their bank. If there are outstanding deposit issues please reach out to Check's Support team with the impacted employee IDs.

We have identified an increased number of 5xx errors in Check API, which is also impacting Console usage. Investigation is in progress.

The system has recovered and is now operating normally. The issue was transient and related to an in-progress deployment. We are continuing to monitor the system closely and are conducting a root cause analysis to better understand the issue and prevent similar occurrences in the future.

Between approximately 19:11 and 19:23 UTC, a subset of Check API requests returned 5xx errors, which also intermittently impacted Console and Components. The errors occurred because a routine deployment introduced a new data value that application instances still running the previous version did not yet recognize; while the rollout was in progress, requests served by those older instances failed. Error rates returned to normal at 19:23 UTC once the deployment fully completed and all traffic was handled by the updated version. We are implementing safeguards, including updated data-migration and deployment practices plus additional automated review checks, to prevent similar issues in the future. No customer action is required, and the issue did not affect payment or payroll processing.

Delayed employee payments were identified this morning and are under active investigation. Many payments are processing, though arriving later than expected, and the total number of outstanding payments is actively decreasing. Work with our banking partner is ongoing, and we expect to work through the remainder of the day to ensure all affected payments are processed. Note: This only impacts payments that were funded and scheduled to land today. Please confirm any reported late payments are included in a payroll dated for today with no funding issues before escalating. No support outreach is needed to ensure payments are included in our efforts.

Our payment processor has identified the issue leading to delayed payments and is working on a fix. We will provide another update at 11:45am ET.

Our payment processor has identified the issue leading to delayed payments and is working on a fix. We will provide another update at 11:45am ET.

Our payment processor has developed and is deploying a fix. We will provide another update at 12:30pm ET.

Our payment processor has deployed a fix and we are working through the backlog of delayed payments.

We have rescheduled all delayed employee payments due today. We are actively working with our payments processor to ensure timely processing of these rescheduled instant payments. Most are completed, and a minority of those due today are still impacted. Funding payments have not been impacted.

All instant payments scheduled for today have been successfully processed. If we have not contacted you via Slack or email, all your customers' employees were paid today.

We are investigating an issue impacting payroll preview and approval. Requests to preview or approve payrolls are returning errors. This affects all payroll types. Other endpoints are not impacted. Our team has identified a database capacity issue as the root cause and is implementing a permanent fix. Estimated time to resolution: within 90 minutes.

Update: We have confirmed the root cause and are now applying a database fix. We are rolling the change through sandbox first before applying to production. Due to the size of the change, we are revising our estimated time to resolution to several hours. We will continue to provide updates as the fix progresses. Payroll preview and approval remain impacted across all payroll types in production. These endpoints will be unavailable in sandbox during application of our database fix. Other endpoints are not affected.

Update: The database fix has been successfully applied to our sandbox environment. The fix is now in progress on production. Estimated time to resolution: 60-90 minutes. We will update when complete. Payroll preview and approval remain impacted in production. Sandbox payroll operations have been restored.

Update: The database fix has been successfully applied to production. Payroll preview and approval are now operational and we are no longer seeing errors. We will continue monitoring to confirm stability before fully resolving this incident.

Resolved: The database fix has been fully applied and verified. Payroll preview and approval are operating normally across all environments. This incident has been resolved. Root cause: A database limit was reached that prevented payroll calculations from being processed. We have applied a permanent fix and are adding monitoring to prevent recurrence. We apologize for the disruption and thank you for your patience.

On the evening of Tuesday, May 26, 2026, a code change caused a subset of API key requests to incorrectly return 403 Forbidden. We detected the issue after a partner report, reverted the change, and restored service within approximately 5 hours. We are deeply sorry for the disruption. This explains what happened and what we are doing to prevent recurrence. Impact The issue was live from Tuesday, May 26 at 8:04 PM ET to Wednesday, May 27 at 1:27 AM ET, a window of 5 hours and 23 minutes. During that time, API requests that create or update resources (POST and PATCH) returned 403 Forbidden for a subset of partners: partners who had their API key associated with a Console user of the roles standard or cost owner. Most partners were not affected. Read traffic (GET) and the underlying data were not affected; no records were created, modified, or lost as a result of this bug, and approved payrolls and scheduled payments continued to process normally. Root cause We deployed an authorization refactoring on our write endpoints. The change contained a bug that caused the new check to incorrectly reject legitimate write requests for some partners if their API key was tied to a Console user with a role of either standard or cost owner. These unintended errors were mixed with legitimately rejected traffic, which affected our detection time. The change was reverted. No further action is required from partners, and any request that failed with a 403 during the window can be viewed in API Logs and safely retried. What we are doing differently First, we will reintroduce the change behind a safer rollout, re-landing the additional write-path authorization check with additional automated tests for this API key provisioning setup and in more incremental stages. Second, we will tighten our deploy guardrails by restricting changes affecting authentication or authorization to adjusted hours, along with implementing more robust post-deploy monitoring for faster response. If you believe you saw a related issue outside the window above, or have questions about this incident, please reach out to us and reference this note.