Skip to content
Resrv
Esc
↑↓navigate↵open⌘Jpreview
On this page

Upgrading to v6

Find the section that starts at your version, then work through it and every section after it. composer update installs the latest release in one go, so read all the sections that apply before you run it.

  1. Upgrading from v5 to v6: new requirements, destructive rate migrations, settings and custom code.
  2. Upgrading from v6.0.0 to v6.1.0: one removed attribute.
  3. Upgrading from v6.1.0 to v6.4.0: a new gateway method, a new status and a changed tag default.
  4. Upgrading to v6.5.0: manual reservations, gateway interface changes and a scheduled command.
  5. Upgrading to v6.5.2: a security fix, one migration and two translation keys.
  6. Upgrading to v6.5.3: one translation key, two payment views and a check for custom gateways.
  7. Upgrading to v6.5.4: a check for searches that set the quantity themselves.
  8. Upgrading to v6.6.0: two migrations, offline bookings that wait for payment, a cache store check and the PayPal add-on.

Each section ends with a checklist for confirming the upgrade worked.

Upgrading from v5 to v6

v6 replaces the old “advanced” and “connected” availability with collection-scoped Rates, adds multiple payment gateways and moves most settings from the config file to the Control Panel.

1. Bump your requirements

Requirement v5 v6
PHP 8.1 / 8.2 8.4+
Laravel 10 / 11 12 or 13
Statamic 5 6
Livewire 3 3.6.4+ or 4

Upgrade your project to Statamic 6 and Laravel 12 or 13 before you upgrade Resrv. Then update the package:

composer update reachweb/statamic-resrv

Laravel 13: keep php session serialization

Laravel 13 changed the default session serialization in config/session.php from php to json. Resrv’s availability search keeps its AvailabilityData form object in the session with Livewire’s #[Session('resrv-search')] attribute, and JSON turns that object into a plain array. The next request then throws:

Cannot assign array to property ... of type AvailabilityData

Set it back to php in config/session.php:

'serialization' => 'php',

The Resrv starter kit already ships with this setting. It works around a Livewire limitation, so keep it until Livewire fixes it.

2. Run the migrations

php artisan migrate

Watch the four rate migrations. They run in this order:

  1. Create the resrv_rates and resrv_rate_entries tables.
  2. Add a nullable rate_id column to resrv_availabilities, resrv_reservations, resrv_child_reservations and resrv_fixed_pricing.
  3. Data migration: group existing availability by collection, create a rate per unique property (or a default rate for standard availability) and backfill rate_id on every row.
  4. Finalize: delete orphaned rows with no rate_id (logged as warnings), drop the property column and the resrv_advanced_availabilities table, make rate_id required and add the new unique constraints.

The other new v6 tables and columns need no special handling.

3. Migrate your settings

Most settings now live in the Control Panel under Resrv → Settings and are saved to resources/addons/statamic-resrv.yaml. The published config/resrv-config.php is now for developers only and holds just payment_gateway, payment_gateways and the stripe_* keys.

composer update already copied your old values across. A Statamic update script runs when you cross into 6.0.0 and prints a short report. Run the command yourself to preview the result, or to re-run it if composer update ran with --no-scripts or you edited config/resrv-config.php afterwards:

php please resrv:settings:migrate --dry-run   # preview, saves nothing
php please resrv:settings:migrate             # run or re-run

It never overwrites a value already set in the Control Panel. The report lists the values it seeded (including the old nested checkout_forms and reservation_emails), conflicts where the Control Panel value stays active, keys that are safe to delete, stale keys such as enable_advanced_availability, and the developer keys to keep.

While config/resrv-config.php still defines keys the Control Panel manages, the settings page shows a “⚠ Published config file detected” warning. Delete those keys, keeping only the developer keys, to clear it.

See Configuration for every setting.

4. Move from advanced/connected availability to Rates

v5’s per-entry “advanced availability” (the property column) and “connected availabilities” are removed and replaced by Rates.

The migrations in step 2 created a rate for each old property, plus a default rate for standard availability. The resrv:upgrade-to-rates command gives those rates titles. It doesn’t run automatically:

php please resrv:upgrade-to-rates --dry-run   # preview
php please resrv:upgrade-to-rates

In standard collections, it renames the default rate to “Standard Rate”. In collections with properties, it titles each rate from the advanced_availability labels in your blueprint, so {"non-refundable":"Non Refundable"} gives the non-refundable rate the title “Non Refundable”. It warns about connected availabilities but doesn’t migrate them.

Then open Resrv → Rates and check the rates and titles in each collection.

Replacing connected availabilities

