An Event Services Website That Books and Bills: Payments, Onboarding and Case Studies From a Real Build

Key takeaways

• Event buyers are nervous about one thing: will it work on the day. A supplier's site has to show that it has done an event like theirs, with a full case study per client rather than a logo wall.
• Take the booking and the payment in one step. MyEventWiFi's onboarding forms collect the event details and the payment together, and the payment reference arrives attached to the form submission, so nobody matches payments to events by hand.
• A Webflow form cannot hold a payment secret. A small server function, in this build a Cloudflare Worker, checks the amount and creates the charge, so the price never comes from the visitor's browser.
• Ask only the questions that fit the job. A three-path wizard keeps a small shipped-kit booking short while an enterprise deployment still collects everything the engineers need.
• Bank payments cost far less on big bookings. On Stripe's US pricing page, a $5,000 booking costs about $145 by card and $5 by ACH Direct Debit, because the ACH fee is capped.
• Passing card fees on is regulated. Rules vary by country and US state, card networks set caps, and Australia ended surcharging on eftpos, Mastercard and Visa cards on 1 October 2026. Check where your customers are before you copy any fee pattern.

Who this is for

This is for suppliers whose customers book by the project and pay in sums that matter: event technology, AV, staging, catering, photo and video crews, and similar B2B services. A typical booking is large enough that a payment link in an email feels amateurish, and varied enough that a one-size-fits-all form asks the wrong questions.

The buyer's worry, and what answers it

MyEventWiFi runs the internet behind conferences, trade shows, live sport and broadcasts, from a pre-configured kit shipped to the venue to engineers on site. Its buyers are event producers, marketing teams and broadcast crews, many working for well-known brands. They are used to paying the venue for slow, capped WiFi, and they need to trust a new supplier with the one thing that cannot fail on the day.

For a supplier like this, the question every buyer asks is simple: have you done an event like mine? The site answers it with a full page per client, using the same structure each time:

1. A headline that names the stakes. What had to work, and for whom.
2. A row of facts. The client, the industry and a number that matters, such as bandwidth.
3. The challenge, broken into clear parts. Not a paragraph of praise.

We built five case study pages to one shared structure in Webflow, so a new one can be added by filling in the same sections. See the MyEventWiFi case study for the finished pages. For your own site, the same rule applies to any trade where trust is the product: show a finished job like theirs, in detail.

Build the pages natively, so your team can edit them

MyEventWiFi designed the site, and our job was development: nine pages built natively in Webflow, covering the home page, contact, five case studies and two onboarding pages. Every page was built in Webflow rather than pasted in as code, so the team can change text, images, prices and case studies without a developer. That includes the pricing section and a network test card on the home page that works as a real component rather than a flat image.

It is a point worth making to any agency you hire: ask whether pages will be editable, and by whom, before the build starts.

Stage two: payment inside the booking form

The two onboarding forms, one for shipped kits and one for enterprise events, first collected the event details but not the payment. We added Stripe to both, so a customer can fill in the event details and pay in one step, by card or by bank transfer, or choose to be invoiced. The payment reference always arrives attached to the form submission.

How it works, in plain terms

Webflow cannot run server code or hold a Stripe secret, so the payment runs through a small Cloudflare Worker:

1. The visitor fills in the form with their event details.
2. The form sends the details to the Worker, not to Stripe directly.
3. The Worker works out the amount from your own price list, instead of trusting a number from the browser.
4. The Worker creates the charge with Stripe and returns what the page needs to complete the payment.
5. The payment reference is attached to the form submission, so every payment arrives already matched to its booking.

The principle is simple: the browser never decides the price. A good habit on any build like this is to confirm payment status on the server before marking a booking as paid, and to test in Stripe's test mode before going live.

What a card costs, and what a bank payment costs

Bookings by event suppliers are often large, and card fees grow with the amount. Stripe's US pricing page, read on 17 October 2026, lists 2.9% plus 30 cents for cards and 0.8% for ACH Direct Debit, capped at $5.00. Rates differ by country and by arrangement, so use your own figures. For illustration, on US pricing:

On MyEventWiFi, customers can pay by bank transfer with an instant bank login, with no card fee added, which gives larger customers a cheaper option. ACH is a US bank network, so check which bank payment methods your own country supports.

Passing card fees on: do the legal check first

