P2P Credit
P2P Credit turns identity, underwriting, escrow, servicing, and settlement into one programmable rail — so your platform can originate, fund, and service loans between people, businesses, and agents without carrying the risk on your own balance sheet.
Why it exists
The idea is rarely the hard part. Matching a lender to a borrower is a weekend. Everything after that — proving who they are, deciding what they can afford, holding the money safely, and keeping an honest record for the next three years — is the product. P2P Credit is that part, built once.
Every new market needs new signals, a new scorecard, and a new appeals path. Most teams end up with a spreadsheet behind an API and no record of why anyone was declined.
Capital leaves the lender the moment a button is pressed, so collateral, guarantees, and conditions get chased afterwards — over email, in a different system.
Partial payments, early settlement, restructures, grace periods, defaults, and the ledger entries behind all of them. This is the work, and it never appears in the demo.
How it works
Each step composes modules that already run the rest of the platform, so credit inherits the identities, accounts, and audit trail you are already using.
Step 1 of 6
A credit agreement is only enforceable against an identity that can be proven later. Borrower and lender are resolved before terms are ever quoted.
Step 2 of 6
Underwriting returns an approval, a limit, a price, and the reasons behind all three. A score with no explanation is not a credit decision — it is a refusal with extra steps.
Step 3 of 6
Terms compile into an agreement both parties sign: schedule, profit or fee basis, collateral, grace period, and what happens on a missed payment.
Step 4 of 6
Lender capital settles into a segregated escrow account and is released only when the funding conditions on the agreement are satisfied.
Step 5 of 6
Repayments, partial payments, early settlement, and restructures execute against the schedule and post to a double-entry ledger as they happen.
Step 6 of 6
Grace periods, restructuring offers, collateral liquidation, guarantor calls, recovery, and write-off are defined at origination and executed as workflow.
Capabilities
Principal, schedule, markup or rate, collateral, grace period, and default path are fields on a single agreement object — not scattered across four services.
Lender capital settles into a segregated escrow account and releases only when the conditions written into the agreement are met.
Every approval, limit, and price returns reason codes and the policy version that produced it, so a decline can be reviewed, appealed, and defended.
Stablecoins, tokenized real-world assets, receivables, group guarantees, and guarantor signatures — held, valued, and released under policy.
Schedules, retries, reminders, partial payments, and early settlement run against the signed terms and post as they happen.
Grace, restructuring offers, guarantor calls, collateral liquidation, recovery, and write-off execute as workflow defined at origination.
Every movement lands as a balanced ledger entry with the agreement, party, and policy attached. Nothing waits for a nightly reconciliation job.
Autonomous agents hold verified identities and act within explicit limits, so a machine can request, fund, or repay credit under a mandate you set.
Fund in one currency, repay in another. Stablecoin and fiat rails settle through the same accounts and the same ledger.
Credit structures
Conventional and Shariah-compliant credit are two families of the same contract model — same escrow, same servicing, same ledger. You can offer both without maintaining two systems.
Interest-bearing structures, priced per agreement and serviced against a schedule.
A fixed principal repaid over a fixed schedule, with amortisation set at origination.
Interest accrues daily on the outstanding balance.
A reusable limit the borrower draws against and repays, with the limit restored on repayment.
Interest on drawn balance, plus an optional commitment fee.
Capital advanced against a verified receivable and cleared when the invoice is collected.
Discount rate applied to the face value of the invoice.
Financing secured against the asset being acquired, with the lien tracked on the agreement.
Interest, with recovery routed to the pledged collateral.
Pricing, fees, grace periods, and late-payment treatment are set per portfolio and disclosed to the borrower before acceptance.
Structures where the return comes from a sale, a lease, or shared profit — never from lending money at interest.
A benevolent loan. The borrower repays the principal and nothing more.
No return to the lender. Any platform fee is fixed and disclosed.
The financier buys the asset and resells it to the borrower at a disclosed markup, payable in instalments.
A fixed markup agreed before the sale, not a rate over time.
Both parties contribute capital to a venture or asset. Diminishing Musharakah lets the borrower buy out the share over time.
Profit shared by agreed ratio; loss borne in proportion to capital.
One party provides capital, the other provides the work. Common for cooperative and community funds.
Profit shared by agreed ratio; capital loss sits with the investor.
Ijarah, Salam, Istisna, and Wakalah use the same contract model. Structures are configurable so your Shariah board approves the terms, not our defaults.
Use cases
SACCOs, ROSCAs, and stokvels run on trust that already exists. Group guarantees, rotating contributions, and Qard Hasan are first-class structures rather than workarounds.
Formalise an existing circle without changing how it works.
Underwrite against settlement history you already hold, advance against verified receivables, and collect from future payouts before they leave the platform.
Fund sellers from the data your platform already produces.
A lender in one jurisdiction funds a borrower in another. Identity, sanctions screening, currency, and disclosure rules are resolved per side of the agreement.
Lend across borders without a bilateral integration each time.
An agent that buys compute, data, or inventory can hold a revolving line with hard caps, an expiry, and a human owner who can revoke it instantly.
Give machines spending power without giving up control.
Underwriting
Credit decisions change what people can do with their lives. That makes explainability a requirement, not a feature — and it is why every decision here arrives with its reasoning attached.
They score repayment likelihood from cash-flow patterns, repayment history, collateral quality, and network signals such as group guarantees. They do not set your credit policy — the policy engine does, and you own it.
Each outcome carries ranked reason codes, the inputs that drove it, and the policy version in force at the time. That record is what makes an appeal possible and an audit survivable.
Any decision can be routed for review, and a reviewer can override with a recorded justification. Overrides are tracked as their own signal so you can see where the model and your team disagree.
Thin-file and low-confidence cases fall back to a deterministic rule set or a manual queue instead of guessing. A borrower is never declined by a model that had nothing to work with.
Borrower data stays scoped to the agreements it was collected for. Zero-knowledge proofs let a lender confirm a condition — income band, residency, age — without receiving the underlying document.
Security and compliance
Lending attracts scrutiny — from regulators, auditors, partners, and the borrower who disputes a charge. These are the mechanisms behind that scrutiny, not a badge row.
Lender capital is held apart from platform funds and can only move along paths the agreement permits.
Policy changes, manual overrides, and liquidations require a second approver and are recorded against a named identity.
Decisions, signatures, disbursements, and repayments are append-only and exportable as a single evidence pack per loan.
Rate caps, disclosure requirements, cooling-off periods, and collections rules are enforced per market rather than per developer.
Both parties are screened at origination and rescreened on schedule, with hits blocking release rather than raising an alert after the fact.
Signing keys for escrow and collateral sit in hardware-backed custody with quorum approval for release.
Developers
Structure, parties, principal, schedule, collateral, escrow conditions, and default handling are declared once. Everything after origination — release, servicing, escalation — runs from that declaration and reports back over webhooks.
POST /v1/credit/agreements
{
"structure": "murabaha",
"borrower": "idt_9c1f4a2b",
"lender": "pool_community_04",
"principal": { "amount": "250000.00", "currency": "USDC" },
"markup": { "type": "fixed", "amount": "18750.00" },
"schedule": { "instalments": 12, "cadence": "monthly" },
"collateral": [
{ "type": "tokenized_invoice", "ref": "inv_7d20e1" }
],
"escrow": {
"release_on": ["collateral.locked", "borrower.signed"]
},
"on_default": { "grace_days": 7, "then": "restructure_offer" }
}Get started
Bring the lenders and borrowers. We will handle identity, underwriting, escrow, servicing, and the record that has to survive an audit.