e-OSCAR 4.0 Planned Releases
Check out features and enhancements that we're planning on releasing in upcoming e-OSCAR System Releases.
NOTE: Delivery dates for these features are subject to change due to unforseen circumstances including development delays, feature priority modifications, quality assurance testing, or direction & guidance from regulators &/or Consumer Reporting Agencies. RELEASE CONTENTS ARE NOT FINALIZED UNTIL JUST PRIOR TO SCHEDULED RELEASES. FINAL INFORMATION ABOUT RELEASE CONTENT IS INCLUDED IN RELEASE NOTES.
e-OSCAR's General Release Timeline
Planned release contents updated as of: April 2, 2026
April 23, 2026 eo2026.04
-
(Services by e-OSCAR Schema Change) Creation of a new header "call-new-version-true" to leverage new schema during six-month backwards compatibility periods. For a period of six months after a schema change, if the new header is NOT included or if the version is FALSE, the previous version of the schema will automatically be used. This update will impact all API schema, including those leveraging payload encryption (ASL-86931 & ASL-86940)
-
(Services by e-OSCAR Schema Change) Addition of Notification ID field after "recordidentifier" and before "notificationType" to Block/DR Notification Services. Details to be published in SwaggerHub. We will provide backwards compatibility until October 16, 2026 (ASL-75567)​
-
(Services by e-OSCAR Schema Change) Update to Payload Encryption schema to remove "pwObjClass" in the payload response for all API endpoints with JSON. Details to be published in SwaggerHub. We will provide backwards compatibility until October 16, 2026 (ASL-75250)
-
(Services by e-OSCAR Schema Change) To improve the performance and efficiency of the Auth token process, e-OSCAR will now require Data Furnishers to include the most recent Auth token in the header of each new Auth token request via the auth/v2/authRequest endpoint. We will provide backwards compatibility until October 16, 2026 (ASL-85010)
May 28, 2026 eo2026.05
Various security and compliance-related efforts will be included in this release, including:
-
Improved secret management by moving Okta keys to Azure key vault
-
Reduced user-enumeration risk in authentication responses
-
Tightening of role-based permissions to strengthen access controls
​
Additionally, the following enhancements will be introduced:
-
Enablement of export to CSV of Operator Activity Report (ASL-69571)
-
Addition of API User ID in the "Performed By" section of Case History to clearly designate when a Dispute Response Notification, AUD Notification, or Block Notification has been ingested by API (ASL-88042)
June 20, 2026 eo2026.06
-
Pega platform upgrade (software currency)
-
​Update to e-OSCAR Validation Logic relating to values entered into ACDV Response "Amount Past Due" field when certain Account Status Codes are used (ASL-89596)
-
Updates to case management behaviors for AUD Notifications and DR Notifications, specifically when previously linked cases are unlinked (ASL-85632)
-
Removal of a deactivated Manager Operator from all user operators that have that user listed in their "Reports to" field on operator profiles (ASL-65167)
-
Minor bug remediations