Cut your transaction fees to 0%, without losing your sales records

Look at your last payout statement and find the line for transaction fees. That number is what a percentage rate looks like after a month of packages, memberships, drop-ins, and event tickets. Multiply it by twelve.

Most owners have already done this math and arrived at the obvious question: why not have customers pay you directly? Send them your QR code. Give them your bank details. The money lands in your account whole.

Plenty of businesses try exactly that. Then they discover what it costs.

The transaction never appears in their sales records. Nobody gets a receipt. Someone has to activate the package by hand, match the transfer to the right customer, and keep a WhatsApp thread open until it's sorted. What started as a way to protect revenue turns into a second, manual system running beside the first one.

So the choice has always been the same. Keep the fee and keep your records, or keep the money and manage payment yourself.

Manual Payment with Approval removes that choice. Your customers pay you directly through your own QR code, bank transfer, or e-wallet. Rezerv charges nothing on those transactions. And every payment still runs through your booking system with a receipt, an invoice number, a tax line, and a plan that activates when you approve it.

This article covers what manual payment methods do, the controls that keep self-reported payments from becoming a liability, and how different businesses configure them around the way they already collect money.

I. What percentage-based transaction fees actually cost you

Transaction fees are the easiest cost in your business to ignore, because you never write a check for them.

They come out before the money reaches you. There's no invoice, no due date, no moment where you approve the amount. The payout simply arrives smaller than the sale, and you move on to the next thing.

The fee scales with your success, not your usage.

This is what separates transaction fees from every other cost you carry. Rent stays flat whether you sell ten memberships or a hundred. Your software subscription stays flat. Your insurance stays flat.

A percentage rate does the opposite. Sell more, pay more. Raise your prices, pay more. Launch a premium package, pay more on every unit. The better your month, the larger the deduction.

Where it lands in a fitness business:

• Packages and credit packs, often your highest-value single transactions
• Memberships, charged on every renewal for as long as the member stays
• Class drop-ins, where the fee is small per sale and constant across volume
• Appointment bookings, including higher-priced personal training and treatment sessions
• Event and workshop tickets, usually sold in bursts where the total deduction is significant

Run the numbers on a single package. A studio selling a $500 credit pack loses a meaningful slice of it before the money arrives. Sell forty of those in a year and the total is no longer a rounding error. It's a piece of equipment, a month of rent, a part-time salary.

You're already paying for the software.

Here's the part worth sitting with. You pay a monthly or annual subscription for your booking platform. That subscription is the price of the product: the scheduling, the customer records, the class timetable, the reporting, the app your members use.

Then a percentage of every sale goes to the same platform on top of it.

Two separate charges for one product. The subscription covers the software. The transaction fee is a second bill that arrives automatically, sized by how well your business performs, for the same thing you already bought.

Payment processors are a different case. They charge because they're doing real work: moving money, handling card networks, absorbing chargeback risk. That's a service with a genuine cost behind it, and every business that accepts cards pays some version of it.

The platform layer sits on top of that. It's revenue tied directly to yours, collected on sales you generated, through software you're already subscribed to.

Which explains why a feature like this is uncommon in the category.

A platform earning a percentage of your revenue has no reason to build the tool that eliminates its own percentage. Removing the fee means removing the income. The incentive points the other way, and product roadmaps follow incentives.

Rezerv charges a subscription and stops there. Manual payments carry no transaction fee, which is the position a platform can take when the subscription is the whole business model.

That's the gap worth understanding before you look at the alternative. The cost stays out of sight because everyone who collects it benefits from your not looking at it too closely.

II. Why the fee has been treated as unavoidable

Most gym owners have already thought about taking payments directly. The idea comes up every time someone looks at a payout statement. It usually gets abandoned within a week of trying.

Understanding why it failed is the key to understanding why this feature works.

1. Booking software is built around a single payment path.

In most platforms, checkout means one thing: the customer enters card details, the payment routes through a connected gateway, and the software marks the sale as complete. The transaction record, the receipt, the package activation, and the sales report all depend on that gateway confirmation.

The system is designed to trust the gateway. Nothing else counts as payment.

So when a customer says they'd rather transfer the money to your bank account, there's no place to put that. The software has no way to record a payment it didn't process.

2. Working around it means leaving the system.

Here's what actually happens when a studio decides to accept a bank transfer or other manual payment methods

