Shift4 says Givex gift-card, loyalty and B2B card services have been restored following a disruption first reported on October 31. Reporting remains degraded in Canada and Europe, according to its November 4 update at 23:59 UTC, leaving transaction recovery and back-office reporting on different tracks. [1]

Payment recovery preceded formal incident closure

The disruption affected the functions that make a stored-value card usable: checking a balance, activating or redeeming a card, and making an online purchase. Shift4 initially described preventative maintenance, then reported phased restoration. Some merchants regained service while others were still affected. Its bulletins do not establish a single recovery time for every customer. [1]

Olo, which connects its customers to Givex payment processing, issued two separate incident reports. In the first, the interval from its initial October 31 alert to a notice that gift-card balance checks and payments were succeeding again was 912 minutes, or 15 hours 12 minutes. Formal resolution followed at 1,117 minutes, or 18 hours 37 minutes, after the initial alert. [2]

The data behind the story

Olo Givex incidents: time between recovery notices

Elapsed minutes from each initial Olo incident bulletin to its normal-transactions monitoring notice and formal resolution. These are provider reporting intervals, not measured uninterrupted downtime.

minutes between status notices
Sources
Olo: initial Givex incident, 31 October to 1 November 2026 ; Olo: recurrent Givex incident, 1 to 2 November 2026

Calculated from the displayed timestamps to one-minute precision, including the change from EDT (UTC-4) to EST (UTC-5). Successful transactions were reported before formal closure. The notices do not quantify affected locations, failed transactions, card balances or lost sales. Do not add these intervals into a downtime total.

Show data tableHide data table
Scroll left or right to see all columns
Olo Givex incidents: time between recovery notices (minutes between status notices)
CategoryTo normal-transactions monitoringTo formal resolution
Initial incident, 31 October912 minutes between status notices1,117 minutes between status notices
Recurrence, 1 November20 minutes between status notices1,100 minutes between status notices

A recurrence on November 1 produced a much shorter interval to normal-transactions monitoring: 20 minutes. Olo did not formally close that incident until the next morning, 1,100 minutes after the first bulletin. The contrast matters because the age of an open incident includes time spent checking that recovery holds. It does not show that payments failed continuously until closure. [3]

Olo warned that affected guests could encounter slow-loading payment options as well as failed gift-card checks or payments. It said other payment methods were working normally. That identifies a problem with the Givex route in those notices, rather than evidence that every payment method at affected businesses had stopped. [2] [3]

The wider Shift4 updates describe a more uneven recovery. Core services were reported restored across several regions on November 1, but later notices still identified configuration problems and partial B2B-card restoration. By November 4, the restored list included Givex Gift, Loyalty, B2B Cards, point-of-sale functions and online-ordering payments. Reporting was still catching up, with Canada and Europe specifically named as degraded. [1]

For merchants, restored redemption permits customers to spend existing balances again, while delayed reporting leaves a separate reconciliation task. The notices disclose neither affected transaction volumes nor lost sales. They also do not establish a cyberattack, lost stored value or a change to cardholder terms. The reported timing therefore measures the providers' recovery communications, not the financial cost or total duration of the disruption. [1] [2] [3]

Image: Shift4 logo, used as a contextual illustration of the company issuing the Givex status updates. Paul.jonah.paul / Wikimedia Commons, CC BY-SA 4.0. Resized and converted for this publication. [4] [5]