Pay.gov's Move to the Cloud - news and updates for agency testing and production
Pay.gov's move to the cloud is included in the 9.0 Release. For more information, visit the Agency Documentation site to view the 9.0 Release Notice.
Do you retrieve activity files and have questions on submitting the Access Request Worksheet (ARW)? Click the blue button below to continue to the form to see our FAQs.
Latest information for the production environment (Updated 7.2.2026)
Pay.gov's migration to the new cloud services began on Saturday, June 20, 2026, at 5:00 p.m. ET, and all services were unavailable for the duration of the cutover. The move to the cloud was successful, and Pay.gov services were fully restored on Sunday, June 21, 2026, around 6:15 a.m. ET.
If you are encountering any issues after the cloud migration, please contact Pay.gov Customer Support (pay.gov.clev@clev.frb.org or 800-624-1373) for assistance. When sending an email, include "Cloud Migration Issue: < your Pay.gov application name >" in the subject and include issue details in the body of the email.
Known Issues
- If you use Pay.gov's Web Services (Trusted Collection Service or Hosted Collection Pages) and receive the error code 4002 because the request originated from an IP not allowed, contact Pay.gov Customer Support (pay.gov.clev@clev.frb.org) to have it investigated. Please provide your tcs_app_id or Pay.gov application name.
- If you retrieve Pay.gov activity files and send the parameters in the body of the message, you must also set the Content-Type header. The header value must be application/x-www-form-urlencoded. Refer to the activity file guide for more information.
- Requests through the Pay.gov Web Services (qa.tcs.pay.gov) using ciphers for both TLSv1.2 and TLSv1.3 may experience timeouts and no response from Pay.gov. If possible, Pay.gov recommends using TLSv1.3 exclusively to resolve the issue.
This is a secure service provided by United States Department of the Treasury. The information you will enter will remain private. Please review our privacy policy for more information.