A 71-comment community thread on 365's transaction review delays surfaced one clear finding: most operators don't know what's normal, which means they're either panicking over expected behavior or missing actual problems. Here is the breakdown.
365 is the market-leading platform for enterprise vending and micro-market operators. Their transaction review process — the time between a customer completing a purchase and that transaction appearing as confirmed in the operator portal — has been a recurring source of confusion. Understanding what's normal, what's a problem, and what fixes each state saves hours of unnecessary support calls.
What is normal: 6–12 hours
365's transaction review process batches transactions for fraud screening and payment gateway processing. Under normal operating conditions, transactions complete review and appear in your portal within 6–12 hours of the original sale. A sale at 2pm typically shows confirmed by midnight to 2am, sometimes earlier.
Weekend processing runs slightly slower due to reduced gateway staffing at the processor level. A Friday 5pm transaction may not confirm until Saturday morning. This is expected, not a bug.
When it becomes a problem: 18+ hours
Transactions in review for more than 18 hours, particularly on weekdays, fall outside normal range. Causes the community has identified:
- Gateway delays: 365 uses third-party payment processors. When gateway volumes spike (major consumer holidays, payday Fridays in dense markets), review queues back up. These typically self-resolve within 24–36 hours.
- Weekend batching edge cases: Transactions processed late Friday that don't clear the weekend batch run can sit through the full weekend. Expected resolution by Monday morning.
- Network sync issues: The machine is physically connected and processing sales but hasn't synced its transaction log to the 365 cloud. Caused by intermittent connectivity. Check the machine's connection status in the 365 operator portal — if it shows offline or last-sync older than 4 hours, connectivity is the issue, not the review queue.
- Machine-level software errors: Specific machine software states can cause transactions to batch but not transmit. Reboot the machine (with 365 support guidance) to force a sync in these cases.
Picture the machines paying you while you sleep
That’s the real promise of vending — income that doesn’t cost you your time, and a life on your own terms. VendBuddy turns this guide into a step-by-step plan so you actually build it instead of just reading about it. Start free today.
Start building free →How to diagnose the root cause
- Check the 365 operator portal status page for any platform-wide gateway incidents. If there's a listed incident, wait it out — your call to support won't speed resolution of a platform-wide issue.
- Check the machine's last sync time in the portal. If last sync was more than 4 hours ago, connectivity is the likely issue. See connectivity troubleshooting for root cause steps.
- If connectivity is confirmed good and no platform incident is listed, open a support ticket with the specific transaction IDs and timestamps. 365 can pull transaction logs on their side and identify whether the issue is gateway, machine, or portal-specific.
When to call vs. when to wait
Wait it out: 6–18 hours on a weekend, any transaction review delay with a concurrent platform status incident. Call support: any transaction delay beyond 24 hours on a weekday with no status incident, any pattern of recurring delays (same time window, same machine repeatedly), or any transaction showing as "declined" that you believe should have processed.
VendBuddy's operator dashboard flags machines with stale transaction data and unusual review lag so you know when to escalate before the delay compounds.
Try VendBuddy free →FAQ
How long should 365 transaction review take?
6–12 hours under normal operating conditions. Weekend transactions can take up to 24 hours due to reduced gateway staffing. Delays beyond 18 hours on weekdays without a platform status incident are worth investigating: check connectivity, then open a support ticket with specific transaction IDs.
Why do 365 transactions stay in review for so long?
365 batches transactions for fraud screening and payment gateway processing. Delays beyond normal range are typically caused by gateway volume spikes, machine connectivity issues that delay the sync, or specific machine software states that prevent transmission. Check the platform status page and machine last-sync time before calling support.
What should I do if my 365 transactions haven't cleared in 24 hours?
First check the 365 platform status page for any announced gateway incidents. Then check the machine's last sync time in the portal. If connectivity is confirmed good and there's no platform incident, open a support ticket with the transaction IDs, timestamps, and machine ID. 365 support can pull server-side logs to identify where the delay is occurring.
Related: how to read your vending sales reports, smart cooler connectivity troubleshooting, HAHA vs Stockwell vs 365 vs Cantaloupe, managing multiple vending platforms.