OwnerRez stops processing on five card processors after 30 November, existing connections included

OwnerRez's 28 October release puts a date on something that was open ended a week earlier. Charges will stop going through Payeezy, USAePay, eProcessing Network, Plug'n Pay and OpenEdge after 30 November 2026.

That is a different and harder statement than the one in the 21 October release. Then, those five were closed to new connections while existing ones kept working. Now the processing itself ends. If you take card payments through any of them today, you have roughly a month to move to a supported processor, and the move involves a new merchant account rather than a setting.

The same release also blocks new Lynnbrook Classic payment method connections. Existing Lynnbrook Classic connections keep working, which is the softer treatment the five processors had until this week.

What to do, in order

Open your payment methods and note the processor behind each one. Property per processor setups are the ones most likely to have a legacy connection sitting quietly in the list, often on a property that someone else onboarded.

If any method runs on one of the five, start the migration now rather than in the last week of November. A new processor connection means underwriting, bank details and a test transaction, and none of that moves at your pace. Bookings already taken with stored cards are the part to ask OwnerRez about directly: a card on file against a dead processor is not a card you can charge on arrival.

Separately, if you are on Bambora, that migration to Shift4 is still due before December 2026, with no specific day given.

The pattern is now clear

Five processors closed to new connections on 21 October. Lynnbrook Classic closed to new connections on 28 October. Processing on those five ends 30 November. Bambora has to be on Shift4 before December.

Read together, OwnerRez is consolidating onto a much smaller set of card processors, and legacy connections are being retired on a timetable rather than left to wither. For most hosts that is fine and probably overdue, because fewer supported processors means fewer half-maintained integrations. For anyone whose merchant account is tied to a specific processor by an existing agreement, or whose owners have their own accounts, it is a month of admin that arrived with a deadline attached.

The rest of the release

The 28 October notes are mostly fixes, several of them worth checking against your own data rather than assuming the fix is enough.

Booking.com listings could become permanently unbookable when a room type was closed outside OwnerRez. Vrbo commission imports were not crediting rows as negative fees. QuickBooks customer mappings could be recorded incorrectly when owner payouts were booked as bills. Airbnb pricing sync failed when yesterday's rate was lower than today's.

Two smaller changes affect what guests see. The Extend My Stay link in guest messages now lasts seven days instead of three hours, which should cut the number of guests clicking a dead link. And Vrbo headline and description limits have been updated to match Vrbo's current requirements, now 20 to 40 characters for a headline and 400 to 10,000 for a description, so listings written to the old limits may need trimming or padding.