Pause interest accrual

An interest pause is an effective-dated interval attached to a loan. Eligible days between startDate and endDate do not accrue contractual interest, while principal, payments, and prior accrual history are preserved.

Create a pause

Interest pauses have their own routes rather than a transaction command. A human call carries LendEasy-Case naming an open case when case management is enabled; without it the call is rejected before execution.

curl -X POST "$BASE/v1/loans/7204/interest-pauses" \
  -H "Authorization: Bearer $TOKEN" \
  -H "LendEasy-Tenant: demo-lender" \
  -H "LendEasy-Case: case_HBR_DISASTER_19" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: hbr-interest-pause-2027-08" \
  -d '{
    "startDate": "2027-08-01",
    "endDate": "2027-10-31",
    "dateFormat": "yyyy-MM-dd",
    "locale": "en"
  }'

{
  "resourceId": 12
}

GET /v1/loans/7204/interest-pauses lists the loan’s pause periods:

[
  { "id": 12, "startDate": "2027-08-01", "endDate": "2027-10-31" }
]

Adjust or remove

The interval is managed explicitly by id—variationId in the route:

• PUT /v1/loans/7204/interest-pauses/12 with a new startDate/endDate body moves the interval—for example extending relief to November 30. The response echoes the change: { "resourceId": 12, "changes": { "endDate": "2027-11-30" } }.
• DELETE /v1/loans/7204/interest-pauses/12 removes the interval with no request body.

Each mutation is governed: it carries the case header on human calls, writes a governance record, and can be parked by maker-checker for a second approver. The governance ledger—not a silent edit—is how a shortened or removed pause is explained later.

State is derived from dates

A pause has no stored status machine. It is scheduled while the business date is before startDate, active inside the interval, and completed after endDate—all derived from the stored dates. Ending relief early is a PUT with a nearer end date; cancelling a future pause is a DELETE before it starts.

Eligibility and overlap

The loan must be active, interest-bearing, and configured for interest pauses. Product policy limits interval length, backdating, and overlap; two overlapping pauses are rejected rather than double-applied—amend the existing interval instead.

A schedule modification interacts with pauses: applying a re-age, re-amortization, or reschedule while an interval is active can require the pause to be reviewed. Check GET /v1/loans/{loanId}/interest-pauses before and after schedule-changing commands.

Calculation and final amount

Any avoided-interest amount estimated before the interval ends is a projection, because future payments change daily balances. Final avoided interest is derived from the actual balance path when the interval completes. Keep the projection in the case; read the final effect from the loan’s transactions and schedule.

What a pause does not stop

Fees, penalties, autopay, statements, and delinquency continue unless their own policy or a servicing restriction changes them. If disaster assistance should also suppress fees or contact, apply those controls explicitly—restrictions, charge waivers—and link them to the same case.

Correction

A future interval can be deleted outright. Once accrual days have been processed, correct by amending the interval through PUT under governance; the platform does not quietly delete the interval and recreate interest. Every version of the interval remains explained by its governance records.