The AvailabilityChanged event and the UpdateConnectedAvailabilities listener are gone too. If you used connected availabilities to sync inventory across entries, either:

  1. Merge the connected entries into one entry with several rates. We recommend this, since rates with shared availability draw from one inventory pool.
  2. Write your own sync in listeners for ReservationCreated and ReservationCancelled:
use Reach\StatamicResrv\Events\ReservationCreated;
use Reach\StatamicResrv\Events\ReservationCancelled;

Event::listen(ReservationCreated::class, function ($event) {
    // Your custom availability sync logic.
});

Event::listen(ReservationCancelled::class, function ($event) {
    // Your custom reverse-sync logic.
});

Custom code changes

In custom PHP, replace property references with rate references:

// Old
$reservation->property;
$reservation->getPropertyAttributeLabel();
$availability->property;

// New
$reservation->rate_id;
$reservation->rate;          // Rate model relationship
$reservation->getRateLabel(); // Human-readable label
$availability->rate_id;

Useful rate lookups:

use Reach\StatamicResrv\Models\Rate;

Rate::forEntry($statamicId)->get();        // rates available to an entry
Rate::forCollection('rooms')->get();       // all rates in a collection
Rate::findOrCreateDefaultForEntry($id);    // ensure a default rate exists

Availability request arrays now use an integer rate_id instead of the advanced property string:

// Old
['date_start' => '2026-04-01', 'date_end' => '2026-04-05', 'quantity' => 1, 'advanced' => 'double-room'];

// New
['date_start' => '2026-04-01', 'date_end' => '2026-04-05', 'quantity' => 1, 'rate_id' => 3];

The NoAdvancedAvailabilitySet exception is gone, so remove any catch blocks for it.

The old advanced_availability and connected_availabilities blueprint fields no longer do anything. Remove them once you’ve checked the migration.

5. Update custom payment gateways

A custom gateway that implements PaymentInterface fails to load until it has these five new methods. Resrv loads every configured gateway class, so one outdated gateway breaks checkout, webhooks and the Control Panel reservation pages.

Method Role
name(): string Machine slug, lowercase with no spaces, such as paypal.
label(): string Default label in the checkout gateway picker.
paymentView(): string Blade view for the inline payment UI. Redirect gateways return the default view, which never renders.
supportsManualConfirmation(): bool true only for offline gateways that no provider verifies, false for provider-backed ones.
cancelPaymentIntent(string $paymentId, Reservation $reservation): void Voids an abandoned provider-side intent.

Because composer update installs the latest release, make the later interface changes before you deploy too: supportsAutomaticRefunds() from v6.2.0 and the v6.5.0 changes.

v6 also adds per-gateway webhook routes (/resrv/api/webhook/{gateway}). Single-gateway sites keep working, because the payment_gateway config key and the bare /resrv/api/webhook route still point to the default gateway.

See the Custom payment gateway guide for each method, and Payment gateways for multiple gateways, surcharges and amount limits.

6. Update published frontend templates

Component property renames

In your Antlers templates, rename these properties on the availability components:

Component v5 v6
availability-search advanced rates
availability-search anyAdvanced anyRate
availability-search and availability-results overrideProperties overrideRates
availability-results advanced rates

Rate selector rename

If you published the advanced-availability partial, rename it:

mv resources/views/vendor/statamic-resrv/livewire/components/availability-advanced.blade.php \
   resources/views/vendor/statamic-resrv/livewire/components/availability-rates.blade.php

In availability-search.blade.php, update the variable, component tag and wire model:

{{-- Old --}}
@if ($advanced)
<x-resrv::availability-advanced wire:model.live="data.advanced" :entryRates="$this->entryRates" :errors="$errors" />
@endif

{{-- New --}}
@if ($rates)
<x-resrv::availability-rates wire:model.live="data.rate" :entryRates="$this->entryRates" :errors="$errors" />
@endif

Results template

In availability-results.blade.php, replace the request.property checks with message.status:

{{-- Old --}}
@if (data_get($availability, 'request.property') !== 'any')

{{-- New --}}
@if (data_get($availability, 'message.status') === true)

Also rename advancedProperties() to entryRates() and checkoutProperty() to checkoutRate(). If you copied the old advanced sub-view, move your changes to the <x-resrv::availability-results-advanced> component (components/availability-results-advanced.blade.php), which replaces it.

Checkout and email templates

In checkout-reservation-details.blade.php and any email template that used the property, swap the accessors:

{{-- Old --}}
@if ($reservation->property)
    {{ $reservation->getPropertyAttributeLabel() }}
@endif

{{-- New --}}
@if ($reservation->rate_id)
    {{ $reservation->getRateLabel() }}
@endif

Calendar library and CSS variables

The frontend calendar is now @reachweb/alpine-calendar instead of Vanilla Calendar Pro. Day.js is still bundled and the asset URLs haven’t changed, so re-publishing the frontend assets is usually enough. Every calendar CSS variable was renamed, though.

