Pay run submission issues due to third-party certificate expiration

The issue affecting pay run access and submissions has been resolved.

The problem was caused by an expired SSL certificate on a third-party service, which led some browsers to block required resources. The certificate issue has been mitigated by our engineering team (removing the dependency), and PayEvo functionality has been restored.

If you are still encountering an issue, try a new browser session / clear cache or use a private browser session. This will resolve any locally cached pointers to the misbehaving CDN.

Workaround: While we work with the third-party provider to resolve the certificate issue, affected users may be able to access and submit pay runs by using a different browser (such as Chrome or Edge), clearing their browser cache, or connecting from a different network.

Why it may help: Browser SSL handling and cached certificate behavior differ, and some users may not encounter the block.

We are currently investigating an issue affecting some customers where payruns cannot be accessed or submitted.

This issue is caused by an expired SSL certificate on a third-party content delivery service used by PayEvo (ajax.aspnetcdn.com). As a result, some browsers are blocking required resources, which may prevent payruns from loading or submitting successfully.

Our team has identified the root cause and is working on mitigations while coordinating with the third-party provider.

We will provide further updates as more information becomes available.