From the first tap to the last scan

Entraqo covers the whole visit: choosing a slot, paying, carrying the ticket, passing the gate and reading the numbers afterwards. Here is what each part does.

The buyer journey

  1. 1

    Pick a slot

    The venue home shows products and the next available times. Capacity is enforced per zone per slot, so a sold-out Oratory never oversells.

  2. 2

    Choose tickets

    Adult, senior, student, child, resident, family, guided, audio — the tiers the venue defines. Bundles combine products in one line.

  3. 3

    Add from the shop

    Guide book, print, audio guide: in the same basket as the tickets, collected at the venue by scanning the same wallet.

  4. 4

    Pay with the fee in view

    Face value plus the booking fee, itemised. Stripe handles the card with 3-D Secure; amounts are recomputed server-side from the price list.

  5. 5

    Receive the wallet

    A magic link opens the buyer's wallet: every ticket with its rotating QR, shop items, transfer and reschedule within the venue's rules.

The gate

A progressive web app for staff on ordinary Android phones. Camera scan, zone selection, result in under 300 milliseconds, every scan logged.

  • Offline by default

    The QR is a signed token carrying ticket id, zones, validity window and holder initials. The device verifies it with the venue's public key and no network.

  • Blackout mode

    A switch in the gate app disables the network and proves the phone still admits and refuses correctly. Two charged phones and a power bank are the whole hardware list.

  • Local mesh

    Devices at the same venue share scan logs over local Wi-Fi or Bluetooth, so a ticket used at door A is refused at door B within seconds, with no internet.

  • Printed fallback

    Every ticket carries a ten-character code and a Code-128 barcode. The admin prints the day's manifest before opening; paper and a pen are the last line.

  • Reconciliation

    When connectivity returns, devices push their logs. The server merges them, flags duplicates for review and recomputes capacity. Nothing is silently dropped.

The wallet

  • No app to install

    The wallet is a page, cached in the browser, so a loaded ticket still shows its QR with no signal at the door.

  • Rotating QR

    The code changes every 30 seconds and is signed per venue. A screenshot shared on a group chat is dead within the minute.

  • Transfers inside the system

    Send a ticket to another wallet by email, as a gift or at face value plus fee. The original QR dies; the seller's payout is held until the gate scan.

  • Reschedule within rules

    Move to another slot when the venue's policy allows it, logged, without a helpdesk ticket.

Your tickets in one wallet

Every venue on Entraqo issues tickets to the same wallet: sign in once with your email and see every ticket you hold, grouped by venue, upcoming first. Each ticket opens on the venue's own domain with its rotating QR; Apple and Google Wallet passes follow once the venue installs its certificates.

Open your wallet

Inside the venue's own website

One script tag and one div put the slot picker on the venue's existing site, in the venue's colours or inheriting the page's own. Checkout and payment open on the venue's ticketing domain, never inside the frame, so the visitor pays where the certificate says they do.

Agents and DMCs

Resellers self-register, the venue approves, and they receive an API key and an embeddable widget for their own site. Availability, holds and orders through the API; their own sales dashboard; commission paid out of the platform's slice so the venue's economics never change.

Shop

Souvenirs, guides and add-ons sold in the ticket flow and collected at the venue shop by scanning the wallet. Shop revenue goes to the venue minus a published platform fee; VAT per product.

Reporting

Sales by day, product, tier, zone, slot, performance and agent. Live occupancy. Settlements per promoter and agent. CSV export of everything.