If you customized the calendar’s colors, rename your --calendar-* variables to the new --color-calendar-* and --radius-calendar-* ones:

/* Old */
--calendar-color-main: #06b6d4;

/* New */
--color-calendar-primary: #06b6d4;

The --calendar-color-slate-* palette and the --calendar-color-main accent are gone. The new defaults have zero specificity, so your overrides don’t need !important. See Frontend Setup for the full variable list and the re-publish command.

7. Update language overrides

If you published the language files, add the new rate keys. The old property keys still work.

New key Default
selectRate “Select rate”
pleaseSelectRate “Please select a rate…”
pleaseSelectRateToBook “Please select a rate to book”
multipleRatesAvailable “Multiple rates available.”

Payments and cancellation policies added more frontend keys, such as selectPaymentMethod and noGatewayAvailableForAmount. Re-publish the language files and merge the new keys into your overrides. See Languages for how overrides work.

Checklist

  • The migration output has no warnings about deleted orphaned records, or you’ve checked that those rows didn’t matter.
  • Resrv → Settings shows your old values, without the “⚠ Published config file detected” warning.
  • Resrv → Rates lists the rates you expect in each collection, with readable titles.
  • An existing reservation that used an advanced property shows its rate label in the Control Panel.
  • If you used connected availabilities, you merged those entries into one, or booking one of them updates the others.
  • Checkout and the Control Panel reservation pages load. An outdated custom gateway breaks both.
  • A test booking works from start to finish: search, pick a rate, check out and pay, with each gateway you offer.
  • If you customized the calendar’s colors, the frontend calendar still uses them.

Upgrading from v6.0.0 to v6.1.0

v6.1.0 has no migrations and nothing destructive.

1. Remove the resetOnBoot attribute

The resetOnBoot attribute on the availability-search component has been removed. Delete it from your templates, or Livewire throws a “property does not exist” error. Coming from v5, remove its old name, resetAdvancedOnBoot, as well.

{{-- Before --}}
{{ livewire:availability-search calendar="range" :rates="true" :resetOnBoot="true" }}

{{-- After --}}
{{ livewire:availability-search calendar="range" :rates="true" }}

You don’t need it anymore. Every availability component now drops a rate from the resrv-search session that doesn’t apply to it, and auto-selects the rate when only one is valid.

2. Optional: schedule housekeeping

The new resrv:housekeeping command clears long-expired reservations and their related rows, orphaned customer details and availability for past dates. It doesn’t run on its own, so add it to your scheduler:

// routes/console.php
use Illuminate\Support\Facades\Schedule;

Schedule::command('resrv:housekeeping')->daily();

Preview what it removes first, and check that the retention window (--days, default 30) suits your site:

php please resrv:housekeeping --dry-run

Checklist

  • grep -rnE "reset(Advanced)?OnBoot" resources/views finds nothing.
  • Pages with an availability search load without a Livewire error.
  • If you scheduled housekeeping, php artisan schedule:list shows resrv:housekeeping.

Upgrading from v6.1.0 to v6.4.0

These releases are small and nothing in them is destructive. Each one is listed separately, so skip any you already have. Their two migrations (v6.2.0 and v6.3.0) run with the others in step 2 of the v6.5.0 upgrade.

v6.2.0

  • Custom payment gateways need supportsAutomaticRefunds(): bool, or they fail to load. Return true only if your refund() returns the money through the provider’s API, and false for gateways like bank transfer. See Refunds.
  • refunded now only means the gateway returned the money. Cancellations without a refund, and voids of bookings that were never charged, get the new cancelled status. If your code checks for refunded, handle cancelled too.
  • The new reservation status page and customer cancellations stay off until you enable them.

v6.3.0

  • A coupon tied to an affiliate still credits the affiliate, but no longer lets the customer skip payment. Only affiliate links do.
  • With Enable affiliates off, Resrv no longer sets affiliate cookies, credits affiliates, lets them skip payment or sends affiliate emails.

v6.4.0

  • The reservation_from_uri tag now finds Partner bookings as well as Confirmed ones. Add statuses="confirmed" to any page that should only show confirmed bookings.

Checklist

  • Every custom payment gateway has supportsAutomaticRefunds().
  • Code that checks for the refunded status also handles cancelled.
  • Pages built on the reservation_from_uri tag show the bookings you expect.

Upgrading to v6.5.0

v6.5.0 adds manual reservations and four migrations, none of them destructive. It also changes the interface custom payment gateways implement, so if you have one, update it before anything else.

1. Update custom payment gateways first

