Home/Resources

SevenRooms & CRMMarch 202610 min read

SevenRooms Paylinks: remote payment, Apple Pay and chargebacks

Send a Paylink, what Apple Pay and Google Pay cover, Charge & Save Card, how to handle a chargeback and limit disputes: the guide to remote payment on SevenRooms.

Casa Yuma's terrace at dusk

A guest books by phone for eight people on a Saturday night. You want a deposit, without making them read out their card number. With SevenRooms Paylinks, you send a secure link, the guest enters their own card and the reservation updates itself. Then comes the question every restaurateur ends up asking: what if that guest disputes the charge with their bank three weeks later? That is a chargeback, and it is handled outside SevenRooms.

This guide covers remote payment from start to finish. Whenever a feature depends on your payment processor, your country or your package, we say so plainly.

A Paylink is a secure payment link, sent to the guest by email, text message or both, so they can save their card or pay an amount without reading anything out loud. According to SevenRooms, it is PCI-compliant, 3D Secure-enabled (strong customer authentication, "in applicable regions") and hosted by SevenRooms: card details never travel in an email or a text.

Once the card is entered, you can charge it immediately (prepayment, deposit, ad hoc purchase), hold it for up to seven days before charging, or save it for late-cancellation or no-show fees.

Use cases listed by SevenRooms: a reservation taken by phone or email that requires a deposit or card guarantee, a payment required by a Shift or an Access Rule, a friend or relative who wants to buy something for a guest, a private dining or large-party deposit, countries where 3D Secure is mandatory.

Prerequisite: a payment processor connected to SevenRooms. Stripe is the preferred processor (Settings > Integrations > Payment Gateway; another source says "Payment Processors", so the label may vary). Paylinks are supported by all SevenRooms payment processors (Stripe, Adyen, FreedomPay, CyberSource, SaferPay, Shift4, and Network International in the UAE only). Availability, setup time and fees depend on the processor, your region and your contract.

The māhie tip: before talking Paylinks, we check that your processor and payment settings hold up. We audit and configure SevenRooms end to end, from Shifts to the texts your guests receive.

You create the Paylink from the reservation, choose the delivery method, and the reservation moves to Booked as soon as the guest has paid. The sources describe behaviour more than exact clicks, so button labels may vary.

  1. Create or edit the reservation. You can choose the delivery method there. On an existing reservation, the Paylink is added by editing the Payment section.
  2. Set the amount and the delivery method: Email, Text or Email & Text. For texts, SevenRooms validates the phone number before sending.
  3. Optionally add a payment deadline (see below) and a note to the guest.
  4. The guest opens the link, reviews the reservation, enters their card and completes authentication if required. The reservation updates automatically.
  5. If a payment is processed, they receive a Transaction Alert email with an itemized receipt.

Useful settings:

  • Message wording: Settings > Guest-Facing Language > Emails > Paylink Request.
  • Default delivery method: General Venue Settings > Charges, which you can override Paylink by Paylink.
  • Resending: the Resend option is available at any time from the reservation, including to someone other than the guest.
  • Team alerts: in Profile, enable "Notify me of payment or credit cards received via Paylink on reservations I'm following".

Auto-Cancel Paylinks: stop chasing by hand. Enable them in Venue Settings → Credit Card Collection Options. A reservation with a Paylink starts in Hold status. If the guest pays, it moves to Booked (or Confirmed, depending on your auto-confirm settings). If not, it is cancelled when the deadline you chose expires, even if you had marked it Confirmed in the meantime. The guest gets reminders 12 hours and 1 hour before expiry, then the standard cancellation email. Not available for Nightlife venues.

Fictional example: a restaurant in Lyon takes a party of 8 by phone, with a €20 tax-inclusive deposit per guest. The host sends a Paylink by text, expiring in 24 hours: the guest pays and the table goes from Hold to Booked.

Common mistake: if your emails are translated (Guest-Facing Language), translate the Paylink fields too, or your international guests get a message in the wrong language.

Apple Pay and Google Pay on SevenRooms: what depends on your processor

Apple Pay and Google Pay are offered whenever a payment or a card is requested, but the sources only document them for Stripe and FreedomPay. For Adyen, CyberSource, SaferPay or Shift4, nothing is stated: ask SevenRooms to confirm.

They appear for a deposit, but also for a simple card on file with no charge.

  • Stripe: Reservation Widget (all versions), Events Widget, Paylinks, Online Ordering. Enabled automatically.
  • FreedomPay: Reservation Widget (new version only), Events Widget, Paylinks, Online Ordering. The HPC integration is required: they are not available with FreedomPay Freeway.

What you need to do

  1. Stripe: in the Stripe Dashboard, on the Payment method domains page, add www.sevenrooms.com (and eu.sevenrooms.com if you are on the European server), then Save.
  2. FreedomPay: raise a ticket with FreedomPay support to have these domains added as trusted domains for your store IDs.
  3. Widget embedded on your site or custom iFrame: for Google Pay, the page's Permissions Policy must allow "Payment". For Apple Pay, also register the domain of your website (with Stripe, or by ticket with FreedomPay).

A guest cannot see Apple Pay? It shows on iPhone or in Safari on Mac; Google Pay on Android or in Chrome, with a card saved in the guest's wallet. Your fees and payouts do not change: these payments are treated like ordinary card transactions.

The māhie tip: if your booking widget is embedded on your site, we test the journey on iPhone and Android. One forgotten domain is enough to make Apple Pay disappear. We connect the widget to your site and check these settings.

Charge & Save Card: charge at booking and keep the card

