Unit 03 · Chapter 1 · 10 min read

Underwrite the merchant business

Understand what is sold, when it is delivered, and who absorbs a failure.

A concert promoter collects cash today for a show six months away. A coffee shop collects cash for a drink handed over now. Both accept cards. Their risk can be very different because the promise stays open for very different lengths of time.

Start with the economic promise

Merchant underwriting evaluates the business and the exposure created by processing for it. Identify the product, customer, delivery timing, refund promise, and payment flow. A business registration proves that an entity exists; it does not prove the entity can fulfill its promises.

Write the model in one sentence: this merchant collects this amount from these customers for this service at this time. Then test the sentence against the website, contracts, financial records, and transaction plan. If the explanation changes across documents, resolve the discrepancy before deciding which controls are suitable.

A merchant application often describes a product category. Underwriting needs the actual promise made to customers. A business that sells a book for immediate shipment has a different exposure timeline from one that sells a course beginning in six months. Both may have the same monthly payment volume, but the second holds more unfulfilled obligations at a given moment.

Lantern therefore maps order creation, customer payment, fulfillment, refund rights, and merchant payout on one timeline. The distance between collecting money and delivering value is a source of exposure. The analysis then asks what resources remain if the merchant stops trading during that interval. Revenue growth can make the business look stronger while increasing the amount the platform may need to return to customers.

Start with the economic promise Start with the economic promise — the flow Follow the sequence. Identify refund and loss exposure. Offer Identify the promised product Delivery Locate when the obligation is met Failure Identify refund and loss exposure — Follow the sequence. Identify refund and loss exposure. Chapter sources · Open image

Start with the economic promise Start with the economic promise — the distinction These concepts answer different questions. Read each definition in the context of the section. Entity existence Business is registered Operating viability Business can fulfill its promises — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Start with the economic promise Promoter business model Fictional teaching record. Potential correlated exposure. Promoter business model Illustrative data; not a real customer record or a prescribed policy. Sale concert ticket Customer buys future access Delivery six months later Long open obligation Failure refund demand Potential correlated exposure Registration alone cannot establish fulfillment ability — Fictional teaching record. Potential correlated exposure. Chapter sources · Open image

Start with the economic promise Start with the economic promise — control and failure modes Registration alone cannot establish fulfillment ability. The branches show why alternative designs fail. Control design Underwrite the operating promise. Registration alone cannot establish fulfillment ability. Failure mode 1 Approve from the certificate only. It does not show the business model. avoid Failure mode 2 Treat all card merchants alike. Delivery and liability differ. avoid Failure mode 3 Ignore refund terms. They shape the open obligation. avoid — Registration alone cannot establish fulfillment ability. The branches show why alternative designs fail. Chapter sources · Open image

Map the payment and liability chain

Determine who is merchant of record, who receives settlement, who pays suppliers, and who bears refunds and chargebacks. A marketplace can present one brand while several entities perform these functions. Contracts and actual fund flows must agree.

Create a flow diagram with every legal entity and account boundary. Include refunds, reserves, and partner fees, not just incoming sales. A mismatch between the contractual seller and the visible checkout can confuse customers and complicate disputes. Escalate unclear models to the responsible legal and compliance owners before treating an account identifier as a complete answer.

Map the payment and liability chain Map the payment and liability chain — the flow Follow the sequence. Assign refunds and losses. Contract Identify the seller and obligations Funds Trace settlement and payouts Liability Assign refunds and losses — Follow the sequence. Assign refunds and losses. Chapter sources · Open image

Map the payment and liability chain — the distinction

Brand on screen: Customer-facing name
Merchant of record: Entity responsible in the payment arrangement

These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Map the payment and liability chain Marketplace chain Fictional teaching record. Must match the actual arrangement. Marketplace chain Illustrative data; not a real customer record or a prescribed policy. Checkout Lantern Visible platform Seller vendor-12 Underlying supplier Refund owner contract-defined Must match the actual arrangement Both are needed to understand responsibility — Fictional teaching record. Must match the actual arrangement. Chapter sources · Open image

Map the payment and liability chain — control and failure modes

Control design

Match agreements to actual fund flows. Both are needed to understand responsibility.

Failure mode 1avoid: Assume the logo owns every obligation. Branding does not determine all legal roles.
Failure mode 2avoid: Ignore supplier payouts. They can remove funds needed for refunds.
Failure mode 3avoid: Use only the bank account nickname. It does not establish the legal entity.

Both are needed to understand responsibility. The branches show why alternative designs fail. Chapter sources · Open image

Test fulfillment and concentration

Delivery exposure depends on how much business remains unfulfilled and how failures correlate. A merchant with many tickets for one event has concentration even if it has thousands of customers. Customer count is not the same as independent risk.

Estimate undelivered value by cohort and delivery date. Identify common suppliers, venues, platforms, and geographic events that can disrupt many orders together. Ask how the merchant would handle a cancellation or supplier failure. The point is to test a plausible loss path, not to forecast every possible disaster.

Test fulfillment and concentration Test fulfillment and concentration — the flow Follow the sequence. Estimate a correlated refund event. Cohort Group open customer promises Dependency Find shared failure causes Stress Estimate a correlated refund event — Follow the sequence. Estimate a correlated refund event. Chapter sources · Open image

Test fulfillment and concentration Test fulfillment and concentration — the distinction These concepts answer different questions. Read each definition in the context of the section. Many buyers Large customer count Diversified exposure Losses do not depend on one common event — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Event concentration