The bundled Stripe and Offline gateways are already updated. If you wrote your own gateway, PaymentInterface has two changes that PHP enforces as soon as the class loads:

  • paymentIntent() gained a 4th parameter, ?string $returnUrl = null. Without it, the class fails to load with “Declaration of …::paymentIntent() must be compatible with …”. Redirect gateways must also use it to build the return URL they send to the provider.
  • retrievePaymentIntent(string $paymentId, Reservation $reservation): ?object is a new required method. Resrv uses it to resume an interrupted payment and to check that a payment it cancelled can’t still collect money.

Resrv loads every configured gateway class, so one outdated gateway breaks checkout, webhooks and the Control Panel reservation pages. Deploy these changes together with the package update.

Gateways that confirm payments through webhooks also need verifyPayment() to confirm Awaiting payment reservations as well as pending ones. Otherwise a customer pays through the payment link and the booking never confirms. Manual reservations only offer online gateways whose supportsWebhooks() returns true.

The Custom payment gateway guide covers all three changes. On v6.1 or earlier, your gateway also needs supportsAutomaticRefunds() from v6.2.0.

2. Update the package and run the migrations

composer update reachweb/statamic-resrv
php artisan migrate

Run the migrations before the site serves traffic, because any page or email that lists a reservation’s extras fails until the new total column exists. migrate also runs the migrations of any release you skipped.

Migration Adds
2026_07_05_000000_add_manual_reservation_columns_to_resrv_reservations_table affects_availability (boolean, default true), created_by, hold_expires_at and payment_request_email_sent_at on resrv_reservations
2026_07_21_000000_add_payment_unresolved_to_resrv_reservations_table payment_unresolved (boolean, default false) on resrv_reservations
2026_09_08_000000_add_units_per_addon_to_rates units_per_addon (nullable integer) on resrv_rates, for Booked units per add-on
2026_09_14_000000_add_total_column_to_resrv_reservation_extra_table total (nullable) on resrv_reservation_extra

Existing rows need no backfill and behave as before.

3. Schedule the lapsed-hold sweep

A manual reservation can have a payment deadline, and resrv:cancel-lapsed-holds cancels it if it’s still unpaid by then. Resrv doesn’t schedule the command for you:

// routes/console.php
use Illuminate\Support\Facades\Schedule;

Schedule::command('resrv:cancel-lapsed-holds')->everyFifteenMinutes()->withoutOverlapping();

Each run cancels the Awaiting payment reservations past their deadline and releases their availability. It also cancels any online payment in progress and emails the customer and your admins. Fifteen minutes is only a suggestion. A lapsed hold stays in place until the next run.

To see how many holds a run would cancel:

php please resrv:cancel-lapsed-holds --dry-run

See Payment deadlines for how holds and the arrival-day cut-off work.

4. Set up the payment page

Customers pay manual reservations on a page of your site, linked from the payment request email. Skip this step if you won’t take online payments for them.

  1. Create a published, non-private entry with a URL, and render the payment component in its template:

    {{ livewire:reservation-payment }}
  2. Select the entry under Resrv → Settings → Checkout → Manual reservations → Payment Page Entry.

Without it, the Create reservation page only offers offline (manually confirmed) methods, and you mark those bookings as paid in the Control Panel.

The page renders your gateway’s payment form, so its layout needs the same assets as your checkout page: Livewire, the Resrv frontend assets and, for Stripe, Stripe’s JavaScript. See Payment page for details.

5. Optional: add offline payment instructions

For offline payment methods such as bank transfer, enter your payment details under Resrv → Settings → Checkout → Manual reservations → Offline Payment Instructions. They’re shown as plain text on the payment page and in the payment request email. If you leave the field empty, customers are told to arrange payment with you and quote their booking reference.

6. Use a cache store that supports locks

The payment page uses Cache::lock(), so a double click or a second tab resumes the same payment instead of starting another. The file, database, redis, memcached, dynamodb and array stores support locks. apc doesn’t, and on it every online payment on the payment page fails with “We could not start the payment process”. If you run more than one app server, use a shared store (redis, database or memcached).

Without locks, two submits sent at the same moment on the Create reservation page could also both create a booking.

7. Re-publish or merge customized views and translations

  • If you published the email templates (php artisan vendor:publish --tag=resrv-emails) or set a custom template on an email event or form, merge in the changes from vendor/reachweb/statamic-resrv/resources/views/email/reservations. cancelled, cancelled-customer, confirmed, made, orphaned-payment and refunded changed, and old copies keep the old wording. An old cancelled template, for example, tells your admins that a lapsed hold was “cancelled by the customer”. See Template changes in v6.5 and Editing the templates. The new payment-request template uses the packaged copy until you publish it.
  • Published checkout views (--tag=resrv-checkout-views) need no merging. The new livewire/reservation-payment.blade.php and livewire/components/partials/business-contact.blade.php use the packaged copies until you publish them.
  • The frontend language file (--tag=resrv-language) has 23 new keys in frontend.php for the payment page. Only English ships, so add them to every locale you’ve published. Payment page lists them.
  • The new email and Control Panel sentences go through __(). If you translate Resrv in lang/<locale>.json, add them there.

