Find payment codes on the Payments shelf of Create. Each one is built to its own scheme's standard, and every field is checked before the code is made.
What each one does when scanned
- UPI: any UPI app opens with your UPI ID and the amount filled in. The person confirms the payment; nothing is taken by the scan.
- PIX (Brazil): a banking app opens the transfer with your key and amount. The checksum is computed, so a bad code is refused before printing rather than at the till.
- QRIS (Indonesia): a payment app opens with your merchant details. Any participating app works.
- PromptPay (Thailand): a banking app opens the transfer to your PromptPay ID.
- SEPA transfer (EPC) (Europe): a banking app opens a transfer with the IBAN and amount filled in.
- PayPal.Me: the browser opens your PayPal.Me page, with the amount set if you named one.
- Bitcoin, Ethereum, Solana, XRP and USDT: the wallet opens a payment request. For Ethereum and USDT, the network is written into the code, so it can't be paid on the wrong network by accident. XRP has no payment-link standard, so its amount is shown rather than filled in.
Your payment details are never guessed
Payment details are only what you type. AI can help fill other forms, but it never writes a UPI ID or any other payment address: a wrong one sends someone's money to a stranger. When the studio reads a standee photo, you type the UPI ID yourself before the code is made.
For UPI, add a payee name. Some UPI apps refuse codes without one.
Before you print
- Scan the printed code with two or three different payment apps.
- Send yourself a small test payment.
- Keep a clear white border around the code, and don't place it behind glare.
See Printing a code.
Standees and table tents
To print a payment code on a standee or table tent with your business name and prices, see Print and social designs.