Military service · LendEasy Docs

Active-duty status is checked against Baselayer on a daily cycle, with the full identifier resolved only at the request boundary — and a current no-hit never overrides credible evidence of past service.

Servicemember protections do not depend on the borrower mentioning their service, and the consequences of missing them are not proportionate to the difficulty of checking. A servicer that discovers active duty during litigation discovers it too late. Monitoring makes the check routine.

at rest

Held in the monitoring subject

Name, date of birth and address
The last four of the identifier
Enough to compare a result against, and not enough to perform the search

in flight only

Resolved at the request boundary

The full identifier, from the authorized identity source, at the moment the request is built
Passed straight into the outbound call
Held in no field, record or transaction afterwards
In no log line and no exception message, on either side

The search is refused rather than degraded. Without a full identifier and date of birth the request fails with a named input error instead of quietly falling back to a name-only search — because a name-only search against a common surname returns an answer that looks like the same answer and is not.

Where the answers come from

Every night the platform asks Baselayer whether a borrower was on active duty as of a stated date, and asks for the certificate that proves the answer.

The connection is credential-gated in the same way as the death-record check: the agreement is between the lender and Baselayer, and until those credentials are in place the connection cannot be activated.

Everything that comes back is kept — whether they were covered, the service dates, the branch, and the certificate itself. And the answer is recorded as what it actually is: a statement about service, not an approval of a benefit. If the evidence a decision needs is missing, the finding stays open rather than being resolved in either direction — which is the difference between “we checked and they do not qualify” and “we could not tell”.

The identifier never rests anywhere

This search requires a full tax identifier and a date of birth. That constraint is met without ever holding the identifier in the platform’s own working records.

A no-hit is not a denial

The most important rule on this page is about the direction of evidence. A current negative result means the search found nothing today. It does not mean the borrower never served, and it is not permitted to override credible historical evidence or a timely retroactive request.

That asymmetry is enforced rather than advised:

Requests and orders presented directly by a borrower enter the same lane as scheduled checks.
A no-hit updates monitoring freshness. It does not create a case, and it does not clear a previously verified fact.
Timeouts, stale sources, and partial results resolve to unknown, never to no match, and never release an existing protection.

From match to relief

A positive result is a STRONG match and opens a military-duty case at high priority into the military specialist queue. Verification resolves as service verified or not eligible, and the reviewer’s evidence-backed decision is recorded separately from the provider’s answer.

LifecycleService verification

SEARCHEDactive-duty status checked as of a stated date

MATCHEDcoverage, dates, branch, and certificate preserved

VERIFIEDspecialist confirms service and eligibility

RELIEF APPLIEDrate cap and protections applied to the account

MONITOREDservice period tracked to its end

VERIFIED→NOT ELIGIBLEmatch is not the borrower, or service does not qualify

MONITORED→RELEASEservice ends and the protection period expires

Release requires specific evidence and authority. A date passing is not release.

At intake the case pauses collections-scoped outreach and collections actions. Account-level relief is a separate, governed step: the SCRA rate cap is applied as an authorized servicing action with its own approval path and its own ledger effect, routed to payment operations. A verification task being marked done is not proof that a rate was changed — the account result is confirmed before the case can close.

Separate service periods stay separately distinguishable, so a borrower with two deployments has two service records rather than one merged interval.

Coverage status returned by a search is not a determination of benefit eligibility, and the protections a servicemember is owed are a matter of law and of your own counsel’s reading. Configure eligibility rules, relief mechanics, and release criteria with your legal team.