What changes for existing sites

These apply even if you never create a manual reservation. The v6.5.0 changelog has the details.

  • Checkout now enforces extras made required by the Extra in category is selected and No extra in category is selected conditions. If you use them, test a checkout that needs one.
  • Payment webhooks no longer fail with a 419 error on Laravel 13. You can remove any preventRequestForgery(except: [...]) exclusion you added for them.
  • The Use Statamic Resrv permission now also lets a user create reservations, mark them as paid, send payment requests, extend holds and cancel unpaid reservations. Review which roles have it.
  • The Reservations status filter now defaults to Confirmed, Partner and Awaiting payment.
  • Offline checkout bookings show Payment instead of Paid, since Resrv can’t know whether the money arrived. Refunding a booking that wasn’t paid online now reminds you to return the money yourself.
  • Admins also get the orphaned-payment email when a payment lands on a Cancelled reservation.
  • Confirmation emails say “Amount already paid” instead of “Already paid by credit card” when nothing was charged online.

Checklist

  • Checkout and the Control Panel reservation pages load without a “must be compatible” error, with your custom gateways and any Mollie or PayPal add-on updated.
  • php artisan migrate:status shows the four v6.5.0 migrations as ran.
  • php artisan schedule:list shows resrv:cancel-lapsed-holds, and your server’s cron runs schedule:run every minute.
  • Your cache store (CACHE_STORE in .env) isn’t apc.
  • If you take online payments for manual reservations, a test reservation paid through its payment link turns Confirmed once the webhook arrives.
  • Your published email templates, checkout views and language files include the v6.5.0 changes.

Upgrading to v6.5.2

v6.5.2 fixes a data exposure on the checkout-complete page and adds one migration. v6.5.1 had no upgrade steps, so this section also covers upgrading from v6.5.0. The v6.5.2 changelog has the details.

1. Update the package and run the migration

composer update reachweb/statamic-resrv
php artisan migrate
Migration Adds
2026_11_15_000000_add_confirmed_at_to_resrv_reservations_table confirmed_at (nullable timestamp) on resrv_reservations

Run it before the site serves traffic. Resrv records confirmed_at every time a booking is confirmed, so confirmations fail until the column exists. Existing rows need no backfill: bookings confirmed before the upgrade use created_at for their cancellation label.

2. Clear the static cache

If your site uses Statamic’s static caching and didn’t exclude the checkout-complete page, run this once after deploying:

php please static:clear

From v6.5.2, Resrv keeps pages that render {{ resrv_checkout_redirect }} out of the static cache, but copies cached before the upgrade are still served until you clear them. A CDN or reverse proxy that caches HTML must not cache that page either.

3. Update custom payment gateways

There’s no interface change, so nothing fails to load. But if your gateway’s handlePaymentPending() looks the reservation up with Reservation::find(request()->input('payment_pending')), replace its body:

use Reach\StatamicResrv\Http\Payment\PendingPayment;

public function handlePaymentPending(): bool|array
{
    return PendingPayment::fromRequest();
}

The tag now filters what any gateway returns, but update the gateway anyway. See Handling the redirect back.

If your provider can’t cancel an order the bank hasn’t answered yet, you can now report when that order expires. See Retrieving a payment intent.

4. Merge customized views and translations

  • The frontend language file (--tag=resrv-language) has two new keys in frontend.php: freeCancellationPassed (cancellation policy keys) and paymentAttemptStillOpen (payment page). Add them to every locale you’ve published.
  • A published livewire/reservation-payment.blade.php doesn’t show the new “try again after” notice. Merge in the $paymentRetryAt block from the packaged view if your gateway reports ->expires_at.
  • Custom result views that style the cancellation label, such as a green “free cancellation” badge, should check CancellationPolicy::freeCancellationOpen() and treat a closed window like non-refundable. The stock views need no change.

What changes for existing sites

  • Rates no longer offer free cancellation once its date has passed for the dates searched. They show “No free cancellation for these dates” instead.
  • The checkout-complete page shows a booking’s data only to the session that made it, for 60 minutes. Anyone else, including the same customer in another browser, sees the pending message without it.
  • The booking calendar is updated to @reachweb/alpine-calendar v1.4.1. The precompiled script and stylesheet update with the package. If you bundle the calendar yourself, update it too.

