How to take deposits and payments for a holiday let, on your own site

Ask any host why they haven't gone direct and, sooner or later, you'll hear the real reason: "I don't know how I'd actually take the money." It feels like the hard part, the bit Airbnb quietly does for you. In reality, taking a card payment on your own site in 2026 is genuinely simple, safer than most people assume, and cheaper than handing over a commission every single time. This guide walks through exactly how it works, from the first deposit to the security hold, and where the (small, manageable) risks actually sit.

How do I take card payments without a platform like Airbnb?

You connect a payment provider to your booking website, and it does the heavy lifting. The two most common in the UK are Stripe and PayPal. A guest picks their dates, reaches the checkout, enters their card, and the money is deposited into your own bank account a couple of days later. There's no middleman holding your funds and no platform deciding when you get paid. Setup is a one-off job: create an account, verify your identity and bank details, and connect it. FindYourStay plugs your booking site directly into your Stripe or PayPal, so payments always land in your account, never ours.

What do payment fees actually cost me?

Far less than commission, and that's the whole point. A payment processor charges a small fee per transaction, not a percentage of your business. As a rough 2026 guide for standard UK cards, Stripe is around 1.5% + 20p and PayPal around 2.9% + 30p for online card payments. Rates vary by card type (commercial and non-UK cards cost more) and change over time, so always check the provider's current pricing. Compare that with a typical OTA commission of 15% or more and the maths speaks for itself.

On a single £600 stay, going direct with Stripe keeps roughly £80 more in your pocket than the OTA route. Over a season of bookings, that difference funds a lot of new towels, or a very nice holiday of your own.

Deposit then balance, or pay in full?

This is your call, and both work well on a direct site. The two common models:

• Deposit now, balance before arrival. Guests pay a percentage (often 25% to 50%) to confirm the booking, then the remainder is due a set number of days before check-in, commonly 14 to 60 days out. This mirrors what OTA guests are used to and feels low-commitment at the point of booking.
• Pay in full at booking. Simplest to run, strongest protection against no-shows, and best for short-notice or last-minute stays where there's no time to collect a balance. Many hosts use full payment for bookings inside their balance window and a deposit split for anything further out.

How do I take a refundable security deposit?

For breakages and damage, the cleanest tool is a card pre-authorisation, not an actual charge. A pre-auth places a temporary hold on the guest's card for a set amount (say £150 to £500) without moving the money. If the stay goes fine, the hold is released and the guest is never charged. If there's damage, you capture some or all of it. Providers like Stripe support authorising a card now and only capturing later, which is exactly what a security deposit needs.

Pre-auth holds don't last forever (Stripe holds are typically valid for up to 7 days), so for longer or later stays many hosts instead take a small refundable deposit as a real payment and refund it after checkout, or use a damage-waiver fee (a small non-refundable charge that covers minor accidental damage). Any of these is far tidier than the old approach of asking for cash or a bank transfer on arrival.

Why not just take a bank transfer?

You can, but it's clunky and it's riskier than it looks. Bank transfers put all the friction on the guest: they have to leave your site, log into their banking app, copy your account details and type a reference, and plenty simply don't finish. You then have to manually watch your account and confirm each one landed before you can mark the booking as paid. Worse, sharing your account details by email is a well-known fraud target, and there's no built-in refund or dispute process if something goes wrong. A card checkout is instant, automatic and far more reassuring to a guest handing over hundreds of pounds to a name they found online. Offer bank transfer as a backup if you like, but don't make it the main way in.

What about chargebacks and getting scammed?

A chargeback is when a guest disputes a card payment with their bank and asks for the money back. They're rare in holiday lets, but worth understanding. The bank reverses the payment while it investigates, and the provider usually charges a small dispute fee (around £15 on Stripe). You then submit evidence, and if the claim is unfounded you can win the money back. The best protection is simply good record-keeping.

• Keep your booking confirmation, dates and guest messages so you can prove the stay was real and agreed.
• Have clear, visible terms at checkout (cancellation policy, deposit rules, house rules) that the guest accepts when they pay.
• Use the provider's built-in fraud checks (Stripe and PayPal screen risky payments automatically) and be cautious with unusual last-minute, high-value bookings.
• For extra peace of mind, providers offer optional fraud tools that flag or block suspicious cards before they ever reach you.

Is it safe? Do I have to handle card details?

No, and this is the part that quietly removes most of the worry. With Stripe or PayPal, the card details never touch your website or your inbox. The guest enters their card into the provider's own secure, hosted checkout, and you only ever receive a confirmation that payment succeeded. That means you're kept out of scope for the heavy PCI DSS compliance obligations that would apply if you were storing card numbers yourself. The provider is the one handling encryption, security and regulation; you just get told the booking is paid. It's genuinely safer than the old paper-card-slip world, and safer than emailing bank details around.

Where do cancellation terms fit in?

Your cancellation policy is what ties the payment side together, and going direct means you set it rather than accepting a platform's. Decide how much notice earns a full or partial refund, whether the deposit is non-refundable, and what happens for no-shows. Show these terms clearly at checkout so the guest agrees to them as they pay. A fair, plainly-worded policy protects your income, sets expectations, and (as noted above) is exactly the evidence that helps you win any dispute. You can be more generous than an OTA to win the booking, or firmer to protect peak dates, because the choice is finally yours.