MUSD Pay Links

Mezo Buildathon, Access and Distribution track

A merchant asks for MUSD with a standard EIP-681 link or QR code. Before the payer's wallet or agent builds the transfer, the guard checks that the token is the real MUSD for that chain, that the recipient address is valid and checksummed, and that the amount is within the payer's limit. Every refusal says why.

Live MUSD contracts

Read just now from the MUSD contracts over the public Mezo RPC, through this Worker. Nothing here is hard-coded except the contract addresses.

Reading the contracts...

1. Merchant, request MUSD

Creates the link and QR code. The link is run through the payer guard before it is shown.

Network Your address (recipient)

Amount in MUSD

Reference (optional)

2. Payer, check before paying

Paste any link. The checks run in your browser with the same library the API uses.

Payment link

Try a bad link

Your limit in MUSD

Checksum

Allowlist (optional, one address per line)

3. Merchant, confirm the payment on chain

Reads the transaction receipt and counts MUSD Transfer events from the real MUSD contract to the address you enter. Prefilled with a public MUSD transfer on Mezo Testnet made by someone else on 17 October 2026. That transfer was a contract to contract MUSD movement, not a payment to a merchant, and no merchant payment has been made yet. Verification retries a few times if the public RPC lags.

Transaction hash

Network

Recipient

Expected MUSD

Reference

Open source under the MIT license: github.com/theluckystrike/musd-pay-links. JSON API at /api/check, /api/link, /api/verify, /api/token. Built by Michael Lip, Warsaw, Poland.