• The sale exists in your bank account and nowhere else.
• Your sales records show nothing. The transaction never happened as far as your software is concerned, so your revenue reporting is now wrong by exactly the amount you just collected. Every report you run from that point forward understates what your business actually earned.

• The customer has no receipt.
• No invoice number. No tax line. No record in their billing history they can look up later. When they ask for proof of purchase at tax time or for a corporate reimbursement, you're generating it by hand.

• Someone has to activate the plan manually.
• The package doesn't credit itself. The membership doesn't start. Someone on your team opens the customer's profile and adds it, which means someone has to remember, and remember accurately, and do it before the customer shows up for their next class.

• Verification lives in a chat thread.
• The customer sends a screenshot of their transfer. Your team checks the bank account, or means to, or checks it tomorrow. If the screenshot is blurry, that's another message. If the amount is short, another. If the transfer came from a family member's account under a different name, you're now matching a payment to a person by guesswork.

• Nobody can tell which payment belongs to which customer.
• Five transfers arrive on Tuesday. Three are for packages, one is a membership renewal, and one you can't place at all. The bank statement shows amounts and names, not what anyone bought. Matching them takes someone sitting down with two screens open.

• Each of these is small. Together they're a second system.
• You now run payments in one place and everything else in another, held together by a person who remembers to connect them. That works at five transactions a month. At fifty it becomes someone's job, and the wage costs more than the fees you were avoiding.

3. The admin cost quietly replaces the fee you saved.

A studio doing S$30,000 a month saves around S$1,000 by taking payments directly. If that creates several hours a week of receipt chasing, cross-checking, and manual entry across your team, you've converted a clean automated cost into a messy manual one.

Worse, you've moved a business-critical process out of your software and into someone's memory. Software doesn't forget to activate a package. People do, especially during a busy Saturday morning.

4. The fee was never really the problem.

The problem was that saving the fee meant giving up the transaction record.

You lost the automatic activation. You lost the audit trail. You lost the receipt, the tax record, the sales report line, and the customer's billing history. You traded a clean system for cheaper money.

So the trade has always been the same. Keep the transaction fee and keep your records intact, or keep the full payment and take on the manual work of running payment yourself.

Manual Payment with Approval exists because that trade was never necessary. The money can move outside your platform while the record stays inside it.

III. What Manual Payment with Approval is

Manual Payment with Approval adds your own payment channels to Rezerv checkout as a selectable option, alongside the payment gateways you already run.

Your customer chooses it, pays you directly through your QR code, bank transfer, or e-wallet, and submits proof or a reference. You review the submission and approve it. Rezerv records the transaction, issues the receipt, and activates the plan.

The money never touches a processor. The record never leaves your system.

Rezerv charges nothing on these transactions.

Open any approved manual payment in your Sales Transactions and look at the payment details. Alongside the tax and the amount, there's a line marked Fee. On a manual payment it reads zero, and the net matches the amount in full.

That's the whole claim, visible on the record itself. Whatever your customer pays, you receive. The only costs that apply are whatever your own bank or e-wallet charges you, which is between you and your bank.

It appears at checkout as a normal payment option.

Your customer sees it in the same list as Stripe, Fiuu, or any other gateway you've connected. They select it and the option expands to show whatever you've configured: your QR code at full size for scanning, the payment instructions you've written, and any fields you're asking them to complete.

They pay, they submit, and they land on a confirmation page telling them the payment is under review. Nothing about the flow asks them to leave, message you, or handle payment separately from booking.

It works across everything you sell.

• Packages and credit packs
• Memberships, including one-time membership purchases
• Class drop-ins
• Appointment bookings
• Event and workshop tickets

Any service you sell through Rezerv can accept manual payment at checkout.

You can run more than one.

Each manual payment method is configured on its own, with its own name, its own instructions, its own uploaded image, and its own rules. A studio might run a PayNow QR alongside a bank transfer option and a pay-at-counter method, each behaving differently.

Name them whatever your customers will recognize. Bank Transfer, PayNow QR, QRIS, Charge to Room, Pay at Counter. The name you enter is the name they see.

The transaction record stays complete.

This is what separates the feature from collecting payment off-platform. An approved manual payment carries everything a gateway payment carries:

