Invoice settlement
Publish an immutable obligation → your customer pays USDC from their own wallet → Credo verifies and settles it.
Why businesses choose Credo
Stablecoins move money. Credo proves what the money settled. Invoice, payroll, reconciliation, and accounting evidence — connected by verifiable cross-chain settlement, without ever holding your funds.
The problem
Sending USDC globally takes seconds. Running payments is still manual. A transaction hash doesn't tell you which invoice it paid. Finance teams match wallets, amounts, and recipients in spreadsheets. Audit evidence is screenshots and database flags.
The database does not decide whether something was paid. The settlement contract does.
What Credo does
Atomic payroll
One BatchPay transaction pays every contractor — all succeed together or none do.
Auto-reconciliation
Transactions are matched to obligations deterministically; mismatches become explicit exceptions, never silent.
Accounting evidence
Balanced double-entry journals and public receipts are generated only from finalized on-chain settlement.
Public receipts
Account-free, independently verifiable settlement records for auditors and counterparties.
Browser companion
A Manifest V3 extension captures explorer transactions directly into your workflow.
What makes Credo different
| Capability | Typical system | Credo |
|---|---|---|
| Send stablecoins | ✅ | ✅ |
| Invoice tracking | ✅ | ✅ |
| Payroll | ✅ | ✅ |
| Reconciliation | ⚠️ Often manual | ✅ Deterministic |
| Accounting ledger | ✅ | ✅ |
| Source-chain proof | ❌ / trusted provider | ✅ |
| Cross-chain verification | ❌ | ✅ Attestcoin |
| Settlement enforced on-chain | ❌ | ✅ |
| Database-independent evidence | ❌ | ✅ |
| Public settlement receipts | Rare | ✅ |
| Non-custodial | Varies | ✅ |
Credo is not another wallet. It is the business operating layer around stablecoin settlement — the layer that turns a payment into evidence your auditor, counterparty, and accounting system can verify independently.
Business model
Software subscription priced by operational complexity — no custody, no percentage taken from customer funds. The first customers are crypto-native agencies, DAO contributor operations, and treasury teams that already pay 20–200 stablecoin payments a month and reconcile manually.
| Plan | Intended customer | Value |
|---|---|---|
| Free | Small teams evaluating Credo | Limited invoices and public receipts |
| Team | Active distributed teams | Payroll, reconciliation, approvals, and exports |
| Growth | Platforms and treasury operators | API, webhooks, policy controls, multiple organizations |
| Enterprise | Regulated or high-volume operators | SLA, custom controls, deployment and compliance support |
Success metric: the percentage of payment obligations reconciled without manual intervention. Go-to-market: three to five design partners run a real workflow on testnet, measure manual work removed, then convert to a paid Team plan.
How it works
- Create an invoice or payroll obligation — still a draft, no transaction.
- Publish it on Creditcoin: token, receiver, amount, and expiry become an immutable obligation.
- Your customer (or your treasury) pays USDC from their own wallet — Credo never touches funds.
- Attestcoin proves the source transaction;
ProofPaySettlementvalidates it natively on Creditcoin. - On success, settlement finalizes: reconciliation updates, a balanced journal posts, and a public receipt is issued.
Live testnet evidence
Not an architecture proposal — the complete flow has been executed end-to-end on public testnets and is independently inspectable (verified August 21, 2026).
| Path | Sepolia source | Creditcoin settlement | Result |
|---|---|---|---|
| Invoice · 5.0 USDC | 0x232c00…cf11c | 0x88cb6e…4cd59f | SETTLED |
| Atomic payroll · 1.0 + 2.0 USDC | 0xab7d15…e8af | 0xadeaef…fb67 | SETTLED |
| Underpayment · 1.0 vs 2.0 USDC | 0x1004a0…f5924 | 0x6aa3ae…6650 | REJECTED |
Each settlement receipt contains an event from the native USC v2 verifier precompile 0x0FD2 — verification happens inside the Creditcoin execution environment, not in a backend. The underpayment test matters: Credo proves whether a transaction satisfies the business obligation, not merely that it exists.
Security, without the fine print
- Non-custodial — no private keys, seed phrases, or balances stored. The only contract that can move funds is the explicitly invoked
BatchPay. - On-chain validation — token, receiver, amount, expiry, commitment, source chain, and replay protection are checked by the contract.
- Idempotent financial operations — every mutation carries an idempotency key; journals balance inside one transaction.
- Wallet authentication — origin-bound signed challenges, server-side revocation, capability-based roles (owner / operator / viewer).
Roadmap
| Phase | Status | Scope |
|---|---|---|
| 0 — Settlement primitive | ✅ | Cross-chain proof, settlement contract, invoice / payroll / negative-path |
| 1 — Business operations | ✅ | Reconciliation engine, double-entry ledger, public receipts, browser companion |
| 2 — Production readiness | ○ | Additional stablecoins / networks, production proof infrastructure, monitoring, security review |
| 3 — Finance integrations | ○ | Accounting / ERP integrations, treasury workflows, approval policies, export APIs |
| 4 — Settlement network | ○ | Multi-chain obligations, programmable policies, cross-border AP, autonomous operations |
Try the working product.
Run the real workflow on public testnets, inspect the evidence, and follow every payment from intent to final receipt.