Institutional Lender
The Financial Conduct Authority (FCA)-authorised firm that funds confirmed receivables. Browser Single-Page Application (SPA) for treasury work, Representational State Transfer (REST) Application Programming Interface (API) for tech-led lenders who want to underwrite at scale. The lender is the only party who sees both the seller's economics and the on-chain token references — gated by their own authorisation status.
Flow map
| Step | What the lender sees | Channel | State event |
|---|---|---|---|
| L1 | Sign up, choose role | Browser | SUBJECT_CREATED |
| L2 | Onboarding (Know Your Business (KYB) on the firm, named directors, FCA permissions, designated settlement account, optional stablecoin opt-in) | Browser | ONBOARDING_SUBMITTED |
| L3 | Gates 1–3 + FCA permissions confirmed | RISK_PASSED + FCA_VERIFIED | |
| L4 | Welcome — concentration limits set, marketplace access | Email + dashboard | SUBJECT_ACTIVE |
| F1 | Discover · marketplace listing | Browser + API | — |
| F2 | Underwrite · price & pre-fund check | Browser + API | — |
| F3 | Fund · explicit approval, transfer initiated | Browser + API | INVOICE_FUNDED |
| F4 | Disbursement reconciled | Email + dashboard | ADVANCE_DISBURSED |
| F5 | Track · portfolio + days-to-maturity | Browser + API + webhook | — |
| F6 | Receive settlement · Great British Pound (GBP) fiat or USD Coin (USDC) | Browser + email | INVOICE_SETTLED |
Onboarding · L1–L4
3–10 business days end to end. Bottleneck is the FCA register check (continuous, but takes 24h to surface a register-status change) and the designated settlement account setup (banking-side onboarding outside FinToken X).
/compliance/onboarding/lender. Heavier than seller — captures FCA reference, permissions scope, designated settlement account, named authorised representatives, optional USDC opt-in.Pennine Asset Management LLP
Step 4 of 6 — Designated settlement account & concentration appetite
Designated settlement account
Disbursements leave from this account; obligor remittances land in this account; we never custody these funds.
Concentration appetite
Settlement currency
Faster Payments / Bankers' Automated Clearing Services (Bacs) into your Lloyds account.
Settled on the FinToken X Network. Requires Chainalysis wallet screening on your treasury wallet.
Application in review
FX-APP-77298 · Submitted 12 May 2026
Per-receivable · F1–F6
For every confirmed invoice listed on the marketplace, the lender's flow has six steps. F1 and F2 are discovery + underwrite; F3 is the explicit funding click; F4–F6 are disbursement, tracking, settlement.
FX-INV-23A4F appears the moment Tom Whitfield confirms it on the buyer side.Receivables marketplace
Confirmed receivables that fit your appetite. Refreshes live as new ones arrive.
Risk grade is FinToken X's internal model output; the lender can also pull underlying inputs (buyer credit score, originator tenure, vision-pass artefacts) into their own model via the API — see F2 below. "Risk" column is allowed here per money-control rule 7 because the lender owns the credit risk.
FX-INV-23A4F. Caroline sees originator history, obligor history, the OCR-extracted invoice fields, the buyer-confirmation evidence, and a price calculator.FX-INV-23A4F · £10,000.00 · Northwind Retail plc
Originator: Coppergate Joinery Ltd · Tenor 60d · Maturity 21 Jul 2026
Originator · Coppergate Joinery Ltd
14 invoices financed · £142,420 cumulative · 0 disputes · 12 months on FinToken X · LOW risk
Standard Industrial Classification (SIC) 4332 · Yorkshire · 18 staff · Companies House (CH) 07452983
Obligor · Northwind Retail plc
142 invoices confirmed · £487,210 cumulative · 3 disputes (resolved) · 18 months on FinToken X
FTSE 250 · D&B 9A1 · CH 04382671
Buyer confirmation evidence
Confirmed by tom.whitfield@northwind.co.uk at 14:21 on 22 May 2026 from IP 92.40.171.•••. Page hash 0x7a2c…b811.
Pricing
FXR-INV-23A4F) — and on the API surface, the on-chain contract address + tokenId.
What the lender does NOT see (per money-control rule 1): the seller's bank account number — they disburse to a FinToken X bankable virtual account that we route to the seller. The lender treats that virtual account as if it were the seller's; they never need to know the underlying.
Pricing override: within the lender's pre-set band only. A lender can offer better than indicative pricing to win the deal; they cannot price above their stated band without a re-onboarding step.
Fund FX-INV-23A4F
Final review before disbursement
/settings/security./settings/security. When on, F3 routes to a "pending second approver" state visible at /payments?status=pending_approval; a second authorised representative must sign off before disbursement fires. State: on disburse, the receivable record gains funded_by=, funded_at=…, discount_rate=2.4%, net_advance=9760.00 ; the token is transferred from the FinToken X mint wallet to the lender's wallet via an Ethereum Request for Comments 3643 (ERC-3643) transfer (which itself runs through the compliance modules).
Disbursement acknowledged ✓
Caroline,
Your disbursement of £9,760.00 against receivable FX-INV-23A4F has been received by FinToken X collections and routed to the originator. The receivable token FXR-INV-23A4F has been transferred to your wallet.
Posted to your FinToken X ledger. Track maturity, days to settlement, and accrued income at your portfolio.
Receivables register
Recent postings · Designated settlement account
Receivable settled ✓
Caroline,
The obligor has paid in full. £10,000.00 has been remitted to your designated settlement account at Lloyds Bank (•••• 7719). Receivable FX-INV-23A4F is now closed and the token FXR-INV-23A4F has been burned on the FinToken X Network.
Posted to your FinToken X ledger.
API surface
Tech-led lenders use REST + webhooks instead of (or alongside) the browser. Same business rules, same audit trail, same gates. Authentication is mutual Transport Layer Security (mTLS) plus a per-firm API key created at /lender/api-keys.
List the marketplace
// Headers Authorization: Bearer fxk_live_4Z… FX-Idempotency-Key: 9c2f4ab1-… // 200 OK { "data": [ { "reference": "FX-INV-23A4F", "token_reference": "FXR-INV-23A4F", "originator": { "name": "Coppergate Joinery Ltd", "ch_number": "07452983", "history": { "financed": 14, "disputes": 0 } }, "obligor": { "name": "Northwind Retail plc", "ch_number": "04382671", "credit_grade": "9A1" }, "face_value_pence": 1000000, "currency": "GBP", "tenor_days": 60, "maturity": "2026-07-21", "indicative_discount_bps": 240, "risk_grade": "LOW", "buyer_confirmation": { "confirmed_at": "2026-05-22T14:21:08Z", "page_hash": "0x7a2c…b811" }, "chain": { "contract": "0xfx3643…a1f", "token_id": 23147 } } ], "page": { "cursor": "eyJjIjo…", "has_more": true } }
Fund a receivable
// Request { "receivable_reference": "FX-INV-23A4F", "discount_bps": 240, "net_advance_pence": 976000, "two_eyes_approver_subject_id": "sub_pen_g1k…" } // 201 Created { "id": "pay_5fz1qa…", "receivable_reference": "FX-INV-23A4F", "status": "DISBURSING", "disbursement": { "rail": "FPS", "expected_completion": "2026-05-22T14:24:00Z" }, "chain_transfer": { "tx": "0x…queued", "status": "PENDING" } }
FX-Idempotency-Key. We replay-suppress identical requests for 24h. Two-eyes: if your firm has it on, omitting the approver subject ID returns 409 PENDING_APPROVAL; the second representative completes the call from their session.
Webhook · receivable settled
// Headers FX-Event: receivable.settled FX-Signature: t=1721555640,v1=… // Body { "id": "evt_h7vf…", "event": "receivable.settled", "data": { "receivable_reference": "FX-INV-23A4F", "settled_at": "2026-07-21T11:14:23Z", "face_value_pence": 1000000, "discount_realised_pence": 24000, "settlement_rail": "FPS", "settlement_reference": "NW-2107-FXC", "token_burn_tx": "0xa12c…ff04" } }
{timestamp}.{body} with the per-firm webhook secret. We retry with exponential backoff up to 24h on non-2xx responses; failed deliveries surface in /webhooks/logs visible to the lender's API admin.
Where it can go wrong
| Branch | What the lender sees | State | Recovery |
|---|---|---|---|
| Concentration breach attempted | F2 button disabled; tooltip: "would push your Northwind exposure to 102% of cap (£5.10m / £5.00m)". | — | Adjust the cap at /settings or wait for an existing receivable to settle. |
| FCA permission revoked (Gate 4) | Marketplace access frozen; portfolio remains visible read-only. | SUBJECT_FROZEN_FCA | Manual MLRO intervention; new disbursements blocked until FCA register confirms reinstatement. |
| Disbursement bounces back from FinToken X | Email + portfolio entry: "We couldn't apply your disbursement. Please re-initiate from /payments/ | DISBURSEMENT_FAILED | FinToken X ops re-routes; lender notified within 2 hours. |
| Obligor pays late · 5 BD past due | Receivable shifts to PAST_DUE in portfolio. FinToken X collections team kicks in. | PAST_DUE | FinToken X chases; lender's principal continues to accrue per the receivable's contract. |
| Obligor pays late · 30 BD past due | DEFAULT in portfolio. FinToken X invokes the platform's recourse pool (sandbox-phase only — see backend). | DEFAULT | Recovery handled per the lender's contract; in sandbox phase, FinToken X is liable for up to 1% of cumulative disbursed volume per default. |
| Obligor enters administration before maturity | Receivable shifts to OBLIGOR_INSOLVENT; lender notified immediately. | OBLIGOR_INSOLVENT | Token transfer is locked at the chain compliance module; recovery is filed against the obligor's administrators by FinToken X collections on behalf of the lender. |
| Disputed after funding | Receivable shifts to POST_CONFIRMATION_DISPUTE. Settlement may be delayed beyond maturity while compliance investigates. | POST_CONFIRMATION_DISPUTE | If dispute upheld against the seller (fraud), recovery from seller wallet + recourse pool; if dispute is buyer trying to wriggle out, FinToken X enforces obligation. |
432119) and verifies it carriescredit-related regulated activitypermissions. The check fires every 24h continuously after onboarding (Gate 4); a register status change opens an alert in compliance lender monitoring.Designated settlement account: per money-control rule 1, this is the only banking detail the platform handles for the lender. Disbursements leave it; remittances land in it. FinToken X never custodies funds here — we sit between as a directing party with read-only AIS visibility for reconciliation.
Concentration limits are stored as hard rules on the marketplace — receivables that would breach a lender's per-obligor or per-originator cap are not surfaced to that lender.