On this page
- Tickets are delivery codes: you generate the codes, paste them into a shop product, and the number of codes is your capacity.
- Each purchase is one ticket; a pair is a separate product with two codes on one line. Buyers pay your price plus a Solana fee under $0.01, and you pay nothing.
- Receipt pages are public and nothing marks a code as used, so the door check is your spreadsheet: first person to show a code gets in.
Which events can sell tickets for USDC on Fianto?
Fianto fits events with one kind of entry, a known capacity in the hundreds or low thousands, and an audience that already holds USDC: a meetup, a workshop, a conference side event, an online session. USDC is a dollar stablecoin; the buyer pays it from a Solana wallet, and the price moves from their wallet to yours in one transaction.
| What a ticketing platform usually does | On Fianto | What you do instead |
|---|---|---|
| Seat maps and reserved seating | Not available | Sell general admission only, or one product per seating area |
| QR codes and a scanning app | Not available | Check codes against your own list at the door |
| Several tickets in one order | Not available: one price of one product per purchase | Add a "Two tickets" product with two codes on one line |
| Attendee names | Not collected; only the buyer email | Ask for names in the after-purchase message |
| Ticket transfers | Not tracked | A forwarded receipt works as a transfer, so treat the code as the ticket |
| Refunds | No refund button | Send USDC back from your wallet |
| Reminders before the event | None | Email buyers yourself from your sales export |
If more than two of those rows matter for your event, use a ticketing platform. As one dated reference point, Eventbrite's US pricing page listed "3.7% + $1.79 service fee per ticket" and "2.9% payment processing fee per order" on 15 October 2026, paid by buyers by default; on a $25 ticket the service fee alone is $2.72. Those fees buy features this post says Fianto lacks. If buyers should be able to resell entry, a token checked at the door is the other model, compared in token-gating vs subscriptions.
How do you turn delivery codes into tickets?
A delivery code is a line of text from a list you upload, given to exactly one paying buyer; for an event, it is the ticket number. The mechanics (5,000 unused codes per product, holds while a buyer pays, low-stock emails) are the same as for software keys and are set out in selling licence keys for USDC. For tickets, the setup is:
- Generate ticket codes in a spreadsheet, one per seat, random enough not to guess and 12 or more characters long, for example QFL-WS-7K2M9X, so the dashboard later shows the last four. Keep the sheet: it is your door list.
- In the dashboard, create a product named after the event with a one-off price, say 25.00 USDC.
- Add it to your shop. There is no event kind; Service works, since its button reads "Book" and it asks for the buyer email as Required. Kinds change only the button, the email field and the default message, as the Support or tip kind in a USDC tip jar shows. Replace its default message under After a purchase with the date, the address and the door rules, up to 2,000 characters.
- Turn on "Give each buyer a code" and paste the codes. Sixty codes means sixty tickets.
- Publish. Your merchant account must be approved first, and a published change reaches visitors within about 15 seconds.
The buyer sees their code on the receipt page and in the shop's buyer email. Fianto stores the codes encrypted and shows you only the last few characters of each, next to the purchase it went to, and the product's code list shows only the 20 most recently given. The spreadsheet is the only full copy you have. The shop's other limits, such as the fixed your-name.fianto.xyz address with no custom domain, are in the no-code USDC shop post, and how the shop compares with merchant-of-record platforms is in Gumroad, Lemon Squeezy and Paddle for crypto sellers.
How do you stop selling when the event is full?
A shop ticket product stops selling by itself when its codes run out: it shows a disabled "Sold out" button, and a checkout that finds no free code refuses before the wallet signs. While every remaining code is held by an open checkout, the product shows "Reserved" instead.
One edge case can take you one seat over. A payment can settle after its checkout expired and its code went back on the shelf; if the shelf is empty by then, that buyer has still paid, the receipt says the code will appear once you add one, and you get an email that a buyer is waiting. Leave a seat or two of slack, or refund that buyer.
To stop sales before the codes run out, for instance on the morning of the event, use "Remove unused codes". It deletes every free code of the product; codes already given out or held for a checkout stay. You can also unpublish the shop.
Can a payment link sell tickets instead?
A payment link can cap sales but cannot hand out codes. Its "Ends when full" limit closes the link once it reaches the number of paid payments you set, from 1 to 10,000, and "Ends on a date" closes it at a time you pick. The proof of purchase is then the receipt and the paying wallet, which makes door checks harder. Fianto never refuses money that has already moved, so a payment that lands late can take the count past the limit. Link limits are covered in USDC payment links.
How do you check people in without a scanning app?
Check-in on Fianto is a lookup in your own spreadsheet: the guest shows the code from their receipt or email, you find it, and you mark it used. Nothing in Fianto marks a code as used.
- Print your spreadsheet of codes, or load it on a phone that works offline, sorted by code. Unsold codes were never shown to anyone, so a code from your list in a guest's hand was bought.
- At the door, find the code and tick it. A code already ticked means someone forwarded the receipt; the first person to show it got in.
- For a guest whose code is not on your list, compare its last characters with Recent purchases in the shop dashboard, which shows up to the latest 50.
What happens if you cancel or move the event?
A cancelled event is refunded by hand: Fianto has no refund API, and you send USDC back from your own wallet to each buyer's wallet, which the sale record shows. The buyer cannot pull a payment back, and there are no chargebacks. Strike refunded codes off your door list, since a code once given is never taken back. The mechanics are in how to refund a USDC payment.
Fianto sends buyers no message about a change. To tell everyone, export the orders or customers CSV, whose email column holds the address each buyer typed, unverified, and write to them yourself.
What does a USDC ticket cost the buyer and the organiser?
An invented example: Quillfern Labs sells 60 workshop seats at 25.00 USDC. Each buyer pays 25.00 USDC plus the Solana fee of the one transaction they sign, under $0.01; the checkout tells them the exact SOL they need. A one-off ticket carries no USDC network fee, and there is no Fianto fee during the beta. After the beta the buyer pays about 0.1 to 0.5% on top, at most 0.125 USDC on a 25.00 ticket. Quillfern pays nothing either way, and a sold-out workshop puts 1,500.00 USDC in its wallet, sale by sale.
Buyers need a Solana wallet with USDC and a little SOL, which many event audiences do not have. Sell USDC tickets alongside card tickets unless your audience is already on chain. The checkout itself is described on the hosted checkout page, and the buyer's view in the Fianto docs on buying from a shop.
Load sixty codes, publish the page, take USDC for every seat. You pay nothing.
Open a shop