Key takeaways
- Deposits taken months ahead create delivery-delay risk, which is what drives reserves and rolling holds in hospitality underwriting.
- Tell your processor about festival-season volume spikes before they happen, or expect held batches in March and April.
- SB 478 generally requires resort and cleaning fees to be in the advertised nightly price, not added at checkout.
Palm Springs hospitality payment processing has a shape you rarely see elsewhere in California: a business that books a large share of its annual card volume in a handful of months, collects money long before it delivers anything, and then goes quiet through a desert summer. Boutique hotels along East Palm Canyon, vacation rentals in Deepwell and the Movie Colony, restaurants on Palm Canyon Drive, wedding venues booking a year out, and anyone within driving distance of festival weekends in Indio all live inside that pattern. Underwriting reads it very differently than it reads a steady main street retailer.
Delivery delay is the real risk factor
It is not about your neighborhood or your reviews. When a guest books a March stay in October and pays a deposit, the acquiring bank carries exposure for five months. If the property closes, cancels, or fails to deliver, the issuer refunds the cardholder and the acquirer absorbs the loss if you cannot. That one fact explains most of the terms you will be offered.
Expect questions about your average booking window, deposit percentage, cancellation policy, and whether you take full prepayment. Long windows and full prepayment push you toward a rolling reserve, often a percentage of volume held for a set period. A reserve is not a punishment and it is not permanent, but you should get the release schedule in writing before you sign.
The seasonality problem nobody warns you about
Most merchant accounts are approved with a monthly volume cap and an average ticket. A Palm Springs property doing modest summer numbers and then five times that in high season will trip its cap, and the batch gets held for review at the worst possible moment.
- Give underwriting your actual month-by-month history at application, not an annual average divided by twelve.
- Ask for a seasonal cap or a documented process for temporary increases.
- Flag festival weekends and big group bookings in advance, especially a single ticket far above your stated average.
Fee display and SB 478
California's junk-fee rule, in effect since July 2024, generally requires that the advertised price include mandatory fees. For lodging and dining that has real consequences for resort fees, cleaning fees, and mandatory service charges. Government taxes and shipping are treated differently, and hospitality has seen specific follow-on guidance, so confirm the current treatment of your particular fee structure with counsel rather than copying what the property next door does.
From a disputes angle this matters twice over. A surprise line item at checkout is one of the most reliable ways to generate a "charged more than agreed" chargeback, and those are hard to win even when your terms technically disclosed it somewhere.
No-shows, cancellations and the paperwork that wins disputes
Card networks allow lodging merchants to bill no-shows and late cancellations, but only if the cardholder was given the policy in a way you can later prove. Your representment packet lives or dies on that evidence.
- Timestamped booking confirmation showing the cancellation window the guest accepted.
- The confirmation email or SMS, with delivery logs.
- Property access records, key card logs, or gate entry data showing the stay occurred.
- Signed folio or receipt for on-property charges, including incidentals.
- Any messages with the guest before or after the stay.
Assemble that packet automatically rather than hunting for it later. Strong fraud screening on the booking side also helps, because a stolen-card reservation is far cheaper to block at authorization than to fight sixty days later.
Card present, card not present, and keeping the two clean
Most properties run both: a website or booking engine taking deposits and a terminal at the front desk or in the restaurant. Keep them on the same merchant account where possible so your descriptor is consistent, but understand they price differently. Card-not-present interchange is higher, and a pass-through pricing structure makes that visible instead of burying it in a blended rate.
On the web side, use hosted fields so raw card data never touches your booking site, and store the card as a token for the balance charge and incidentals. That narrows your PCI scope considerably, which matters when a management company handles several properties on one platform.
Descriptors, group bookings and ACH
Your billing descriptor should say the property name a guest would recognize, not the LLC. A holding company name on a statement three months after booking is a friendly-fraud generator. Include a working phone number.
For weddings, corporate buyouts and long group stays, consider moving deposits to bank transfer, which settles in 1-3 business days and costs far less than card interchange on a five-figure ticket. Cards settle in 1-2 business days. Send the balance request as a payment link tied to the same customer record so the paper trail stays intact.
The properties that come through a bad season without a payments crisis are usually the ones that told their processor the truth about their seasonality up front, wrote a cancellation policy they could actually evidence, and stopped treating chargebacks as a cost of doing business in a resort town.
Ready to get set up with Flux?
Cards, ACH, and stablecoins in one platform, with volume-based pricing. No setup fees or contracts.
Get Started