• Transaction number and invoice number
• Receipt number, issued to the customer on approval
• Tax lines calculated the same way as any other sale
• Customer, item, location, and amount
• Payment method name and a source marked as Manual Payment

Your revenue reporting stays accurate. Your customer's billing history shows the purchase alongside every other transaction they've made with you. The package credits itself when you approve it.

Your customer tracks it without asking you.

While a payment is under review, it sits in the customer's Billing under Payment Due with a Pending approval status. They can open it, see the proof they submitted, and confirm it's with you.

When you approve, they receive an email notification and the transaction moves into their Transaction History marked Paid, sitting in the same list as every card payment and cash transaction they've ever made.

Nobody has to message anyone to find out where a payment stands.

IV. The controls that make self-reported payment safe

Direct payment carries one obvious risk. Your customer tells you they've paid, and until you check your bank account, that's all you have.

The controls in this section exist to close that gap. They sit under Get full control over manual payments when you create or edit a manual payment method, and each one is set per method, so a bank transfer option can behave differently from a pay-at-counter option.

1. Require manual payment approval

The foundation. With this on, a manual payment submission is recorded as pending rather than paid. Nothing settles until a person confirms it.

The transaction sits in your Sales Transactions with a Pending approval status. The customer sees the same status in their billing. Neither the sale nor the plan is treated as complete until you approve.

Turn it off and manual payments record immediately without review, which suits businesses collecting payment in person where the money is already in hand.

2. Auto-reject if not approved within

A time limit on unreviewed submissions. Choose 6, 12, 24, 48, or 72 hours, or Never.

This protects you from the slow failure mode, where a submission sits in the queue for a week because the person who checks the bank account was away. The window closes the transaction automatically instead of leaving it open indefinitely.

Set it against your actual review rhythm. A business checking payments twice a day can run a tight window. One that reconciles weekly should choose Never and manage the queue directly.

3. Allow plan usage before payment is approved

Whether the customer can start using what they bought while you verify it.

Enable it and the package credits or membership become usable immediately after submission. The customer buys a credit pack at 9pm, books a class for the morning, and you approve the payment when you check the bank at 10am.

Disable it and the plan stays inactive until you approve. The purchase exists, the customer can see it, and nothing is usable until the money is confirmed.

4. Allow check-in before payment is approved

A separate permission covering physical attendance. Enable it and the customer can check in to a class while their payment is still under review.

These two controls work independently. A studio can let customers hold a booking without letting them attend, or let them attend without activating a full package. Set them according to how much exposure a single unapproved session actually represents.

5. Enable proof of payment upload

Requires the customer to attach a receipt, transfer slip, or screenshot at checkout. Accepted formats are JPG, PNG, and PDF, up to 3MB.

The file attaches to the transaction record. When you open the payment to review it, the proof is there under Payment submission with a View File link. You check the document and the bank in the same sitting, without hunting through a chat thread for the screenshot.

6. Custom input text field

A single text field where you collect whatever identifier your reconciliation actually needs. You write the label, and the label you write is what the customer sees.

A bank transfer method might ask for a Transaction ID, so matching a payment to your statement takes seconds instead of guesswork. A hotel offering fitness classes might ask for a Room Number, which turns the field into the entire submission. Others ask for the sender's account name, since transfers often arrive under a family member's name.

The Required checkbox controls whether the customer must complete it before proceeding.

7. Enable payment option for customer

Controls whether the method appears at checkout at all. Turn it off to keep a method configured without exposing it, which is useful for options handled in person or reserved for specific situations.

Methods can also be deactivated from the list without being deleted, so a seasonal or event-specific option stays ready for the next time you need it.

Where the work actually happens

Every pending submission surfaces in two places.

Your Sales Transactions page lists them with a Pending approval status alongside every other sale, filterable so you can isolate them.

And your dashboard shows a Pending approvals counter at the top of the page, next to overdue payments, the moment your team logs in.

Opening a pending payment gives you the proof file, any custom field values, the amount, the customer, and the item, on one screen. You confirm the money against your bank and approve.

Approving is recorded and attributed. The transaction timeline logs the approval with a timestamp and the name of the staff member who made it. That attribution is what makes it safe to delegate this to your front desk or accounts team.

Approving marks the transaction paid and activates the associated plan, and it can't be undone, which is why the record of who did it matters.

V. What happens when a payment isn't right