Checklist

  • php artisan migrate:status shows 2026_11_15_000000_add_confirmed_at_to_resrv_reservations_table as ran.
  • A test booking confirms and gets a confirmed_at value.
  • If you use static caching, you’ve run php please static:clear.
  • Every custom gateway’s handlePaymentPending() returns PendingPayment::fromRequest().
  • Your published language files include freeCancellationPassed and paymentAttemptStillOpen.

Upgrading to v6.5.3

v6.5.3 fixes four checkout and payment bugs. It has no migrations and no interface changes. The v6.5.3 changelog has the details.

1. Update the package

composer update reachweb/statamic-resrv

If you use the Mollie add-on, update it to v2.0.2 or later too (composer update reachweb/resrv-payment-mollie). Earlier versions report a customer who comes back from Mollie without paying as pending, which ends the checkout instead of letting them try again.

2. Check what your custom gateways return

There’s no interface change, so nothing fails to load. But a false status from handleRedirectBack() now leaves the checkout open. When the customer goes back to the checkout or searches again, Resrv clears the payment from the reservation and calls your cancelPaymentIntent(). So choose the status by what the customer still has to do:

  • Return false when the attempt didn’t succeed and the customer has to act again, such as a declined card or a cancelled or abandoned attempt. Do this even when the provider keeps the payment open for another try.
  • Return 'pending' when the customer has done their part and the payment completes without them, such as a bank transfer or a payment that’s still processing.

A gateway that returns false for a payment that’s still completing has it cancelled when the customer goes back. If the provider can’t cancel it, it’s no longer attached to the reservation, and a later payment on it won’t confirm the booking. See Handling the redirect back.

3. Merge customized views and translations

  • The frontend language file (--tag=resrv-language) has one new key in frontend.php: noGatewayAvailable (“No payment method is available right now. Please try again later.”). Add it to every locale you’ve published.
  • A published livewire/checkout-payment.blade.php or livewire/checkout-payment-offline.blade.php still prints the amount without its trailing zeros. Replace {{ $amount }} with the line the packaged views use:
{{ \Reach\StatamicResrv\Facades\Price::create($amount)->format() }}

The same goes for a custom gateway’s inline payment view that prints $amount.

What changes for existing sites

  • After a failed payment, the customer can go back to the checkout and pay again, and their next search releases the hold on the dates. Before, the checkout was gone and the hold stayed until minutes_to_hold passed.
  • With multiple gateways, a gateway that can’t be loaded is left out of the payment step instead of breaking it. Your error tracker gets “Payment gateway [name] could not be loaded and was left out of checkout.” each time, so a missing gateway still needs fixing.
  • The Stripe and offline payment views show amounts with the currency’s decimals.

Checklist

  • The payment step shows the amount with its decimals, such as “€ 50.00”.
  • Your published language files include noGatewayAvailable.
  • With a redirect gateway, a cancelled test payment shows the payment-failed message, and going back to the checkout opens it instead of “Reservation not found in the session”.
  • Every custom gateway’s handleRedirectBack() returns false only when the customer has to act again.

Upgrading to v6.5.4

v6.5.4 stops a quantity picked in one page’s search from pricing and booking the results of another, and fixes clearing a search and dated links. It has no migrations. The v6.5.4 changelog has the details.

1. Update the package

composer update reachweb/statamic-resrv

2. Check searches that set the quantity themselves

An availability-search without enableQuantity="true" now resets the quantity to 1 when the page loads. If a published search view sets data.quantity its own way, such as the Guests component bound to the quantity, add enableQuantity="true" to that search. Otherwise the guest counts it shows stay after a reload, but the results price one unit.

enableQuantity also shows the stock quantity control in a view that keeps the packaged @if ($enableQuantity) block. Remove that block if the view has its own control.

3. Optional: remove workarounds

Code that set the quantity back to 1 on pages whose search has no quantity control can go. The Resrv Hotel starter kit has one in resources/views/spa-treatments/show.antlers.html: on for_two treatments, the booking panel’s Alpine x-init calls Livewire.getByName('availability-search') and $set('data.quantity', 1), and an x-bind:class on the results wrapper keeps the results invisible until they search again. Delete the Antlers comment above the panel, the panel’s x-data, x-init and x-on:availability-results-updated attributes, and the x-bind:class on the results wrapper, with the if for_two conditions around them. Left in place, they do nothing, because the quantity is already 1 when they run.

A redirectTo added to a search with live off only so that clearing its dates didn’t reload the page can go too. In the starter kit, that’s the Treatment tab’s search in resources/views/partials/hero-booking.antlers.html, with the last sentence of the Antlers comment above it.

