About
What Settle is
Settle is an open-source prototype for supporting an essential bill. A requester shares a bill, a supporter funds part or all of it, and the intent is that the money reaches the provider directly.
Status
Settle 1.1.0 is a testnet prototype. It uses sample data, moves no real funds, and has no users, partners or volumes to report.
Why it exists
Asking for help with rent, power or a clinic bill is awkward, and giving to a stranger's wallet is hard to trust. Settle explores a narrower path: confirm the bill, redact what is private, and send help to the biller instead of a person.
The part Settle is trying to get right is the layer between a verified bill and a payment: a quote the server controls, a wallet that signs exactly that quote, and a receipt that can be checked. It is not meant to be a general escrow or crowdfunding product.
Who maintains it
Settle is written and maintained by Anas Abubakar and released under the MIT license. See the license for the full terms.
Repositories
- settleThe Expo app for web, iOS and Android, and these docs. github.com/Anasabubakar/settle
- settle-apiThe testnet settlement service: quotes, unsigned payments, confirmation and receipts. github.com/Anasabubakar/settle-api
Contribute and report
- Report vulnerabilities privately through the security policy, never in a public issue.
- Follow what changed in the changelog.
Current status
- Web appBuiltAn interactive prototype built with Expo. All data in it is sample data.
- iOS and AndroidBuiltExpo source that runs in Expo Go. There is no store release.
- Bill filesBuiltPicked on your device and previewed there. They are not uploaded.
- AI bill reviewSimulatedA scripted product simulation. No model reads your bill.
- Funding a billSimulatedA testnet preview. No payment is created or signed in the app today.
- WalletSimulatedFreighter detection on web. Mobile wallet signing is not built.
- Settlement APIBuiltA separate testnet reference implementation with fixture providers and rates. Not for production.
- MainnetNot builtNot enabled. It needs the work listed in the readiness guide first.
The flow page explains each step, and the readiness guide explains what must exist before any live use.