Encompass SDK Transitional Access Fees: What We Actually Know (July 2026)
Search for what it will cost to keep using the Encompass SDK after the deadline and you’ll find plenty of vendor pages quoting numbers — most of them describing a fee plan that no longer exists. Here is the current state of play, as of July 2026, with the superseded history clearly labeled.
What ICE has announced
Three facts define the post-deadline landscape:
- December 31, 2026 is the transition deadline for the Encompass SDK and legacy service ordering.
- From January 1, 2027, continued SDK use requires Transitional Access — which is approval-gated. You apply, ICE decides. It is not an automatic paid extension you can simply budget for.
- Transitional Access carries monthly fees that accrue from that date.
What has not been announced
Public per-lender pricing. As of this writing, ICE has not published a general rate card for Transitional Access. Any specific dollar figure you see quoted deserves scrutiny, because there’s a good chance it comes from the plan that was scrapped:
The superseded plan: in October 2024, ICE announced a six-month grace period after the then-current sunset date, followed by per-unit SDK fees (the widely quoted $0.50-per-unit figure) beginning May 2026. The August 2025 revision replaced that entire structure — new deadline, and approval-gated monthly-fee Transitional Access instead of per-unit pricing. Sites still quoting “May 2026” or “$0.50 per unit” are describing the old plan. (Full history in our verified timeline.)
The absence of a public rate card is itself information: pricing that runs through an approval process is pricing ICE controls case by case, and a fee structure designed to end usage tends to only go one direction over time.
The real cost isn’t the fee
Suppose your Transitional Access application is approved and the monthly number turns out to be tolerable. Look at what you’d be renting:
- A feature-frozen platform. The SDK stopped receiving new features on November 1, 2025. You’d be paying recurring fees for software in run-off maintenance.
- A shrinking ecosystem. Every vendor that completes its Partner Connect migration is one more integration whose legacy path can disappear regardless of what you pay ICE. Your fees keep your access alive; they don’t keep your vendors’ SDK-era endpoints alive.
- A deferred project at peak prices. The migration still has to happen. Deferring it past the deadline means doing it later with less available engineering capacity and a meter running — the cost drivers all move against you.
- Approval risk. Renewals of an approval-gated program are a decision ICE makes, not you. Building a 2027 operating plan on access you don’t control is the kind of risk that reads obvious in hindsight.
Transitional Access is a bridge for lenders who started too late — a way to keep production running while a migration finishes. As our timeline piece put it: it’s a bridge, not a strategy.
What to do if you’re reading this in mid-2026
With roughly six months left, the decision tree is short:
- Audit your SDK usage now. The fee exposure question is unanswerable until you know what you’re running.
- Migrate the production-critical components first. Anything that breaks loan production belongs on the API stack before December, component by component, running in parallel until outputs match.
- If the math says you won’t finish, apply early — with a plan. If some components realistically land in 2027, treat Transitional Access as scoped bridge coverage for a named list of items with migration dates attached. An application backed by a credible plan is also, presumably, an easier approval than “we’d like to keep everything indefinitely.”
The cheapest relationship with Transitional Access is never needing it. The second cheapest is needing it for two components for one quarter, on purpose.
A free assessment tells you exactly which components are exposed and what migrating each one costs — so the pay-fees-or-migrate math stops being hypothetical.