What changes for existing sites

  • A search without enableQuantity resets a quantity the visitor picked on another page to 1.
  • Results, lists and collections that render before that search on the same page load still read the saved quantity. That includes all of them in the page template when the search is in your layout. The quantity on other pages explains the render order and pages with two searches.
  • On a page without a search, results, lists and collections keep the saved quantity. A search that redirects to such a page still carries its quantity.
  • Clearing the dates no longer reloads the page when the search has live off and no redirectTo. It updates the results on the page instead.
  • Clearing the dates keeps the Guests component’s guest counts. It still resets the dates, quantity and rate.
  • A link with dates but no rate no longer reuses the rate saved from the visitor’s earlier search.

Checklist

  • Pick 2 in a search with a quantity control, then open a page whose search has none, with dates still set: its results show the price for one unit. If that search is in your layout, check after a second page load.
  • Every search whose view sets data.quantity itself has enableQuantity="true".
  • Clearing the dates of a search with live off and no redirectTo updates the results without reloading the page.

Upgrading to v6.6.0

v6.6.0 holds offline checkout bookings until they’re paid and changes how the checkout starts and cancels payments. It has two migrations, and one of them drops a column, so back up your database first. The v6.6.0 changelog has the details.

1. Use a cache store that supports locks

From v6.6.0, the checkout takes a cache lock for each booking, so two tabs can’t start two payments for it. On the apc store, which has no locks, every checkout now fails, not only the payment page. Check that CACHE_STORE in .env isn’t apc. Use a cache store that supports locks lists the stores that work.

2. Update the package and run the migrations

composer update reachweb/statamic-resrv
php artisan migrate

The two migrations change resrv_reservations:

  • 2026_11_18_000000_add_payment_intent_amount_to_resrv_reservations_table adds payment_intent_amount (nullable decimal), the amount the stored payment charges, so a customer can continue it.
  • 2026_11_18_000001_add_payment_settlement_to_resrv_reservations_table adds payment_settlement (string, default none), fills it in for existing reservations and drops payment_unresolved.

Run them before the site serves traffic: starting a payment and confirming a booking write the new columns, and fail until they exist.

payment_settlement records how a reservation was paid (see Reservation Details). The migration sets it from each reservation’s payment:

  • Paid through a gateway: gateway.
  • Marked as paid in the Control Panel: out_of_band.
  • Cancelled while its online payment couldn’t be verified as cancelled: unresolved.
  • An offline checkout booking confirmed before v6.6.0: unresolved, and its made-up offline_… payment id is removed. Nothing recorded whether it was paid, so the Control Panel still shows Payment rather than Paid.
  • Everything else: none.

Every reservation reports the same amount received as before. Rolling the migration back restores payment_unresolved.

3. Update the PayPal add-on

If you use the PayPal add-on, update it to v1.1.1 or later in the same deploy:

composer update reachweb/resrv-payment-paypal

From v6.6.0, the checkout checks with the provider that a payment is cancelled before it starts another one. Earlier versions of the add-on report a PayPal order the customer started as still payable, so once a customer picks PayPal, Change payment method and a coupon change show “We could not start the payment process” until the checkout expires.

4. Check what relies on offline bookings being confirmed

A website booking made with the Offline gateway, or any gateway whose supportsManualConfirmation() returns true, now waits in Awaiting payment until you Mark as paid (see Offline / pay-later). Skip this step if you don’t offer one at checkout.

  • Emails: the customer gets the Customer payment request email instead of the confirmation, and it’s the only email they get when they book. If you turned that event off because you don’t create manual reservations, turn it back on. Your admins get the new Admin awaiting payment email when the customer books, and Admin made when you mark it as paid. See Offline checkout bookings.
  • Events: ReservationConfirmed fires when you mark the booking as paid, not when the customer books. Listeners and integrations that act on it, such as the Vouchers add-on, now act then.
  • Your process: mark these bookings as paid when the money arrives, and cancel the ones that are never paid. They have no deadline, so resrv:cancel-lapsed-holds leaves them alone unless you set one with Extend hold.

Bookings confirmed before v6.6.0 stay Confirmed.

5. Update custom code and custom payment gateways

PaymentInterface hasn’t changed, so nothing fails to load. Check your own code for these changes:

  • payment_unresolved is gone. Read payment_settlement or $reservation->amountReceived() instead, and don’t treat a payment_id as money received.
  • Removed Reservation methods: supportsAutomaticRefund() (use refundIsAutomatic()) and confirmedWithoutGatewayCharge(). amountPaidOnline() still works, but it’s a deprecated alias of amountPaid().
  • Removed pricing methods: Extra::getPriceForDates(), Option::valuesPriceForDates(), and in the Extras and Options components getExtrasForReservation(), getExtrasForSearch(), getExtrasForSelections(), updateEnabledExtraPrices(), getOptionsForReservation(), getOptionsForSearch(), getOptionsForSelections() and updateEnabledOptionPrices(). Extras and options are now priced by Reach\StatamicResrv\Support\AddonQuote.
  • Checkout::resetPaymentState() returns bool. A component that extends Checkout and overrides it must declare the return type too.
  • New enum cases: ReservationEmailEvent::AdminAwaitingPayment and ReservationLogReason::CheckoutAwaitingPayment. An exhaustive match over either enum throws UnhandledMatchError until it handles them.