Since July 2026, a card charged at booking is also saved on the reservation, so your team can charge it again manually. Before, you had to choose between charging and saving the card.

  • On by default for all venues, on all processors.
  • To turn it off: Settings > Venue Settings > Charges > Charge and Save Card, by unchecking the option. The card is then charged without being saved.
  • No automatic later charge: any new charge is manual. SevenRooms says it is working on automatic charging, with no date.
  • The card stays usable for up to 7 days after the reservation, then it is purged: you must then send a Paylink.

Saved card or Paylink? SevenRooms' rule: charge the saved card if you are speaking to the guest or if the fee comes from a policy accepted at booking (no-show, late cancellation). Send a Paylink if there is no card, if the guest wants to pay with another card, or if the payment was not agreed at booking.

State in Settings → Guest-Facing Language → Policies that the card is kept. It is not mandatory (SevenRooms' legal text already covers saving), but according to SevenRooms it reduces disputes. For deposit and card-guarantee settings, see our guide to deposits, card guarantees and prepayment.

SevenRooms chargebacks: how a dispute works and what to do

A chargeback is a dispute: the guest asks their bank to reverse a charge, and your merchant account is debited the amount, plus any fees, before you can defend yourself. SevenRooms describes it as normal with card payments, as long as they stay under 1% of your processor's transaction volume.

How it unfolds:

  1. The guest disputes the charge with their bank.
  2. The bank presumes the request legitimate. The dispute is reported to the card network and to your processor, who notifies you.
  3. Your merchant account is debited (any fees depend on your agreement).
  4. It is up to you to dispute it, if you think it is unfounded.

What to do

  • Respond to every chargeback. This is SevenRooms' most insistent instruction.
  • Read the reason, find the transaction in SevenRooms and decide whether the dispute is valid.
  • Never refund the guest directly: the dispute already refunds them, and a further refund would give them double.
  • If the dispute is unfounded, build your file according to the reason. SevenRooms' example: for a disputed cancellation or no-show fee, provide the cancellation policy and proof the guest agreed to it. Submit it through your processor's process.
  • Wait a few weeks. If you win, the amount returns to your merchant account; if you lose, nothing changes.

If you do not respond, chargebacks are reported to the card networks. Near 1%, your processor contacts you; at 1% or more, your merchant account may be closed.

SevenRooms does not record chargebacks: you track and manage them in your processor's portal. The procedure, deadlines and accepted evidence therefore depend on the processor and your country. SevenRooms' Chargebacks FAQ dates from 2023: for a real case, follow your processor's current documentation.

With māhie: we train your teams in the "don't refund, answer on time" reflex and prepare the standard file: policy in force, proof of acceptance, exchanges with the guest. We also audit your settings so the proof exists on the day of the dispute.

Limiting chargebacks: cancellation policy, Cancellation Fee Studio and reminders

The best defence is a guest who knows exactly what they pay, when and under what conditions. SevenRooms' best practices:

  • A recognisable bank statement descriptor (set with your processor).
  • A clear cancellation policy, with mandatory acceptance: it is also the centrepiece of your file.
  • Prompt refunds: a direct conversation keeps the guest from going to their bank.
  • A deposit or prepayment explained simply: an unexpected charge triggers disputes.
  • Regular monitoring of disputes to spot recurring reasons.

Cancellation Fee Studio: test fees before applying them. This report (Reporting category, Revenue Management section of the help centre) exists only on select packages: if you do not see it, your package may not include it. It charges nothing: it simulates the impact of late-cancellation fees on your past cancellations, with two settings, Hours in Advance of Reservation Time to Charge Fee (default 24 hours or less) and If Cancellation Fee Per Person (the amount to test). Filters: Reservation Date, Day of Week (the reservation's day, not the cancellation's) and Party Size.

Fictional example, to understand the calculation: if 10 parties of 4 were cancelled less than 24 hours before, a €15 per-person fee would represent 10 × 4 × €15 = €600. This is not a promise of results.

Calibrating to demand. Read our article on payment policy by demand level (Smart Payment & Policy, in beta according to SevenRooms).

Reminding by message. SevenRooms already sends Paylink reminders. Heep integrates with SevenRooms for the rest: a reminder the day before on WhatsApp (SMS fallback), follow-ups, replies to guests. Paylinks are still generated in SevenRooms.

Is a SevenRooms Paylink secure, and does it work with every processor?

According to SevenRooms, it is PCI-compliant, 3D Secure-enabled in applicable regions and hosted by SevenRooms. It is supported by all SevenRooms payment processors.

Do Apple Pay and Google Pay work with my processor?

They are documented only for Stripe and FreedomPay. With FreedomPay, the HPC integration is required: Freeway does not support them. For other processors, the sources say nothing: ask SevenRooms to confirm.

What should I do if a guest disputes a charge with their bank?

Always respond, without refunding directly. Gather the cancellation policy and proof of acceptance, then submit the file through your processor: SevenRooms does not record chargebacks.

How long can I charge a saved card?

Up to 7 days after the reservation. After that, the card is purged automatically and you must send a new Paylink. No later charge is automatic today.

A well-configured remote payment flow secures your bookings without weighing down the guest journey. Badly configured, it leaves tables in Hold and disputes without proof. For your payments, we can:

  • audit your settings: processor, Charges, Paylinks, Auto-Cancel, policies and the texts your guests receive;
  • configure Apple Pay and Google Pay on your widget and your site, and test the journey on mobile;
  • define your cancellation policy and fees, with Cancellation Fee Studio if your package includes it;
  • train your teams to choose between a saved card and a Paylink, and to react to a chargeback;
  • connect Heep for reminders and replies to guests by message.

Want to make your payments more reliable? Explore our SevenRooms expertise or Contact māhie: we will review your setup together.

Corentin
CorentinFounder of māhie