LendEasy/Docs
Get API keys
GuidesOverviewExample product portfolio

Example product portfolio

Four original, fictional contracts that carry the same balances and dates through every LendEasy calculation and servicing guide.

Lending documentation becomes useful when the numbers survive beyond a single page. These four contracts form a small test portfolio: each has a stable identity, unambiguous cash flows, and a specific teaching job. Later guides refer back to them by name.

All people, businesses, identifiers, dates, and amounts in this portfolio are fictional. Figures are educational contract examples, not offers of credit or legal advice.

Harbor Personal Loan

HARBOR · FICTIONAL EXAMPLE

Harbor Personal Loan

Fixed-rate installment loan

A regular monthly loan used to explain schedules, payments, payoff, APR, statements, and delinquency servicing.

Contract principal
$8,400.00
Nominal rate
13.25% fixed
Term
18 monthly payments
Prepaid origination fee
$252.00
Payment
$517.14
Disclosed APR
17.291%
Consummated and fundedAugust 12, 2026First payment dueSeptember 12, 2026Contract maturityFebruary 12, 2028

The fee is withheld from proceeds and classified as a finance charge, so the amount financed is $8,148.00 even though the contract principal is $8,400.00.

Harbor is the calculation workhorse. Its $252.00 prepaid finance charge makes the difference between principal, cash proceeds, and amount financed visible:

Measure Calculation Amount
Contract principal Amount the payment schedule amortizes $8,400.00
Cash delivered $8,400.00 − $252.00 withheld fee $8,148.00
Amount financed Principal − prepaid finance charge $8,148.00
Total of payments 18 × $517.14 $9,308.52
Finance charge $9,308.52 − $8,148.00 $1,160.52

The nominal contract rate is not the APR. The contract rate produces interest on the $8,400 balance; the APR measures the cost of the disclosed cash flows using the smaller $8,148 amount financed. See APR & disclosures for the full solve.

API examples across the guides reuse one set of Sandbox identities for Harbor. Lending Core IDs are numeric; customerId and loanRef serialize as strings ("412", "7204") in read models.

Record Sandbox ID
Customer — Maya Chen 412
Harbor loan 7204
Loan product 3
Payment instrument 704
First payment 9011
Latest statement 7719
Disbursement funding 5107

Juniper SplitPay

JUNIPER · FICTIONAL EXAMPLE

Juniper SplitPay

Promotional BNPL purchase

A no-cost retail plan used to explain down payments, merchant refunds, short schedules, and autopay.

Purchase price
$1,440.00
Checkout down payment
$240.00
Amount financed
$1,200.00
Finance charge
$0.00
Schedule
6 × $200.00 biweekly
Disclosed APR
0.000%
Purchase and down paymentAugust 21, 2026First installmentSeptember 4, 2026Final installmentNovember 13, 2026

The down payment is captured at checkout and is not part of the financed balance. Refund examples identify whether money returns to the borrower or reduces future installments.

Juniper separates checkout cash from financed cash. The $240 down payment completes immediately; the remaining $1,200 becomes the loan balance. It is the clearest example for:

  • down-payment settlement and reversal;
  • card-on-file autopay for a short biweekly schedule;
  • partial and full merchant refunds; and
  • a valid 0% APR result with no finance charge.

Cedar Community Loan

CEDAR · FICTIONAL EXAMPLE

Cedar Community Loan

Zero-interest relief loan

A simple principal-only contract used to make re-aging and re-amortization effects easy to see.

Principal
$3,960.00
Interest rate
0.00%
Original schedule
12 × $330.00 monthly
Origination fees
$0.00
Amount financed
$3,960.00
Disclosed APR
0.000%
FundedJanuary 8, 2027First payment dueFebruary 8, 2027Original maturityJanuary 8, 2028

Because every installment is principal-only, a servicing guide can show exactly where overdue principal moves without interest obscuring the before-and-after schedule.

Cedar deliberately removes interest from the picture. When two $330 installments become overdue, a schedule guide can show whether $660 stays past due, moves into remaining dates, or becomes a new set of installments. The arithmetic is visible at a glance, which makes Cedar useful for re-amortization, re-aging, and rescheduling.

Northstar Merchant Advance

NORTHSTAR · FICTIONAL EXAMPLE

Northstar Merchant Advance

Receivables purchase

A sales-based commercial obligation used to explain remittance, reconciliation, projected completion, and breach monitoring.

Purchase price
$48,000.00
Purchased receivables
$60,000.00
Purchased-amount multiple
1.25×
Remittance rate
12% of settled sales
Expected monthly remittance
$6,000.00
Projected duration
10 months
Agreement acceptedSeptember 3, 2026Purchase price fundedSeptember 4, 2026First sales report dueSeptember 5, 2026

The 10-month duration is a projection, not a fixed maturity promise. Actual remittance follows verified settled sales, with reconciliation and contract-specific minimums or protections applied separately.

Northstar is not an installment loan. LendEasy records a $48,000 purchase price and a $60,000 purchased amount, then applies the contract’s 12% remittance rate to verified settled sales. If Northstar reports $50,000 of settled sales in a month:

Monthly merchant remittance

verified settled sales × remittance rate
$50,000.00 × 12% = $6,000.00
Result$6,000.00

At that sales level, the projected duration is ten months. The projection changes when sales change; it is not silently converted into a fixed maturity date or a $6,000 payment promise. See Merchant advances.

Which example should I use?

If you are exploring… Start with Why
APR, fees, payoff, statements, daily interest Harbor It has interest and a prepaid finance charge.
Checkout financing, down payments, refunds Juniper Its purchase, down payment, and financed balance are distinct.
Hardship schedule changes Cedar Principal-only installments make every moved dollar obvious.
Sales-based commercial financing Northstar Remittance follows receivables rather than a fixed installment.
Cases, promises, contact controls Harbor The servicing snapshot reuses its ledger and schedule facts.

Consistency contract for this documentation

The examples follow four rules:

  1. A posted transaction changes the ledger; an intent or pending rail event does not.
  2. A schedule preview never mutates the loan.
  3. Dates are ISO 8601 in request payloads even when the prose spells them out; native loan responses render dates as [year, month, day] arrays, as described in Dates & timestamps.
  4. Rounding occurs at the contract-defined boundary. Worked totals reconcile to the cent; the production APR solver uses higher precision and rounds only the final disclosed rate.

When a guide needs facts outside this portfolio—an ACH return, bankruptcy filing, or military-service interval—it introduces a dated event against one of these contracts instead of inventing a fifth loan.

Unified search across guides, recipes & the API referenceEsc