Some submissions won't hold up. The receipt is unreadable, the amount is short, the transfer never arrived. This is the part owners assume gets messy, because in the WhatsApp version it always does.

Declining a payment in Rezerv is a structured action. You select a reason, write a note, and decide whether the customer gets another attempt.

The six reasons

When you decline, you choose from a fixed list:

• Unclear proof of payment
• Incorrect additional information
• Mismatched payment amount
• Payment not received
• Fraud suspicion or irregular activity
• Others

These split into two groups, and the split matters more than the labels.

• Correctable submission problems. Unclear proof, incorrect additional information, and mismatched amount all describe a customer who probably paid and got something wrong on the way. A blurry screenshot. A mistyped transaction ID. A transfer short by the amount their bank charged.

• Substantive payment problems. Payment not received and fraud suspicion describe a different situation. The money isn't there, and no amount of resubmitting will change that.

Which group you're in determines the next decision.

The note reaches the customer

Below the reason is a Notes field, up to 250 characters. Whatever you write here appears to the customer directly, in their billing, next to the declined transaction.

Use it for the specific fix. "Please upload your receipt again, the image is blurred" tells someone exactly what to do. "Declined" tells them to message you.

This field is what removes the follow-up conversation. The reason travels with the request to correct it, so nobody opens a chat thread to explain what went wrong.

The note stays editable on the transaction record afterward if you need to revise it.

Hold pricing plan and allow customer to resubmit proof of payment

The checkbox that decides what a decline actually means.

• Leave it unchecked and the decline is final. The transaction closes and the associated pricing plan is deactivated. Any bookings made against that plan are cancelled. This is the right action when the payment genuinely isn't coming.
• Check it and the plan is held rather than cancelled. The transaction stays open, and the customer is prompted to try again. Their package survives the decline, their bookings survive with it, and they get a second attempt at submitting proof.

For the three correctable reasons, checking this box is almost always the right call. The customer paid you. They just sent a bad photo of it.

What the customer sees

The declined transaction stays in their Payment Due list with an Action required status and a Review Payment button.

Opening it shows them the full picture: their original proof file, the custom field values they entered, the reason you selected, and the note you wrote. Below that is a Resubmit Proof action.

The resubmit form arrives pre-filled with what they submitted before. They can delete the original file and attach a new one, and any custom field carries over so they aren't retyping a transaction ID. They submit, and the payment returns to your queue as pending.

The audit trail holds all of it

Every step lands on the transaction timeline with a timestamp and a name.

Payment started. Payment declined, with the staff member who declined it. Proof resubmitted. Payment approved, with the staff member who approved it.

The reason and note stay visible on the record alongside the original proof file and the replacement. Months later, anyone reviewing that transaction can see what was submitted, what was wrong with it, who decided, and what fixed it.

The correction loop stays inside Rezerv from start to finish. No screenshots forwarded to a manager, no chat thread to scroll back through, no reliance on someone remembering why a payment was held up in March.

VI. Four ways businesses set this up

The controls combine differently depending on how money actually reaches you. These four configurations cover most fitness and wellness businesses.

1. QR code studio

The common setup for markets where QR payment is standard. PayNow, QRIS, PromptPay, GCash, and their equivalents.

You upload your QR code to the payment method, write short instructions in the additional details field, and require proof of payment. The customer scans, pays, screenshots the confirmation, and uploads it at checkout.

Configure it as:

• QR code uploaded to the method
• Require manual payment approval on
• Proof of payment upload on
• Auto-reject set to match how often you check your account

The decision worth thinking about is plan usage. QR payments settle instantly, so the money is usually in your account before you look. Allowing plan usage before approval costs you very little and removes the wait entirely for the customer.

2. Bank transfer with a reference

Bank transfers arrive without context. Your statement shows an amount and a sender name, which may not be the customer's name at all.

The custom input text field solves this. Label it Transaction ID or Reference Number, mark it required, and ask for the number their banking app returns after the transfer. Now every submission carries the exact string you'll find on your statement.

Configure it as:

• Bank details written into the additional details field
• Proof of payment upload on
• Custom input text field on, labeled for the reference, marked required
• Require manual payment approval on

Transfers take longer to clear than QR payments, especially across banks or over a weekend. Consider holding plan usage until approval, and set a longer auto-reject window so a slow transfer doesn't close a legitimate sale.

