SevenRooms is more than a restaurant reservation system. For many hospitality businesses it sits between bookings, guest data, deposits, prepayments, payment processing and the venue's wider EPOS environment.
That means choosing a payment provider for SevenRooms is not simply a question of comparing card-processing rates.
A restaurant may need the payment setup to support:
- booking deposits;
- full prepayments;
- card-on-file;
- no-show or late-cancellation charges;
- restaurant experiences and events;
- refunds;
- multiple venues;
- international cards and currencies;
- EPOS integration;
- settlement reporting; and
- reconciliation against reservations and final restaurant bills.
The first question should therefore be:
Which payment providers can support the SevenRooms setup the restaurant actually needs?
Quick answer: which payment providers integrate with SevenRooms?
SevenRooms currently lists the following payment processors within its account setup documentation:
- Stripe;
- FreedomPay;
- Network International;
- Cybersource;
- Adyen; and
- Shift4.
Availability can vary by country, payment functionality and the restaurant's individual setup.
A business should therefore confirm compatibility before changing acquirer, gateway or merchant account rather than assuming that any provider using one of these technologies can automatically be connected.
What is SevenRooms?
SevenRooms is a hospitality CRM, reservation, waitlist and guest-management platform used by restaurants, hotel food and beverage operations, nightlife businesses and other hospitality venues.
Its functionality can include:
- online reservations;
- waitlists;
- table management;
- guest profiles;
- CRM;
- marketing;
- restaurant experiences;
- event bookings;
- deposits and prepayments;
- payment-provider integrations;
- EPOS integrations; and
- APIs and wider restaurant-technology integrations.
This makes the payment decision more important than it might initially appear.
The restaurant is not simply choosing how to take a card payment. It may be choosing part of an interconnected hospitality technology stack.
SevenRooms is now part of DoorDash
DoorDash completed its acquisition of SevenRooms in June 2025.
The stated aim was to connect SevenRooms' reservations, CRM and guest-experience capabilities with DoorDash's wider restaurant commerce platform.
That relationship has developed further during 2026.
DoorDash introduced DashOS in September 2026 as a restaurant growth platform connecting areas including:
- DoorDash Marketplace;
- direct ordering;
- reservations;
- loyalty;
- guest management; and
- marketing.
This is strategically important for restaurant groups because booking, ordering, guest data and payments are increasingly becoming connected rather than separate technology decisions.
However, businesses should distinguish between functionality that is available now and DoorDash's future product roadmap.
Do restaurants still own their SevenRooms guest data?
SevenRooms has stated that restaurants continue to own and control first-party guest data collected through their own channels following the DoorDash acquisition.
This includes data from channels such as the restaurant's own SevenRooms booking widget and other supported first-party reservation integrations.
For restaurant groups assessing SevenRooms as part of a wider technology strategy, data ownership, system access and portability should still form part of the commercial and technical review.
How do payments work with SevenRooms?
SevenRooms does not mean that the restaurant no longer needs a payment provider.
SevenRooms' own onboarding information states that businesses need an account with a supported payment provider before integrating payments.
A typical journey might therefore look like:
Guest → SevenRooms → Payment Provider / Gateway → Acquirer → Merchant Account → Settlement
The exact structure will depend on the selected payment provider.
The payment integration can then support functionality connected with reservations, experiences and other hospitality transactions.
Taking restaurant deposits through SevenRooms
Booking deposits are one of the clearest reasons restaurants need their reservation platform and payment provider to work together.
The restaurant might want to:
- take a fixed deposit per guest;
- take a percentage deposit;
- require full prepayment;
- secure the booking with a card;
- apply different policies to different reservation times;
- take larger deposits for groups;
- collect payment for private dining;
- sell prepaid experiences; or
- apply special payment rules for Christmas, Valentine's Day or other high-demand dates.
We cover the wider commercial and payment considerations in our Restaurant Deposits & No-Show Payments guide .
Card-on-file and no-show payments
A restaurant may prefer not to take a deposit from every guest.
Instead, the reservation can be secured using an appropriate stored payment credential or tokenised card-on-file arrangement.
This can potentially support later charges under the restaurant's agreed booking and cancellation terms where the payment provider and card-scheme framework allow it.
The payment architecture matters because restaurants should not simply retain sensitive card-security information themselves.
The provider needs to support the required tokenisation and stored-credential workflow correctly.
Prepayments, experiences and private dining
SevenRooms can also be used for bookable experiences and events.
This creates more complex payment requirements than a standard table reservation.
A restaurant may need to collect:
- full payment at booking;
- a partial deposit;
- a later balance;
- minimum-spend commitments;
- payment for upgrades;
- private dining payments;
- event tickets; or
- additional charges before the guest attends.
Large restaurants and hospitality groups should consider whether these payment journeys can be reconciled automatically or whether staff will need to match transactions manually.
SevenRooms and EPOS integration
The reservation payment is only one part of the restaurant's payment journey.
Once the customer attends, the venue may also need the reservation to connect with the restaurant's EPOS.
SevenRooms currently supports a range of POS integrations, with availability depending on system, version and country.
Examples listed by SevenRooms include:
- Oracle MICROS Simphony;
- Lightspeed;
- Toast;
- NCR Aloha;
- Shiji Infrasys;
- TISSL;
- Tevalis;
- Zonal;
- Square for Restaurants;
- Quadranet;
- Silverware;
- Squirrel Systems; and
- unTill.
The capabilities are not identical across every integration.
Some can support functionality such as:
- check linking;
- guest-spend data;
- reservation matching;
- real-time information;
- status updates; and
- central reporting.
For the wider technology setup, see our EPOS for Hospitality Businesses guide .
The payment provider has to fit the whole restaurant technology stack
A restaurant using SevenRooms might also have:
- EPOS;
- integrated card terminals;
- online ordering;
- delivery;
- loyalty software;
- gift cards;
- accounting software;
- multiple restaurant locations;
- central finance teams; and
- several merchant accounts or MIDs.
Changing the gateway or acquirer without understanding those dependencies can create more problems than it solves.
Stripe and SevenRooms
Stripe is one of the payment processors SevenRooms officially lists.
It can therefore be a natural option for restaurants that want a straightforward route into SevenRooms payments.
But it is not the only supported payment provider.
Established restaurant groups should still compare:
- processing cost;
- domestic and international card pricing;
- settlement;
- refund processes;
- multi-location support;
- reporting;
- support;
- existing EPOS relationships;
- acquiring structure; and
- whether the required SevenRooms functionality is supported in their market.
The lowest-friction provider is not automatically the lowest-cost or most suitable provider once a restaurant reaches significant payment volume.
Using Cybersource with SevenRooms
Cybersource is also listed by SevenRooms as a supported payment processor.
This can be particularly relevant for established hospitality businesses because Cybersource can sit within more complex gateway and acquiring structures.
That creates the potential to consider the gateway and acquiring relationship separately rather than assuming that both parts of the payment stack must come from one provider.
Merchant Advice Service works with payment providers that support a range of integrations, including SevenRooms-compatible routes.
The important step is establishing the exact configuration required before approaching providers.
Adyen, FreedomPay, Shift4 and other SevenRooms payment routes
SevenRooms also currently lists Adyen, FreedomPay, Shift4 and Network International among its supported payment processors.
This does not mean every provider is suitable or available for every restaurant.
Provider choice can depend on:
- country;
- restaurant size;
- annual processing volume;
- number of venues;
- currencies;
- existing acquiring agreements;
- EPOS;
- required SevenRooms functionality;
- implementation resources; and
- commercial terms.
For restaurant groups, the existing payment infrastructure may therefore determine which SevenRooms route makes the most sense.
Looking for a payment provider that works with SevenRooms?
Tell us which systems you currently use, your payment volume and what you need SevenRooms to do.
Merchant Advice Service can help you understand the gateway, acquiring and integration requirements before identifying providers that may be suitable.
Find suitable payment providers
Can you change payment provider without changing SevenRooms?
Potentially, yes.
If SevenRooms supports another payment processor that meets the restaurant's requirements, the business may be able to change payment arrangements while retaining SevenRooms.
However, this should not be treated as a simple pricing switch.
Before moving, establish:
- whether the new provider is supported in your country;
- which SevenRooms payment features will continue to work;
- whether new merchant accounts or MIDs are required;
- whether stored payment credentials can move;
- how existing future bookings are handled;
- how refunds against historic transactions will work;
- whether EPOS integration is affected;
- how settlement reporting changes; and
- whether downtime or migration testing is required.
Businesses planning a complex migration should also read our guide to changing gateways and moving stored payment credentials .
SevenRooms for restaurant groups and multi-site operators
The payment architecture becomes more important as the number of venues grows.
A group may need to decide whether:
- each restaurant has its own merchant account;
- locations use separate MIDs;
- settlement is centralised or site-specific;
- deposits are reported by venue;
- refund permissions sit locally or at head office;
- pricing is negotiated at group level;
- international venues use different acquirers;
- one gateway can support the entire estate; and
- finance receives consolidated reconciliation data.
Our Merchant ID and Multiple MIDs guide explains how different merchant-processing structures can be organised.
SevenRooms payment reconciliation
Restaurants should also consider what happens after the transaction is approved.
A single guest could create several financial events:
Reservation deposit → refund or adjustment → restaurant bill → tip → final settlement
For events or private dining there may also be:
Initial deposit → interim payment → final balance → additional spend
Finance then needs to associate those transactions with:
- the correct guest;
- reservation;
- venue;
- merchant account;
- EPOS check;
- refund;
- settlement batch; and
- accounting record.
For larger groups this makes payment reconciliation an important part of provider selection.
SevenRooms, DoorDash Reservations and restaurant discovery
SevenRooms now also integrates more closely with DoorDash's restaurant ecosystem.
DoorDash Reservations allows participating restaurants to expose reservation availability through DoorDash, with bookings flowing into SevenRooms.
SevenRooms says participating venues retain control of availability, branding and guest relationships, while DoorDash bookings can feed into the SevenRooms platform.
Availability is currently location-dependent, so UK restaurants should not assume that every DoorDash reservation feature shown internationally is available in the UK.
The broader direction is nevertheless important: restaurant discovery, ordering, loyalty, reservations and customer data are increasingly being connected.
What does DashOS mean for SevenRooms users?
DoorDash announced DashOS on 30 September 2026.
The platform is intended to bring together restaurant interactions across:
- delivery;
- direct ordering;
- reservations;
- loyalty;
- guest profiles;
- marketing; and
- other restaurant systems.
DoorDash has also described plans for wider access to SevenRooms guest-profile and customer-engagement capabilities through restaurant technology integrations from 2027.
This should be treated as a product roadmap rather than an assumption that every SevenRooms or DoorDash customer already has access to all DashOS functionality.
For payment teams, however, the direction reinforces an important point:
restaurant payments increasingly sit inside a wider connected technology and customer-data environment.
Questions to ask before choosing a SevenRooms payment provider
- Is the payment provider supported by SevenRooms in our country?
- Can it support booking deposits?
- Can it support full prepayments?
- Can it securely support card-on-file?
- How are no-show charges handled?
- Can it support restaurant experiences and events?
- What happens when a booking changes?
- How are partial and full refunds processed?
- Does it work with our EPOS?
- Can the restaurant use integrated terminals?
- What happens to existing stored credentials if we switch?
- How are multiple locations structured?
- How quickly are funds settled?
- How are deposits reconciled against restaurant bills?
- What are the total gateway, acquiring and transaction costs?
- Can the provider support our future international expansion?
Start with the integration, not the headline card rate
For a restaurant using SevenRooms, the payment provider needs to work with the operational setup as well as process cards.
A saving on transaction fees can quickly disappear if the new setup creates manual refunds, broken booking workflows, duplicate reconciliation or incompatible EPOS processes.
Merchant Advice Service helps businesses understand the payment requirements first, including SevenRooms, booking payments, gateway compatibility, acquiring, EPOS, settlement and multi-site structures.
Get personalised recommendations Explore payment gateway providers
Related restaurant payment guides
Editorial & Commercial Disclosure
This guide provides general information about SevenRooms payment integration, payment providers, restaurant booking payments, EPOS and related hospitality payment infrastructure.
SevenRooms integration availability, features and supported payment providers can vary by market, account, provider and technical configuration. Businesses should confirm current compatibility directly with SevenRooms and the relevant payment provider before making changes.
References to DoorDash and DashOS include announced functionality and future product plans. Future functionality may change and may not be available in every market.
Merchant Advice Service is independent of SevenRooms and DoorDash.
MAS may receive a referral fee or commission from some payment providers where a business proceeds following an introduction. Commercial relationships do not determine the factual information or provider-selection principles contained within this guide.
Payment-provider approval, pricing, functionality and integration support are determined by the individual provider. Information is provided for general guidance and should not be treated as legal, regulatory or technical implementation advice.