On MyEventWiFi, the card total is calculated so that, after Stripe's fee, the business receives exactly the amount it quoted. That is one way to handle fees. Before you copy it, check the rules where your customers are, because they vary:

Stripe's documentation says that if you surcharge card payments you must comply with all applicable laws, regulations and card network rules. Stripe's guide also says to confirm the current rules with your state attorney general or a payments attorney, since the landscape can shift.

Practical options that avoid the question:

• Absorb the fee and price it into your quote.
• Offer a lower-cost bank payment and make it the easy option.
• Show the full price up front, with no extras added at the last step.

This is general information, not legal advice.

Stage three: a wizard that asks only what fits

A kit in the post and a team of engineers on site need very different information. We built a multi-step onboarding wizard with three paths. The first answers decide which questions come next, so a small booking stays short and an enterprise deployment collects everything the engineers need.

A useful way to design your own:

Keep each step short, show progress and let people go back. The wizard was approved by the client in September 2026 and is live on the site.

Extras that earn their place

For larger packages, we also built branded login pages for individual events, which is the page guests see when they join the network. MyEventWiFi now offers them as part of its larger packages. Look for the small extras that a supplier can sell once the website can deliver them.

How the work was staged

The work ran in three stages between July and September 2026: the site, then payments, then a smarter onboarding flow. The payment forms have been taking real payments since July 2026, and the wizard went live in September. Staging the work let the client approve each piece in turn and start using it before the next began.

We have not been given booking or revenue figures from MyEventWiFi, so we do not publish any.

A checklist before you add payments to a booking form

Platform and cost notes

This build used Webflow, Stripe and Cloudflare Workers. If you are choosing a platform, our guides to Webflow vs WordPress and Squarespace vs Webflow vs Framer cover the trade-offs, and our guide to Shopify vs WooCommerce covers shops where the cart is the product.

How we work with event and B2B suppliers

At Amariq, the first call is about your goals and how bookings really happen, and the proposal names the platform. For MyEventWiFi we worked from the client's own design and did the development, and we can also design the site. Our Webflow integration service covers Stripe, HubSpot and Zapier connections, and our Webflow development service builds the pages so your team can edit them. From an approved design, a Webflow build of this kind typically runs three to six weeks, and milestones and a delivery date are agreed before work begins.

Frequently asked questions

Can I take payments inside a Webflow form?

Yes, with a small piece of server code. Webflow cannot keep a payment secret or run server code, so a function such as a Cloudflare Worker checks the amount and creates the charge. The payment reference then travels with the form submission, so every payment arrives matched to its booking.

How do you add Stripe to a Webflow form?

The form sends its details to a small server function. The function works out the price from your own list, creates the charge with Stripe and returns what the page needs to finish the payment. Test it in Stripe's test mode first, and confirm payment status on the server before marking a booking as paid.

Who pays the card fee on a booking?

It depends on how you set it up. On MyEventWiFi the card total is calculated so the business receives the amount it quoted, with bank transfer available at no card fee. You can also absorb the fee and price it in. Check the rules where your customers are before adding a fee.

Is it legal to pass card fees on to customers?

It depends on the country and, in the US, the state. Stripe's guide says surcharges are generally permitted in the US with caps and disclosure, prohibited in Connecticut, Maine, Massachusetts and Puerto Rico, and capped by the card networks. Australia ended surcharging on eftpos, Mastercard and Visa cards on 1 October 2026. Check current rules before you add a fee.

Is bank transfer cheaper than card for B2B bookings?

Often much cheaper on large amounts. On Stripe's US pricing page, a $5,000 booking costs about $145.30 by card and $5.00 by ACH Direct Debit, which is capped. Rates and bank payment methods differ by country, so use your own figures.

Why use a multi-step form instead of one long form?

Different jobs need different information. A short first question decides which questions follow, so a small booking stays short and a large one still collects everything the delivery team needs. Shorter steps also feel easier to finish.

What should an event supplier's case study pages show?

A headline that names the stakes, a row of facts such as the client, the industry and a number that matters, and the challenge broken into clear parts. Build every case study to one structure so new ones are quick to add.

Can my team edit the site after launch?

Yes, if it is built natively in the platform. On MyEventWiFi every page was built in Webflow, so the team can change text, images, prices and case studies themselves, including the five case study pages.