3. Hotels and add-on services

A different pattern entirely. The guest isn't paying now. They're booking a yoga class, a spa treatment, or a fitness session that gets charged to their room and settled at checkout.

Here the custom field becomes the whole submission. Label it Room Number, mark it required, turn proof of payment off, and skip the QR code. There's nothing to pay and nothing to prove.

Configure it as:

• No uploaded image
• Proof of payment upload off
• Custom input text field on, labeled Room Number, marked required
• Require manual payment approval on
• Allow plan usage and check-in on, so the guest can attend

Approving here means something different. You're confirming the booking is legitimate and recording the charge against a room. The room number sits on the transaction record, so your front desk has a clean list of what to add to each folio at checkout.

The same pattern works for corporate accounts, insurance-funded sessions, and any arrangement where you bill after the fact.

4. Pay at counter

For in-person payment. Cash, a card terminal you own, or any settlement that happens at your front desk.

The customer books online and selects Pay at Counter. Nothing is collected at checkout. When they arrive and pay, your team approves the transaction and the plan activates.

Configure it as:

• Proof of payment upload off
• Custom input text field off, or used for a staff note
• Require manual payment approval on
• Allow plan usage off, so the booking holds without the package activating
• Allow check-in on if you want them able to attend and settle at the desk

This turns a manual payment method into a booking-now, pay-later option that still produces a proper transaction record and receipt.

Running them together

None of these are exclusive. A studio can offer a QR method and a bank transfer method side by side, each with its own rules, and let customers choose. A hotel gym can run a room number method for guests alongside a QR method for walk-ins.

The customer sees whichever methods you've enabled for checkout, listed alongside your payment gateways. Each one behaves according to its own configuration.

VII. When a payment gateway still makes sense

Manual payment is a strong option. It isn't the answer to every transaction, and treating it that way will cost you somewhere else.

Here's where a gateway earns its fee.

1. Recurring memberships

Automatic renewal is the clearest case. A card on file charges itself every month with no action from the member and no action from you.

Manual payment requires a fresh submission each cycle, which means asking your members to remember, and following up with the ones who don't. For a monthly membership base of any size, the collections work outweighs the fees you'd save.

Recurring revenue depends on the payment being effortless, and gateways make it effortless.

2. Customers who can't reach your local payment channels

A local QR code works for local customers. Someone booking from overseas, buying a workshop ticket from another country, or visiting on holiday may have no practical way to use it.

International bank transfers carry their own fees, take days, and arrive short. A card gateway handles all of this without either party thinking about it.

3. High volume, low value transactions

Every manual payment costs someone a minute of attention. Open the transaction, check the proof, confirm the bank, approve.

On a $500 package that minute is well spent. On a $15 drop-in sold forty times a week, the review time becomes real staffing cost, and the fees you avoided end up smaller than the wages you spent avoiding them.

Do the arithmetic on your own numbers. Manual payment pays off most clearly on high-value transactions and least clearly on high-frequency small ones.

4. When nobody is available to approve

Approval requires a person. If your business runs unmanned hours, or a single owner handles everything and travels, submissions will sit in the queue.

The plan usage and check-in permissions soften this by letting customers proceed while they wait. They don't remove the underlying requirement that someone eventually reviews the payment.

5. Run both and route deliberately

Manual payment methods sit alongside your gateways at checkout, which means this was never a single choice.

A practical split for most studios:

• Gateways for recurring memberships, international customers, and small drop-ins
• Manual payment for packages, credit packs, high-value plans, event tickets, and any sale large enough that the percentage genuinely matters

Every sale you move to manual payment is a sale that costs you nothing in transaction fees. Choose the ones where the saving is worth a minute of review, and let the gateway handle the rest.

VIII. Why payment fees matter when choosing fitness booking software

Most software comparisons happen on the pricing page. You line up the monthly subscriptions, weigh the feature lists, and pick the one that fits your budget.

The subscription is the advertised number. The transaction fee is the one that shows up later, and for a growing business it's usually the larger of the two.

Work out the real annual cost

The calculation takes a minute:

Annual subscription + (transaction fee percentage × annual revenue processed) = what the software actually costs you

A studio processing $200,000 a year through a platform charging 2% on top of processor fees pays $4,000 in transaction fees. Against a subscription of a few thousand dollars, the fee is the bigger line.

