ProxyPay, LLC · Pilot stage
Merchant payment control plane for stablecoin at the register.
ProxyPay issues an open, signed payment request that a customer's wallet verifies and pays. It shows the cashier what happened, watches the public ledger, reconciles the day, and prepares refund, close-out and treasury proposals. The merchant approves them with the merchant's own keys.
What the control plane does
Issues
A signed payment request carrying the merchant, the location, the exact amount in base units, and an expiry. The wallet verifies the signature before anything is paid.
Shows
The register sees one state at a time: waiting, paid, expired, or check with a manager. Colour, icon and words together — never colour alone.
Observes
ProxyPay reads the public ledger for the transaction that settles the request and keeps an append-only timeline of what it saw and when.
Proposes
Refunds, end-of-day close-out and treasury sweeps are prepared as proposals. Approval happens on merchant-controlled keys, outside ProxyPay.
Where ProxyPay sits
ProxyPay software does not hold, receive or transmit funds. It has no customer signer and no merchant signer. The money goes from the customer's wallet to the merchant's own vault, and onward through the merchant's own exchange account.
The economics, with the counterpart
What changes
- No card-network interchange on a stablecoin sale, because no card network is involved.
- No chargebacks, because the customer approves the payment in their own wallet and the transfer is final once the ledger confirms it.
- The customer pays the network fee on their own transfer. ProxyPay does not mark it up.
- Settlement lands in an account the merchant controls, not in a processor’s account awaiting payout.
The honest counterpart
Finality cuts both ways. A mistaken or disputed payment cannot be pulled back: a refund is a second, merchant-initiated transfer that a manager proposes and merchant-controlled keys approve. That makes a clear receipt at the counter, an unambiguous amount, and a refund policy your staff can recite part of the product, not an afterthought.
Depending on who you are
You run the store
What the cashier does, what happens when a payment is slow, who can approve a refund, and what you need in place before a pilot. For store owners
You own the numbers
Vault topology, approval thresholds, sweeps, the refund invariant, close-out and signer health. Treasury and controls
You integrate the POS
The open request protocol, the validation order a wallet must follow, and the failure taxonomy. For developers
Pilot stage
ProxyPay is pre-launch. There is no production service, no customer list and no performance claim on this site. We are looking for a small number of retailers to run a supervised pilot with their own vault, their own keys and their own exchange account.