A host I know spent an entire October chasing a single bank transfer. A German guest had booked six nights through her Smoobu direct booking page, promised to pay "by the weekend," and then went quiet. No card on file, no deposit, no leverage. She eventually got the money, but by then she had already blocked the dates for a stay that nearly evaporated. Her takeaway was blunt: the booking engine was only as good as the way it collected money, and she had set that part up wrong.
That is the honest frame for judging Smoobu's payment processing. It is not a payments company. It is a property management system and channel manager that added a way to take money on direct bookings, and the quality of that feature depends heavily on how you wire it up and what you expect from it. I have run bookings through it, watched the payout timing, and poked at the edges. Here is what actually holds up and what does not.
How does Smoobu payment processing actually work?
Smoobu payment processing works by connecting your Smoobu account to a third-party payment provider, primarily Stripe, so that guests booking through your Smoobu direct booking website or booking widget can pay by card at the moment they reserve. Smoobu itself does not hold or move the money. It hands the transaction to the connected processor, the processor charges the guest's card, and the funds land in your own Stripe balance on that provider's normal payout schedule. As of writing, Stripe is the core integration, with PayPal available as an additional option depending on your setup and region.
The important mental model is that Smoobu is the cashier, not the bank. When a guest completes a direct booking, Smoobu triggers the charge through your connected account, records the reservation as paid, and blocks the calendar. Everything after that, including deposits, payout timing, and refunds, runs on the processor's rails, not Smoobu's. That is why two hosts on the same plan can have wildly different payment experiences: one connected Stripe and turned on automatic charging, the other left payments on "request" and is still emailing IBANs.
This only applies to direct bookings. Reservations that come through Airbnb, Booking.com, or Vrbo are paid inside those platforms, and Smoobu simply imports them as already-handled. So when people ask whether Smoobu's payment processing is any good, the real question is narrower than it sounds: how well does Smoobu collect money on the bookings you own end to end?
Lodgify4.5/5
Build your own vacation rental website and manage bookings from one place
From $17/moBest for: Hosts who want a direct booking website
Smoobu supports card payments through Stripe (Visa, Mastercard, American Express and the local card schemes Stripe covers), and it supports PayPal as a separate connection, plus manual methods like bank transfer for hosts who prefer to invoice guests directly. Through Stripe, guests in many European markets can also use the wallet and local payment methods Stripe exposes, such as Apple Pay, Google Pay and, in some regions, SEPA and iDEAL, though exactly which ones appear depends on your Stripe account configuration rather than anything you toggle inside Smoobu.
In practice, most hosts run cards through Stripe and leave it there. That covers the overwhelming majority of guests and gives you an actual card on file, which is the part that matters. PayPal is useful as a fallback for guests who distrust entering card details on a site they have never seen, but it complicates refunds and deposit handling because it does not behave like a card authorization. Bank transfer is the option I would steer people away from unless you are dealing with long stays or corporate guests who insist on it, because it reintroduces exactly the "I'll pay you Friday" problem that automated payments exist to kill.
One thing to check before you commit: the wallet and local methods are a Stripe feature, not a Smoobu feature. If your guests keep asking for a payment method you cannot find, the fix is almost always in your Stripe dashboard settings, not in Smoobu.
Does Smoobu charge extra payment processing fees?
Smoobu does not add its own percentage on top of card payments; the fees you pay are the standard processing fees charged by Stripe or PayPal, which are typically around a small percentage plus a fixed amount per transaction depending on your country and card type. What Smoobu does charge, on some plans, is a booking fee that is separate from card processing. As of writing, the Professional Flex plan runs about EUR 29 per month with a 0.9% booking fee applied to reservations, while the Prepaid plan at roughly EUR 35 per month is commission-free, with extra units starting around EUR 9.60 and a Teams tier (Pro+) at about EUR 55 per month. There is a 14-day trial to test the workflow before you pay anything.
So there are potentially two costs stacked on a direct booking: the payment processor's cut, which you would pay with any tool, and Smoobu's own booking fee if you are on Flex. That 0.9% is easy to overlook because it is small, but on a portfolio doing real volume it adds up, and it is the main reason the Prepaid plan exists. If most of your revenue flows through direct bookings, the commission-free Prepaid plan usually wins on total cost even though its headline price is higher. I walk through that math in more depth in our full breakdown of Smoobu's pricing plans, and it is genuinely the calculation that decides which plan you should be on.
Readers signing up through our Smoobu referral link get a 10% discount, which softens the Prepaid plan's higher base price if that is the route you take.
Uplisting4.5/5
Short-term rental management software and channel manager
From $100/moBest for: Professional hosts who need a powerful channel manager
The best thing about Smoobu's approach is that it does not try to be your payment processor. By leaning on Stripe, it gives you a real merchant relationship, real fraud tooling, and payouts that land in an account you control. You are not waiting on Smoobu to disburse your money on its own schedule, and you are not exposed to a middleman holding funds. If Smoobu vanished tomorrow, your Stripe account and its history would still be yours. For a small software company, that is the responsible design, and it is the same architecture the better tools in this category use.
Automatic charging on confirmed bookings is the feature that earns its keep. Set it up properly and a direct booking behaves like an OTA booking: the guest pays at reservation, the calendar blocks, and you never touch it. That closes the gap that makes direct bookings scary for hosts coming off Airbnb, where the platform handles money invisibly. The onboarding flow for connecting Stripe is also refreshingly short; it is one of the smoother parts of getting started, which I noted in our review of Smoobu's channel manager.
Deposit handling is competent for the common case. You can require a payment at booking and structure a security deposit, which is more than some cheaper booking widgets manage. For a two-to-eight unit host taking a healthy share of direct reservations, this is enough machinery to run cleanly without a separate payments product bolted on.
Where Smoobu payment processing feels limited
The rough edges show up once your needs get specific. Split payments, where a guest pays a deposit now and the balance automatically 30 days before arrival, are not as flexible or as bulletproof as what you get from a payments-first platform, and hosts who rely on that flow tend to feel the friction. Refunds and partial refunds are workable but not elegant, and because the money lives in Stripe, you often end up doing part of the job in the Stripe dashboard rather than entirely inside Smoobu.
Security deposit authorizations, the pre-authorization hold that reserves funds without capturing them, are the weakest area. A true authorization hold that expires cleanly if unused is something dedicated payment stacks handle better, and Smoobu's implementation leans more toward charging and refunding than toward holding. If chargeable damage deposits with genuine authorization holds are central to how you operate, test this specific flow hard during the 14-day trial before you build your process around it.
The other limitation is conceptual: because Smoobu is deliberately not a payments company, you inherit whatever Stripe supports in your market and nothing more. Hosts in countries with thin Stripe coverage, or those who want exotic local payment rails, will hit a wall that has nothing to do with Smoobu's effort and everything to do with the processor underneath. This is the same trade-off you weigh with most PMS-led payment features, and it is worth reading alongside our broader guide to payment processing for vacation rentals to see where the general limits sit.
Guesty4.3/5
The property management platform for short-term and vacation rentals
From Custom pricingBest for: Professional property managers with 20+ listings
Is Smoobu's payment processing good enough for direct bookings?
For most independent hosts, yes, Smoobu's payment processing is good enough to run a direct booking business, provided you connect Stripe, turn on automatic charging, and keep your deposit expectations modest. It reliably collects card payments at the moment of booking, blocks the calendar, and puts money in an account you own, which are the three things that actually protect you from the "guest pays Friday" trap. Where it stops being good enough is at the edges: complex split-payment schedules, true authorization-hold security deposits, and heavy refund workflows all reveal that payments are a feature here, not the product.
The comparison that clarifies this is Lodgify, which invests more heavily in its own payment and direct-booking layer. If you want a booking engine where payments feel first-class and the website is a core selling point, Lodgify is the stronger tool on that single axis, and our Lodgify payment processing review covers exactly how the two differ. Smoobu's counterargument is price and simplicity: for a host who mainly needs to take a card cleanly on a handful of direct bookings a month, paying for a heavier payments stack is spending money to solve a problem you do not have.
The deciding factor is your direct booking mix. If direct reservations are occasional, Smoobu's payments are more than adequate and you should optimize for total cost instead. If direct bookings are your growth strategy and you are engineering deposit rules and payment schedules around them, audit those specific flows in the trial rather than trusting that the feature list covers your case.
My verdict
Smoobu's payment processing is quietly solid for what it is: a clean Stripe-backed way to take money on direct bookings, with automatic charging that makes those bookings feel as safe as OTA ones, and no hidden markup beyond the processor's normal fees and Smoobu's own booking fee on the Flex plan. It will not win a feature war against a payments-first platform, and it should not try to. It handles the common case well and leaves the exotic cases to tools built for them.
If you run one to four units and take direct bookings occasionally, Smoobu's payments will not be the thing that limits you, and the Prepaid plan through the referral discount keeps the total cost low; the 0.9% Flex booking fee is the number to watch as your direct volume grows. For five to fifteen units with a serious direct-booking push, connect Stripe, stress-test deposits and split payments during the trial, and be honest about whether you need something heavier. Past fifteen units, or if damage-deposit authorizations are central to your operation, weigh a payments-forward platform or a dedicated processor sitting alongside your PMS. The right answer is almost always about how much of your money moves through direct channels, not about the payment feature in isolation.
Francesco has spent over 10 years in digital, e-commerce and project management, working with brands across Europe. He founded RentalDuel to bring that same analytical rigor to the messy world of vacation-rental software: setting up trial accounts, mapping pricing tier by tier, and comparing what each platform actually delivers versus what it promises. He handles the data, pricing breakdowns and head-to-head comparisons on the site.
