How Settle works.

Settle connects private invoice records with full-invoice financing in USDC. A business issues an invoice, a funding provider purchases it at a discount, and the customer’s repayment is made available to the current beneficiary.

One invoice. A connected journey.

1. Create & submit. The authorised issuer defines face value, purchase price, dates, customer wallet, and a private document commitment.
2. Review. An authorised reviewer records an evidence decision. This is independent from customer acceptance.
3. Accept. The customer accepts exact terms. Onchain acceptance binds the chain, settlement contract, invoice ID, document commitment, token, fee recipient, and financial terms.
4. List & fund. After review and acceptance, an issuer can list an invoice. An eligible provider purchases it in full before its due date.
5. Repay. The full invoice is paid into settlement escrow once. Repayment after maturity remains possible.
6. Claim. The beneficiary withdraws the credited repayment once.

An unfunded invoice can be paid directly, crediting the issuer. Unfunded, unpaid invoices can be cancelled or delisted. Funded invoices cannot be cancelled. “Overdue” is a time condition, not an automatic penalty or seizure.

Know exactly what the numbers mean.

For face value F, purchase price P, protocol fee C, and actual remaining duration D in days:

• Business net proceeds = P − C
• Expected gross profit = F − P
• Expected term return = (F − P) / P
• Simple annualised equivalent = ((F − P) / P) × (365 / D)

These are estimates, not guaranteed returns or compounded APY. Due invoices have no positive-duration estimate and are excluded from new financing. Amounts use integer USDC units. Display rounds to the nearest cent, with ties rounded up; transfer amounts retain all six decimals. Fees are immutable for accepted terms and capped at 5% of purchase price in the contract; the initial deployment fixes the fee at zero.

Visibility helps. Risk remains.

Onchain records and review decisions do not prove an offchain invoice is authentic, enforceable, or certain to be paid. Customer acceptance does not create insurance. A provider can suffer delay or lose all capital. No credit score, insurance product, or guaranteed return is represented here.

Administrators grant issuer, reviewer, and funder roles and can pause new risk-taking operations. They cannot redirect an existing repayment entitlement. Repayment and claim paths remain open during a pause. USDC issuer controls and token restrictions can still affect transfers.

The included contract has automated tests but has not been independently audited. Before accepting real funds, the operator must define eligibility, evidence standards, disputes, collections, jurisdiction, and legal obligations, and complete independent security review.

One USDC balance. Two interfaces.

Arc Mainnet uses chain ID 5042, RPC https://rpc.mainnet.arc.io, and Arc Explorer. Configuration was checked against official Arc documentation on September 16, 2026, including a live RPC check of the chain ID and USDC metadata.

Native gas accounting uses 18 decimals; the ERC-20 USDC interface at 0x3600000000000000000000000000000000000000 uses 6. Both refer to one underlying balance. Settle’s transfer adapter uses the ERC-20 interface, verifies metadata, and reserves native gas costs separately. See Arc’s stablecoin model.

Local development (chain 31337) and Arc Testnet (chain 5042002) remain available as separate configurations. Settle only activates financial actions after verifying its own contract deployment, token, administrator and runtime code. The administrator deploys from Settings using their own wallet and USDC for gas.

Commercial details stay private.

Live invoice documents are stored in private application storage. Record-level authorisation is required for every read and upload. A document hash is a commitment, not encryption. An unguessable payment URL does not authorise access to supporting files.

Documents up to 4 MB are stored in the private database. Wallet sessions use expiring, one-time signatures and HttpOnly cookies. Invoices and uploads persist across browsers and devices. Customer payment links show payment terms without revealing private evidence. Copying a link does not send an email or message.

Production wallet authentication uses one-time, expiring challenges and server-verified sessions. Organisation memberships and reviewer roles are checked on the server. Onchain issuer, reviewer and funding permissions are separately enforced by the contract.

Your workspace is online.

Connect an Ethereum-compatible browser wallet, sign in, and create your business or provider profile. Businesses can create and edit drafts, attach private documents, lock invoice terms, and share customer payment requests.

The operator must be assigned by the platform owner. In Settings, that wallet can deploy the compiled Settle contract, activate it after server verification, and approve issuer, reviewer and funding permissions. Every contract action requires a wallet transaction. No private key is collected by Settle.

Invoice issuance, review attestations, customer acceptance, listing, funding, repayment and withdrawal use verified contract calls. Receipts are reconciled into saved records; a pending transaction can be recovered after refreshing. Use “Refresh onchain status” to check changes made outside the platform. The app shows whether the settlement contract has been activated.

Underwriting integrations, additional assets, token staking, fractional funding, and secondary transfers are future extension points. No tokenomics or speculative financial products have been implemented.