Crypto payments at events: taking crypto at markets and festivals
Crypto payments at events explained: taking crypto at markets and festivals, what Qvard plans for event terminals and the working path with the API today.
Crypto payments at events mean vendors at markets, festivals and fairs accept crypto from visitors. Qvard plans a terminal for such events, and it is not released yet. This guide explains the event flow and the path that works today: each vendor’s register creates payments through the API and shows a QR code to the visitor.
Why events are a special case
At an event there is often no stable internet and many short sales in a row. Each sale must still be a separate payment with its own status, and the vendor needs a clear way to show the amount.
Status: the event terminal is on the roadmap
A Qvard terminal for event vendors is not released yet, and this article does not describe it as available. The working path below uses the API, the hosted page and the webhook, and needs a connection at the moment of payment.
What works today
The vendor’s register creates each payment with POST /api/v1/payment and the x-api-key header, receives a redirectUrl and shows it as a QR code. The visitor pays on the hosted page, and the webhook returns the final status to the register.
One payment per sale
Create a separate payment for every sale, with a unique id, so that each sale can be confirmed on its own. Batch totals are not a substitute for per-sale status.
x-api-key: sk_live_…
{
"id": "order_1024",
"price": 149.99,
"paymentSystemId": 12
}
// 201 Created
{
"data": {
"id": "8f3k2a1c",
"redirectUrl": "https://my.qvard.com/pay/8f3k2a1c"
},
"code": 201,
"message": "success",
"status": true
}Plan for weak connectivity
If the connection is poor, keep the sale pending on the register and retry the request when the network returns. Do not show a sale as paid until the webhook confirms it.
Reconcile after the event
After the event, compare the list of sales in the register with the paid webhooks. Sales that stayed pending need a follow-up before they are closed.
FAQ
Is there a Qvard event terminal today?
Not yet. The event terminal is on the roadmap. Today each vendor uses a register that works with the API.
Does a vendor need internet at the stall?
Yes, to create payments and receive the webhook. Plan a connection or retry strategy for the event.
Can one payment cover several sales?
No. Create one payment per sale, so that each sale has its own id and status.
How do I test before an event?
Create demo invoices from a test register and check that the webhook marks each one before the event starts.
