Skip to main content
Clever Ops

Case studyReal job

How we built two venue websites with Square payments

We built two websites to the owners' own designs, each with an editor the owners use to change pages, menus, events and products.

  • SquareCard payments
  • OpenTableTable bookings
  • Google DrivePhoto and video links
  • ResendEmail

Transcript

This is a made-up event being set up in a website editor we built for two hospitality venues. Staff set the date, the seats and the ticket price. A guest books and pays by card, through Square, without leaving the venue's own site.

Both venues have the same owners, and we'd worked with them before. They came back with their own page designs: a rebuild of one venue's website, and a new website for the second venue.

They were on WordPress, and they found it hard work for the things that change often. They wanted to update menus, events and shop items themselves, without waiting on a developer and without anything complicated to learn.

There was more on the list. A proper gift voucher, with amounts to choose from, emailed to the person receiving it. A small shop for pickup orders on the second site. Table bookings kept on their own site, through OpenTable. Paid event tickets came a little later.

So we built both sites to their designs, each with its own editor behind a login. Staff change the pages, menus and events, and on the second site the blog, products and orders. For a photo or a video, they paste a Google Drive link, and the site handles the rest.

A gift voucher works like this. The buyer picks an amount and pays in Square's card form. Our server charges the card, gives the voucher a number, a private link and an expiry date, and saves it. Then it emails the voucher to the recipient and a receipt to the buyer. Staff can print a voucher, mark it used, or archive it.

Events have a booking mode: a waitlist, a free RSVP, or paid. For a paid event, the server checks there's room, works out the total from the ticket price, charges it, and sends a confirmation with a booking reference. Staff can add a phone booking by hand, resend a confirmation, cancel a booking, or export the list.

The second site's shop takes pickup orders. Products can have options, like a flavour, the number of people, or add-ons. At checkout the buyer picks a pickup time in fifteen-minute steps, with Today and Tomorrow shortcuts, showing only times inside opening hours that give enough notice for everything in the cart.

People still do the parts that need people. The owners write and update the content. Staff see each order in the editor and get it ready for pickup, and they run the events. Table bookings are handled by OpenTable's own widget, opened from the site's Reservations button.

Now the detail. Each site is a Next.js app on Vercel, with its own Postgres database on Neon. The editor sits behind a password and a signed session cookie. Emails go out through Resend.

Money is worked out on the server, not taken from the browser. Square's card form turns the card into a one-time token. Our server then sets the amount: the ticket price times the party size, each shop line priced again from the products table, or the voucher's face value, checked against an allowed range. Then it asks Square to charge that.

The shop goes a step further. It saves the order before it charges the card. If the card goes through but the follow-up save fails, it refunds the charge through Square's Refunds API. And it checks the signature on each notification Square sends back.

Two smaller details. An event's date is entered once, and that one field drives the events page and the confirmation email, in the venue's own time zone. For table bookings, OpenTable's widget loads with the page and the Reservations button opens its booking window, so guests stay on the site.

The first site went live in March 2026, and both are live now. Since then we've added paid event bookings, printable vouchers and ad tracking, and we host both sites. The owners update their own events, photos and shop. We didn't measure their time before and after, so there's no figure to show you.

If you run a venue and want vouchers, event tickets or pickup orders paid for on your own site, with an editor your staff can use, get in touch.

Guests buy gift vouchers, book paid events and order for pickup on the venues' own sites, paying by card through Square. Table bookings go through OpenTable's widget, opened from each site's Reservations button.

How and why they came

Both venues have the same owners, and we'd worked with them before. They came back with their own page designs: a rebuild of one venue's website and a new website for the second venue. The designs arrived as page layouts and folders of photos, and we built to those.

The problem

They were on WordPress and found it hard work for the things that change often. They wanted to update menus, events and shop items themselves, without waiting on a developer and without a complicated system to learn.

They also wanted a proper gift voucher, with amounts to choose from, emailed to the person receiving it. The second venue wanted a small shop for pickup orders. Table bookings were to stay on their own sites, through OpenTable. Paid event bookings were added after the first site went live.

