GoPay
GoPay
A self-hosted payment backend built for agents and services to exchange value directly, rather than routing every micro-transaction through a card processor. The core idea: a pluggable payment router in front of swappable provider backends, with every transaction backed by a cryptographically signed, Merkle-anchored receipt instead of a bare ledger entry you have to trust.
What's actually working
- An HTTP account API - register, deposit, withdraw, check balance - backed by an in-memory ledger.
- A payment router that picks a provider by cost, speed, and reliability instead of hardcoding one.
- A full Litecoin MWEB (MimbleWimble Extension Blocks) proof of concept: privacy-address generation, invoice creation, sending LTC to an MWEB address, and independently verifying the resulting receipt.
- Ed25519-signed receipts with Merkle proofs, so a receipt can be verified without trusting whoever issued it.
What's still rough
This is pre-MVP, and the project says so plainly: account state is in-memory only (a restart clears every balance), HTTP auth is stubbed rather than enforced, and some crypto utilities are still placeholders. The zero-trust gateway (TLS, macaroon auth, rate limiting) and the agent client SDK are both mid-build.
Why
Card rails don't make sense for sub-cent, machine-initiated payments - the fee alone can exceed the transaction. GoPay's bet is that agents paying each other directly, with a receipt they can verify themselves instead of a balance they have to trust, is a more honest shape for that problem than bolting a traditional payment processor onto an API.