Arc mainnetreal USDC
SettleOnce
Arc

How it works

Six steps, and the chain remembers all of them.

SettleOnce pays USDC invoices on Arc straight from your wallet, and gives each invoice a permanent key so the contract can turn away a second payment for it. Here is the whole loop, including what happens when your app dies halfway through.

  1. Step 1: Connect wallet

    Connect the wallet the money leaves from, on Arc. SettleOnce never takes custody and never asks for a seed phrase: it spends your USDC allowance, in your name, for the exact amount of one invoice. The same wallet is the one the contract files settlements under, so paying invoice INV-1042 from a second wallet is a separate record and a separate payment.

  2. Step 2: Add an invoice

    Three ways onto the desk: photograph a paper invoice and let the scanner read it in your tab, type it in by hand, or load the CSV file you keep. An invoice is four things — vendor reference, invoice number, recipient wallet and USDC amount. The first two become its permanent key; the last two are payment details you can still fix before paying.

  3. Step 3: Save your invoice file

    Download the CSV. The desk in this browser is a convenience, not storage: clearing site data, a new laptop or a private window all lose it. The file is small, plain text and yours, and it is what you load back after anything goes wrong. Nothing about payment status is in it — that always comes from the chain.

  4. Step 4: Pay once

    The desk reads the chain for the invoice key first, then pays. If your USDC allowance is short, the approval and the payment go out as one batched transaction, so your wallet asks for one signature. The contract records the settlement under (your wallet, invoice key) and moves the USDC in the same transaction. A second attempt at that key is rejected on chain.

  5. Step 5: Recover after a crash

    This is the step the whole thing exists for. If the tab dies between the signature and the confirmation, you have no idea whether the money moved — so don't guess. Reopen the app, load your invoice file, and every row is checked against the contract: paid rows come back marked paid with their original transaction, the rest stay payable. There is nothing to reconcile by hand.

  6. Step 6: See receipt and ledger

    Every paid invoice has a public receipt page read live from the contract, with a QR code of its own link and downloads as JSON or PDF for your records. The ledger lists every settlement this deployment has ever made, newest first, with a lookup form for one vendor reference and invoice number. No login, no wallet needed to read either.

What SettleOnce guarantees

For one chain, one SettleOnce deployment, one payer wallet and one invoice key: at most one successful settlement.

  • A second payment for an invoice key you already settled is rejected on chain with AlreadyPaid.
  • Changing the recipient or the amount under a settled key is rejected with SettlementConflict, not paid as a new invoice.
  • A failed USDC transfer reverts the record with it, so the invoice stays payable.
  • Paid status is read from the contract, so it survives a crashed tab, a wiped browser and a new device.
  • USDC moves from your wallet to the recipient inside one transferFrom. Nothing is held by the contract.

Enforced by 0x0D58…CA2c on Arc. No owner, no reset, no upgrade proxy.

What it does not do

  • It can't tell whether an invoice is legitimate: a forged invoice with fresh references is a new invoice to the contract.
  • It can't stop payments made outside it. A plain USDC transfer, or the same invoice paid from another wallet, is out of scope.
  • It can't recover a payment sent to the wrong address. Check the recipient against the paper before you pay.
  • It can't link the same real-world invoice entered under different references. Different references are a different key.
  • It isn't a bookkeeping system. The invoice file stays yours; there is no backend and no database.

Start on the desk