OwnerRez closes five payment processors to new connections, and Bambora users have until December

OwnerRez's 21 October update is mostly bug fixes, but buried in the tweaks are five payment processor changes and one migration deadline. If you take card payments through anything other than Stripe or Lynnbrook, read this one.

What changed

New OpenEdge payment method connections are blocked. Existing OpenEdge connections keep working.

You can no longer add Payeezy, USAePay, eProcessing Network or Plug'n Pay payment methods at all.

And the line that carries an actual deadline: Bambora payment processing must be migrated to a new Shift4 connection before December 2026.

OwnerRez does not state a specific day in December, and it does not say what happens to a Bambora connection that is still in place after the cutoff. If you are on Bambora, that ambiguity is reason to start the move now rather than to wait for a firmer date.

Why this matters even if you are not on Bambora

The OpenEdge wording is the one people miss. Your current connection is fine. Adding another one is not possible. So if you run a property per processor setup, or you are about to onboard a new property or a new owner entity that needs its own merchant account, you no longer have that option on OpenEdge and will be moving to a supported processor anyway. Better to find that out while planning than at the point of going live.

Taken together, five processors closing in one release is a consolidation, not a coincidence. OwnerRez is narrowing the set of card processors it maintains, and the direction of travel for anyone on a legacy connection is clear.

The rest of the release

Two enhancements. Owner bookings can now be made on any property through an owner booking contact. And OwnerRez has improved how it detects Booking.com channel connection errors, with suggested fixes rather than just a failure.

Among roughly fifty bug fixes, three are worth checking against your own records.

Owner statements were overpaying owners when a Stripe payout included a guest refund. If you run owner statements off Stripe payouts, it is worth reviewing recent statements rather than assuming the fix is enough.

Booking.com listings were showing cribs as extra twin beds, and linens, towel and Norwegian cleaning fees were importing as a generic other surcharge instead of matching your property surcharges. Both would have been distorting what guests saw and what your reports said.

QuickBooks deposit syncing is now disabled by default when no bank account is configured. That is a changed default, so if your QuickBooks deposit sync quietly stopped, this is probably why.

There are also fixes to Rezzy AI host directives, which now control reply silence, voice and host name usage across all escalation settings, and to MCP connected assistants that were counting bookings incorrectly when results spanned several pages. OwnerRez opened its MCP server to everyone at the start of October, so that counting bug will have been visible to anyone asking an AI assistant how many bookings they had.

What to do

Check which processor each of your payment methods uses. If any of them is Bambora, book the Shift4 migration in before December. If any is OpenEdge, Payeezy, USAePay, eProcessing Network or Plug'n Pay, you are on a connection with no path to being extended, and the time to plan a move is while it still works.