If you wrote a payment gateway:

  • Report a dead payment as canceled. The checkout now replaces a payment only when retrievePaymentIntent() returns null or reports it canceled. Any other status counts as still payable, and the customer can’t switch method or apply a coupon until it changes. Add ->expires_at when the provider’s payment expires on its own, so the customer is told when to try again. See Retrieving a payment intent.
  • Put resrv_gateway on your return URL. Resrv no longer adds it to the provider URL a redirect gateway returns. See The return URL.
  • Offline gateways never get paymentIntent() calls at checkout, and their bookings wait for Mark as paid.
  • Optional: move your webhook handling to confirmFromGateway(), which adds the stale-payment and paid-twice alerts. See Verifying webhooks and the upgrade guide for gateways.

6. Merge customized views and translations

Old copies keep working, but they keep the old wording and miss the new states. Merge in the changes from vendor/reachweb/statamic-resrv/resources:

  • Language file (--tag=resrv-language): frontend.php has two new keys, statusAwaitingPayment and awaitingPaymentNote (see Translations). offlinePaymentDescription changed too: the old text tells customers payment “can be arranged separately”. Update all three in every locale you’ve published.
  • Email templates (--tag=resrv-emails):
    • payment-request needs the $placedByCustomer branch, or it greets website customers with “We have created a reservation for you.” It also lists each stay of a cart booking.
    • confirmed and made show Payment when Resrv doesn’t know whether the customer paid.
    • cancelled and cancelled-customer decide whether money was collected from amountPaid(). cancelled-customer also lists each stay of a cart booking.
    • orphaned-payment has a new confirmed_by_another_payment context. An old copy describes it as a payment on a booking that’s no longer live.
    • The new awaiting-payment template uses the packaged copy until you publish it.
  • Checkout views (--tag=resrv-checkout-views):
    • livewire/checkout-payment-offline.blade.php shows your Offline Payment Instructions.
    • livewire/components/checkout-payment-table.blade.php shows an extra’s clamped line with $enabledExtras->lineTotal($extra)->format(), not price times quantity.
    • livewire/reservation-status.blade.php shows the Awaiting payment badge and note.
  • JSON translations: the new email and Control Panel sentences go through __(). If you translate Resrv in lang/<locale>.json, add them there.

Sites built on the Resrv Hotel starter kit have published copies of these files, so they need the merges too.

What changes for existing sites

The v6.6.0 changelog has the details.

  • Website bookings made with an offline method wait in Awaiting payment, with their dates held, until you mark them as paid or cancel them.
  • The Reservation Status page shows Awaiting payment bookings, including reservations you created in the Control Panel, without a cancel button.
  • A customer who comes back to the checkout and pays with the same gateway and amount continues the payment they started.
  • The checkout no longer starts a second payment while the first can still be paid. With the Mollie add-on, a customer who leaves Mollie’s page without paying or cancelling, with the browser’s back button for example, can pay with Mollie again, but can’t switch to another method until Mollie expires that payment. Most open Mollie payments can’t be cancelled.
  • Your admins get “Possible duplicate payment” when a Stripe payment succeeds on a booking that another payment, or Mark as paid, already confirmed.
  • An extra clamped by a minimum or maximum price shows and charges its clamped line in the results, the cart, checkout and the Control Panel.
  • Checkout offers only published option values, so a required option with no published values blocks checkout, as it already did on the Create reservation page. An extra that doesn’t allow multiple is capped at one unit.
  • With no rate selected and order sorting, the entry page shows the first bookable rate, which can differ from before.
  • /resrv/api/webhook without a gateway name goes to your only configured gateway.

Checklist

  • php artisan migrate:status shows the two v6.6.0 migrations as ran.
  • Your cache store (CACHE_STORE in .env) isn’t apc, and a test checkout reaches the payment step.
  • If you use PayPal: after picking PayPal at checkout, Change payment method and another method load its payment form.
  • If you offer an offline method: a test booking turns Awaiting payment, the customer gets the payment request, your admins get “awaiting payment”, and Mark as paid confirms it.
  • A search of your code for payment_unresolved, supportsAutomaticRefund, confirmedWithoutGatewayCharge, getPriceForDates and valuesPriceForDates finds nothing.
  • Your published email templates, checkout views and language files include the v6.6.0 changes.

Was this page helpful?