Fictional educational excerpt / Not for execution

Event concentration

Illustrative data; not a real customer record or a prescribed policy.

Customers4000
Many individual buyers
Venueone
Shared dependency
Open ticket value320000 USD
Correlated delivery obligation

Many customers can still share one failure cause

Fictional teaching record. Correlated delivery obligation. Chapter sources · Open image

Test fulfillment and concentration — control and failure modes

Control design

Measure shared delivery dependencies. Many customers can still share one failure cause.

Failure mode 1avoid: Use customer count as diversification proof. The venue can fail for everyone.
Failure mode 2avoid: Ignore future delivery dates. They determine the exposure window.
Failure mode 3avoid: Assume insurance always pays. Coverage and exclusions need evidence.

Many customers can still share one failure cause. The branches show why alternative designs fail. Chapter sources · Open image

Verify the story with proportional evidence

Evidence should test the important claims. Bank activity can support cash-flow claims, supplier agreements can support delivery plans, and complaint records can challenge the customer experience. No single document tells the whole story.

Use a documented discrepancy process. A missing document may be a simple administrative gap; a contradiction may be more serious. Record the question being resolved, acceptable evidence, and the decision owner. Avoid collecting a large pile of unrelated documents because it looks thorough. More data increases handling cost and privacy exposure without necessarily improving the decision.

Evidence is most useful when it tests a specific part of the business story. A sample of supplier records can support a claim about access to stock; fulfillment records can support a claim about delivery timing; financial information can support an estimate of repayment capacity. None proves the entire application. Record the claim, the evidence examined, its date, and the unresolved limitation. This makes a conditional approval understandable to the next reviewer and reduces the chance that a polished presentation substitutes for the operating facts.

Verify the story with proportional evidence Verify the story with proportional evidence — the flow Follow the sequence. Document the remaining uncertainty. Claim Name the fact that matters Evidence Choose a relevant independent source Resolve Document the remaining uncertainty — Follow the sequence. Document the remaining uncertainty. Chapter sources · Open image

Verify the story with proportional evidence Verify the story with proportional evidence — the distinction These concepts answer different questions. Read each definition in the context of the section. Missing evidence A claim remains unsupported Contradictory evidence Sources disagree on the same claim — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Verify the story with proportional evidence Fulfillment evidence Fictional teaching record. Stock receipt still unproven. Fulfillment evidence Illustrative data; not a real customer record or a prescribed policy. Claim stock already purchased Merchant statement Support supplier invoice Purchase evidence Gap delivery confirmation absent Stock receipt still unproven Each request should improve the decision — Fictional teaching record. Stock receipt still unproven. Chapter sources · Open image

Verify the story with proportional evidence Verify the story with proportional evidence — control and failure modes Each request should improve the decision. The branches show why alternative designs fail. Control design Request evidence tied to the unresolved claim. Each request should improve the decision. Failure mode 1 Collect unrelated personal records. They may add no useful support. avoid Failure mode 2 Treat absence as automatic fraud. Missing and false are different. avoid Failure mode 3 Ignore contradictions after one positive check. The conflict still needs resolution. avoid — Each request should improve the decision. The branches show why alternative designs fail. Chapter sources · Open image

Make approval conditional and reviewable

An underwriting result can approve a defined model with limits, reserve terms, review triggers, and prohibited changes. Document the scope so the merchant and operations teams know what was approved. A vague approved status is hard to enforce when the business changes.

Connect conditions to monitoring. If the approval assumes delivery within seven days, the team needs evidence when delivery extends to ninety days. Conditions should have an owner, data source, and response. Review restrictions for proportionality and customer impact. The goal is a sustainable relationship whose assumptions remain visible.

Make approval conditional and reviewable Make approval conditional and reviewable — the flow Follow the sequence. Revisit broken assumptions. Approve scope State the permitted model Set conditions Define measurable boundaries Monitor change Revisit broken assumptions — Follow the sequence. Revisit broken assumptions. Chapter sources · Open image

Make approval conditional and reviewable Make approval conditional and reviewable — the distinction These concepts answer different questions. Read each definition in the context of the section. One-time status Approved without operating context Conditional approval Defined model and review triggers — These concepts answer different questions. Read each definition in the context of the section. Chapter sources · Open image

Make approval conditional and reviewable Approval record Fictional teaching record. Responsible reviewer. Approval record Illustrative data; not a real customer record or a prescribed policy. Model immediate-delivery goods Approved scope Change trigger advance sales Different exposure Owner merchant underwriting Responsible reviewer Unobserved conditions cannot be enforced reliably — Fictional teaching record. Responsible reviewer. Chapter sources · Open image

Make approval conditional and reviewable Make approval conditional and reviewable — control and failure modes Unobserved conditions cannot be enforced reliably. The branches show why alternative designs fail. Control design Tie conditions to measurable monitoring. Unobserved conditions cannot be enforced reliably. Failure mode 1 Approve all future business models. The original evidence may not support them. avoid Failure mode 2 Set a limit without an owner. Breaches may receive no response. avoid Failure mode 3 Keep conditions hidden from operations. The team cannot apply them consistently. avoid — Unobserved conditions cannot be enforced reliably. The branches show why alternative designs fail. Chapter sources · Open image

Chapter connections

Continue with Credit risk and repayment capacity to follow the next part of the system. Use the glossary for terminology and risk mathematics for formulas and worked calculations.

Sources

Reviewed 2026-09-17