Now grow the business. Double the revenue and the subscription stays flat while the fee doubles. The cheaper-looking platform becomes the expensive one, and the crossover happens quietly, without any renegotiation or notice.

The comparison flips as you scale

A low subscription with a percentage attached is genuinely cheaper when you're small. Early on, a percentage of very little is very little.

A higher subscription with no transaction fee is a fixed cost you can plan around. It costs the same in your best month as your worst, and every dollar of growth stays with you.

Which model wins depends on where your business is heading rather than where it is now. Software decisions are sticky, so the number that matters is what the platform will cost you in three years at the revenue you're aiming for.

The gap between rates is easy to underestimate

Two platforms might quote 3.6% and 2.5%. On paper that's a difference of just over a percentage point, which sounds like something you'd absorb without noticing.

Run it against an actual month of memberships and the number stops being abstract. Below is that comparison using published rates from Rezerv and Vibefam, two platforms serving the same fitness and wellness market. Substitute whatever your current platform charges and the shape of the result holds.

What the difference looks like in real numbers

The scenario

A business with 300 members paying an average of S$150 per month by credit card.

That's S$45,000 in monthly card revenue across 300 transactions.

Step 1: What each platform charges per transaction

A difference of S$2.25 on a single membership charge. Small on its own.

Step 2: Multiply by 300 members

You save S$675 every month. That's S$8,100 a year.

That's the difference from card rates alone, before manual payment enters the picture.

Step 3: Move some members to manual payment

Everything covered earlier in this article applies here. Manual payment means your member pays you directly through your own QR code, and Rezerv takes nothing. Zero fee, on every transaction that uses it.

Say half your members switch. Your 300 transactions now split:

The full comparison

Total saved: S$1,267.50 every month. S$15,210 a year.

Two things worth noting

• The savings scale with how much you shift. Half your members is a conservative assumption. Move your packages and high-value plans to manual payment, where a single transaction carries the biggest fee, and the annual figure climbs from here.
• This covers card processing only. It doesn't include what you save on add-on costs, app pricing, door access pricing, or Vibefam's separate AI dashboard fee.

Questions worth asking any platform

That S$15,210 gap comes from two things: a lower card rate, and a payment method that costs nothing at all. Neither appears on a feature list, and both are visible only if you ask directly.

Before you commit, get clear answers on:

• Is there a platform transaction fee on top of what the payment processor charges?
• Does it apply to packages, memberships, drop-ins, appointments, and event tickets equally?
• Does it apply to membership renewals every cycle, or only the first charge?
• Does the percentage change at higher subscription tiers?
• Is there any way to accept payment without the platform taking a percentage?

That last question is the revealing one. A platform with a genuine answer has built something that reduces its own revenue, which tells you where its incentives sit.

Incentive alignment is the underlying issue

A platform earning a percentage of your sales has revenue tied to your volume. That sounds aligned until you notice it holds whether or not your business is profitable. Your margins can compress while the percentage keeps collecting.

A platform charging a subscription earns the same whether you have a strong month or a quiet one. It has to keep you by being worth the subscription, which means competing on the product rather than on your transaction volume.

What this means practically

Manual payment methods let you route sales around the fee entirely. High-value packages, credit packs, and event tickets can be collected directly at 0%, while your gateway handles recurring memberships and card payments.

Rezerv charges a subscription and takes nothing on manual payments. The fee line on those transactions reads zero, and the full amount your customer pays reaches your account.

For a business selling packages and memberships at any real volume, that difference compounds year over year in a way the pricing page never shows.

Cheers, Friska 🐨

Set up manual payment methods in Rezerv

Adding a manual payment method takes a few minutes. You name it, upload your QR code or write your payment instructions, choose which controls to turn on, and save. It appears at your checkout immediately.

Everything after that runs where your team already works. Pending approvals show up on your dashboard and in Sales Transactions, and approving a payment activates the plan and issues the receipt in one action.

The step-by-step lives in our support center, where you'll find how to:

• Create and configure a manual payment method
• Set approval rules, auto-reject windows, and usage permissions
• Review, approve, and decline payment submissions
• Handle resubmissions and read the transaction audit trail

Visit the support center to set up manual payments →

Manual Payment with Approval is included for businesses on the Business tier. If you're on Starter or Team, reach out via live chat in your business portal and our team can add it to your account.