In person
Show the checkout page on a phone or tablet. The customer scans with their own wallet and the status updates on your screen as it confirms.
QR Payments
Point a camera at it, and it is paid
Every Droppy link generates a QR code that wallets read natively. The recipient, asset, chain and exact amount are all encoded — so there is nothing for your customer to type, and nothing to mistype.
The standard
A plain EIP-681 URI — not a proprietary code
EIP-681 is the Ethereum standard for payment request URIs. Because Droppy emits exactly that, any compliant wallet can read the code — there is no Droppy app for your customer to install, and no lock-in for you.
- For ETH the URI carries the destination address, the chain id and the value in wei.
- For USDG it targets the token contract and encodes a transfer call with your address and the exact base-unit amount.
- Scanning never signs anything. Your customer still reviews and approves the transaction in their own wallet.
ETH request
ethereum:0xE0a4f428...048A@4663
?value=50000000000000000USDG request
ethereum:0x5fc5360D...1d168@4663/transfer
?address=0xE0a4f428...048A
&uint256=250000000Where it fits
Made for counters, invoices and print
On paper
The QR is a high-contrast image that survives printing on an invoice, a receipt or a table card. Error correction handles a scuff or two.
In a message
Send the link and the QR together. Whichever your customer finds easier, both resolve to the same verified payment request.
Specifics
What the code encodes
- Standard
- EIP-681 payment request URI
- Chain
- Robinhood Chain, chain id 4663 (testnet 46630)
- Assets
- ETH natively, USDG as an ERC-20 transfer call
- Amount
- Encoded in base units, exact — never rounded or approximated
- Error correction
- Level M, comfortable for screens and print
- Safety
- Scanning only pre-fills a transaction. Nothing is signed or sent until the payer approves it in their wallet.
Ready to accept crypto?
Create your first payment link in under a minute. No signup form, no API key.