What we built

  1. 1

    An editor for each site

    Staff log in and change the pages, menus and events. The second site adds a blog, products and orders. To add a photo or a video, they paste a Google Drive link and the site turns it into an image address, or uses Drive's own player for video.

  2. 2
    Resend

    Gift vouchers

    The buyer picks an amount and pays in Square's card form on the site. The server charges the card, gives the voucher a number, a private link and an expiry date, saves it, then emails the voucher to the recipient and a receipt to the buyer. Each voucher has a print page, and staff can mark it used or archive it.

  3. 3
    Resend

    Events

    Staff set a date, the number of places, photos or video, and a booking mode: a waitlist, a free RSVP or a paid booking. For a paid event the server checks there's room, works out the total from the ticket price, charges it through Square, saves the booking with a reference and sends a confirmation. Staff can add a phone booking by hand, resend a confirmation, cancel a booking and export the list.

  4. 4

    A pickup shop on the second site

    Products can have options: a flavour, the number of people, add-ons. The buyer adds them to a cart, picks a pickup date and time, and pays through Square.

  5. 5

    Table bookings

    OpenTable's widget loads with the page, and the Reservations button opens its booking window.

The sites' own screens, on a made-up venue

  • An event's booking mode, places and price per person.

    The system's own output. Sample data.

  • The booking form works out the total before the card step.

    The system's own output. Sample data.

  • A Google Drive link pasted into an image field.

    The system's own output. Sample data.

  • Pickup dates with Today and Tomorrow, and times in fifteen-minute steps.

    The system's own output. Sample data.

What a person still does

The owners write and update the content. Staff see each order in the editor and get it ready for pickup, and they run the events. OpenTable handles the table bookings.

The technical detail

What each system allowed

Square

  • Square's Web Payments SDK puts a card form in the page and produces a single-use payment token, which the site's server sends to Square's Payments API to create the payment.12
  • Square's Refunds API refunds a payment in full or in part.3
  • Square signs each webhook notification with an HMAC-SHA-256 signature made from the subscription's signature key, its notification URL and the request body, and says to check it before trusting the notification.4

OpenTable

  • OpenTable provides an embeddable reservation widget that keeps guests on the restaurant's own site through the booking, rather than sending them to an external page.1
  • Each site loads that widget out of sight and opens its booking window from the site's own Reservations button.

Google Drive

  • The owners keep their photos and videos in Google Drive.
  • The site turns a shared Drive link into a direct image address, and shows video through Drive's own preview player.

Vendor links checked 16 November 2026.

Design decisions

  • The server sets the amount

    The card form only produces a token. The server works out what to charge from its own records: the ticket price times the party size, each shop line priced again from the products table, or the voucher's face value, checked against an allowed range.

  • Save, then charge, then confirm

    The shop saves an order before it charges the card, then confirms it. If the confirm fails after the card has gone through, the server refunds the charge through Square.

  • One date for an event

    The date is entered once, in its own field. That field drives the events page and the confirmation email, in the venue's own time zone.

  • A database each

    Each site has its own Postgres database on Neon, so the two venues' content, orders and bookings are kept apart.

The hard parts

  • Building to someone else's design

    The owners designed both sites. The designs came as page layouts and folders of photos rather than design files, so the build followed the layouts page by page.

  • Pickup times

    Checkout offers exact pickup times in fifteen-minute steps, with Today and Tomorrow shortcuts. The list is worked out from the opening hours, the notice each product in the cart needs, and local time, including the daylight saving changes.

  • An editor simple enough to use

    The brief was content the owners could change without help. Photos and video come in as Drive links, so there's no upload step to learn.

Where it stands

First site live since

March 2026

  • The first site went live in March 2026, and both sites are live.
  • Since then we've added paid event bookings, printable vouchers that staff can mark used or archive, and ad tracking.
  • We host both sites.
  • The owners update their own events, photos and shop items.

We didn't measure the owners' time before and after, so there's no before and after figure on this page.

Questions

Can I sell gift vouchers on my venue's website with Square?

Yes, on this job. Square's card form sits on the site's voucher page. The server charges the voucher's face value, then emails the voucher to the recipient and a receipt to the buyer. Staff can print a voucher and mark it used.

Can guests pay for event tickets on our own website?

Yes. Each event has a booking mode: a waitlist, a free RSVP or a paid booking. For a paid booking the server checks there's room, works out the total from the ticket price, charges it through Square and emails a confirmation with a booking reference.

Can I keep OpenTable and still have guests book on my own site?

OpenTable provides a reservation widget for your own website. On this job the site loads it with the page, and the Reservations button opens its booking window.

Can staff change the menu and events without a developer?

On this job, yes. Each site has an editor behind a login for pages, menus and events, and the second site's editor covers its blog, products and orders too. Photos and videos are added by pasting a Google Drive link.

What stops someone changing the price in the browser?

The browser only sends a one-time card token from Square's card form. The server works out the amount from its own records and asks Square to charge that.

Want vouchers, event tickets or pickup orders paid for on your own site?

Book Free Assessment

Product names and logos belong to their owners and are shown to identify the systems connected.