Drive-Through Revolution: BLE Proximity Payments

Based on aggregated data from payware partner deployments. Names and identifying details have been changed.

A quick-service restaurant chain with 85 locations puts €42 million a year through its drive-through lanes. It pays €462,000 in card processing fees, and it loses an estimated €225,000 a year in abandoned orders: forgotten wallets, declined cards, and queues made longer partly by slow payment.

With Bluetooth Low Energy (BLE) proximity payments taking 28% of drive-through volume, the chain saves €70,560 in processing, recovers €106,000 of the orders it used to lose, and cuts payment time from 38 seconds to 8.

No commerce environment is as time-sensitive as a drive-through. Every second of transaction time shows up in throughput, queue length and customer mood. Payment ought to be invisible: as the car approaches, the phone picks up a beacon, the customer gets a notification with the amount, confirms with Face ID or a PIN, and the transaction is done before the window.

A card needs physical handling. Hand it to the employee, insert or tap, wait for authorization. That takes time, and every one of those steps is a point where an order can be lost.

Here is how BLE proximity payments are changing drive-through commerce.

The Drive-Through Payment Challenge

Time Is Revenue

A drive-through serves a vehicle in 180 to 240 seconds, aims for 15 to 20 vehicles an hour per lane, and spends 25 to 40 seconds of each service on payment, which is 13-22% of the total.

At lunch (12 to 1:30pm) and dinner (5:30 to 7pm), demand exceeds what the lane can handle. The queue spills past the property line and customers give up. Every second shaved off service time is another vehicle served.

Take a single lane open 16 hours a day. At 17 vehicles an hour it serves 272 vehicles a day, 8,160 a month. Cut service time by 10% and it serves 18.7 an hour, 299 a day, 8,970 a month. That is 810 more vehicles a month at an average of €8.50, €6,885 a month, €82,620 a year, from one lane.

Faster payment means higher throughput means more revenue.

Payment Friction Points

A card payment at the window has four places where time leaks.

The physical handoff takes 5 to 8 seconds: the customer finds the card, hands it through the window, the employee processes it, hands it back, and the customer puts it away. The terminal takes 3 to 10: it does not respond, the connection times out, the customer is not sure whether to insert or tap, and someone retries. Authorization takes 2 to 5: card network routing, issuer authorization, the response, the confirmation on screen. And a declined card takes 30 to 90 seconds: the decline, the customer trying another card, or the customer giving up and leaving.

Total payment time: 25 to 40 seconds on average.

Order Abandonment

Three things make a drive-through customer leave without buying. They arrive and realize they have no wallet (2-3% of customers). Their card is declined and they have nothing else (0.8-1.2%). Or they see the queue at peak and never join it (5-8%).

For the 85-location chain that is €73,000 a year lost to forgotten wallets, €44,000 to declined cards and €108,000 to long queues, the last of which is partly a payment-speed problem.

Proximity-based payment can recover the first two outright: €117,000.

Mobile App Payment (Partial Solution)

The usual answer is order-ahead: order in the merchant’s app, pay in the app, collect at the window. It removes the payment time at the window and the card handoff, and the order is ready when the customer arrives.

What it does not do is reach most customers. It needs a download, it needs planning ahead, and a lot of drive-through visits are spontaneous. Adoption typically sits at 12-18% of customers.

The other 82-88% still need a way to pay in the lane.

How BLE Proximity Payment Works

The Technology

Bluetooth Low Energy is short-range wireless with a configurable range of 2 to 50 meters, low power draw, automatic beacon detection by the phone with no pairing, and encrypted communication.

In a drive-through, beacons sit at four points along the lane. A detection zone 20 to 30 meters before the order point, where the phone picks up the signal as the car approaches. An order confirmation zone at the speaker and menu board, where the order and amount are confirmed. A payment authorization zone 5 to 10 meters before the window, where the customer gets the notification and authorizes. And a completion zone at the window, where the payment is confirmed and the order handed over.

Customer Experience

Setup happens once. The customer installs the merchant’s app or already has a payware-enabled banking app, enables BLE proximity payment with a single permission, connects a bank account, and never has to touch the settings again.

From then on, every visit goes the same way. The car enters the lane with the phone in a pocket or the cupholder. The phone detects the beacon. The customer orders at the speaker and the order is confirmed with the total. The phone buzzes: “Authorize €12.50 payment to [Merchant]?” The customer checks the amount and confirms with Face ID or a PIN, which takes about 2 seconds, and the payment is authorized only after that confirmation. At the window the payment is already complete and the order is handed over.

Two seconds of customer confirmation, 8 seconds for the whole payment flow, against 25 to 40 for a card. No card to find, no handoff, no terminal. The customer reviews and approves while rolling forward, and nothing is charged without that explicit approval. A glance at the notification and a tap or a fingerprint is all it takes.

Use Case 1: QSR Chain with 85 Drive-Through Locations

A burger, fries and drinks chain with 85 locations in Belgium and the Netherlands takes 72% of its revenue through the drive-through, €58M of €80M. Of the €42M of drive-through card volume, 73% is cards and 27% cash. The average order is €8.50 across 4.94 million drive-through transactions a year, with peaks at lunch (12 to 1:30pm) and dinner (5:30 to 7pm).

Current Payment Economics

Card processing runs at an average of 1.1%, €462,000 a year, about €0.09 per transaction.

Payment takes 38 seconds on average against a target of 20, an 18-second overhead per transaction. Throughput averages 17 vehicles an hour, peak capacity is capped by the 180-second service time, and payment is 21% of that service time (38 of 180 seconds).

Abandonment costs €225,000 a year: €73,000 to forgotten wallets (2.5% of potential customers), €44,000 to declined cards (0.9%) and €108,000 to long queues, which are partly a payment-speed problem.

BLE Proximity Payment Implementation

Each lane got three beacons (detection, order, payment), integrated with the POS, with payware A2A payment processing behind them and a BLE proximity feature added to the merchant’s app.

The rollout took four months: 10 pilot locations in months 1 and 2, the remaining 75 in months 3 and 4. Hardware cost €850 per lane for three beacons and installation, €72,250 across 85 lanes.

Customers learned about it from in-lane signage (“Enable proximity payment in app”), an app notification on entering the car park (“Try proximity payment?”), staff mentioning it to regulars, and a QR code at the menu board for the app download.

Adoption Pattern

By month 3, 6% of drive-through transactions at the pilot locations were going through BLE, led by regulars who visit twice a week or more. By month 6 it was 14%, with word of mouth doing the work. By month 12 it was 22% and normal among the regular customer base. By month 24 it was 28% overall: 52% among regulars (two or more visits a week) and 12% among monthly customers.

Financial Impact at 28% BLE Adoption

Processing: €11.76M of BLE A2A volume (28% of €42M) at 0.5% costs €58,800, and the remaining €30.24M of card volume at 1.1% costs €332,640. Total processing €391,440, a saving of €70,560.

Throughput: a BLE payment takes 8 seconds (2 seconds of customer authorization while driving forward, 6 seconds of order handoff) against 38 for a card, saving 30 seconds per BLE transaction. With 28% of transactions on BLE, the blended saving is 8.4 seconds per transaction, taking blended service time from 180 to 171.6 seconds, about a 5% throughput gain at peak: from 17 vehicles an hour to about 17.8, roughly 0.8 more an hour. Across the chain’s peak hours that is about 12,500 additional vehicles a year, €106,250 in additional revenue at €8.50.

Abandonment: 80% of the forgotten-wallet customers who have the app come back, €58,400; 90% of the declined-card customers, now paying from a bank account, go through, €39,600; and faster payment shortens the queue enough to recover another €8,000. Recovered revenue: €106,000.

Total annual impact: €70,560 in processing, €106,250 in throughput, €106,000 in recovered orders. Combined: €282,810.

ROI Analysis

Implementation cost €205,750: €72,250 for BLE hardware, €55,000 for POS integration, €48,000 for app development, €18,000 for the pilot and €12,500 for signage and marketing.

Against €282,810 a year in recurring benefit, that breaks even in 8.75 months, call it nine.

The five-year NPV at an 8% discount rate and no terminal value: €261,861 in year 1, €242,546 in year 2, €224,452 in year 3, €207,948 in year 4 and €192,519 in year 5, about €1,129,326 in total, less the €205,750 investment: roughly €923,576. Operators should apply their own cost of capital.

Operational Insights

Regulars adopted at 52% against 12% for occasional visitors. Speed was the draw; customers notice the time saved. Staff handle fewer cards and fewer declines.

Some benefits were unplanned. Customer satisfaction scores rose 8%. Staff concentrate on order accuracy instead of payment. Cash handling costs fell, because BLE customers rarely switch back to cash.

Some things needed fixing. Customers were initially confused about how it works, which clear signage and staff training resolved. 8-10% were unsure about the authorization flow at first; the message “you review and approve every payment” settled that quickly. And beacon batteries need replacing every 18 to 24 months.

Three optimizations followed. The authorization zone moved closer to the window, from 20 meters to 10, which times better with the order confirmation. A voice prompt was added at the speaker: “Your €12.50 payment request is ready - check your phone to authorize.” And the high-traffic locations were identified for priority rollout, since the return varies with volume.

Use Case 2: Coffee Drive-Through Chain (45 Locations)

A specialty coffee drive-through concept with 45 urban and suburban locations takes 95% of its revenue through the lane, €28M a year, on 4.5 million transactions at an average of €6.20, from customers who come daily.

Current Payment Economics

Cards cost 1.3%, the rate of a smaller merchant, €364,000 a year. The transaction value is low (€6.20 against the QSR’s €8.50), so the €0.081 processing cost per transaction is a bigger share of the order, the customer base visits daily, and speed matters even more because the morning rush is 65% of the day’s volume.

BLE Proximity Payment Implementation

The target was the daily and regular customers who visit four or more times a week: 42% of the customer base and 68% of transactions. The pitch was “Your daily coffee, zero friction - review your total and tap once to pay”, tied into the loyalty program: “Enable proximity payment, earn double points.”

Adoption Pattern

Adoption ran well ahead of the QSR chain: 22% at month 6 (against 14%), 35% at month 12 (against 22%), 48% at month 24 (against 28%).

The reasons: daily routines form habits faster, a low transaction value feels low-risk, the urban coffee demographic is younger and comfortable with technology, and the morning rush makes the time saving tangible.

Financial Impact at 48% Adoption

Processing: €13.44M of BLE A2A volume at 0.5% costs €67,200, the €14.56M of card volume at 1.3% costs €189,280, and the saving is €107,520.

Throughput has to be blended, since only 48% of customers use BLE: 48% of 30 seconds is 14.4 seconds per transaction, taking blended service time from 180 to 165.6 seconds, about a 9% gain during the morning rush. The rush runs at 20 vehicles an hour, constrained by the 180-second service time; at 165.6 seconds it runs at about 21.8, roughly 1.8 more an hour. Over 1,095 rush hours a year (3 hours a day), that is about 1,971 additional vehicles at €6.20, roughly €12,220.

Total impact: about €119,740.

ROI Analysis

Implementation cost €125,000 against about €119,740 a year in benefit: break-even in about 13 months.

Unique Insight

For high-frequency, low-value transactions, removing friction matters more than cutting cost. The processing saving here is €107,520 and the throughput gain about €12,220, but the speed benefit for a daily customer compounds over hundreds of visits a year.

Use Case 3: Pharmacy Drive-Through (12 Locations)

A pharmacy chain runs drive-through prescription pickup at 12 locations, €8.2M a year in drive-through volume at an average of €32 per transaction, 60% prescriptions and 40% retail.

Unique Characteristics

It is nothing like food service. Visits are infrequent (monthly refills), the transaction value is high (€32 against €6-8), the customers are older (45% over 60), and there are healthcare privacy concerns.

BLE Implementation Results

Adoption was lower, as the demographic predicted: 12% at month 12 and 18% at month 24, with 35% among customers under 45 and 6% among those over 60.

It still paid. €14,400 in processing savings, €8,200 in throughput, €12,000 in recovered abandonment: €34,600 a year, breaking even in about 16.8 months.

Even with a less receptive demographic, the return is positive. An implementation does not need 40% adoption to be worthwhile.

Implementation Best Practices

Technical Requirements

Three beacons do the work. The detection beacon, 25 to 30 meters before the order point, broadcasts the signal the phone picks up on approach, gives the phone the payment context and gets the payment infrastructure ready. The order confirmation beacon at the speaker confirms the order details and shows the amount on the phone while the customer orders. The authorization beacon, 8 to 12 meters before the window, sends the authorization request to the phone; the customer reviews the amount and confirms with Face ID or a fingerprint, and the payment is processed during the drive forward, only after that approval.

Beacon range is adjustable from 2 to 50 meters and tuned to the lane. The broadcast interval is 100ms for fast detection. Batteries last 18 to 24 months and are replaceable. The units are IP67 rated for outdoor use.

POS Integration

The POS needs to talk to the beacons, receive payment status in real time, match each payment to the right order, fall back to card if a BLE payment fails, and tell staff which payment method was used.

A modern cloud POS integrates in 3 to 4 weeks. A legacy POS takes 8 to 12 and may need middleware.

Customer Onboarding

Setup in the app: install the merchant’s app (or use a banking app with payware integration), grant the BLE proximity permission, connect a bank account, and optionally set authorization preferences such as always requiring a biometric or PIN, or a maximum amount for proximity authorization.

In the lane, the first time: the phone shows “Try proximity payment?”, the customer taps “Yes” or “Not now”, a 15-second tutorial overlay explains the review-and-confirm flow, and the customer reviews and authorizes the first payment. Every later visit is the same quick notification and confirm.

The first use has to be easy. Clear instructions at the menu board, staff trained to help, a notification that walks the customer through the authorization step, and a tutorial mode for the first transaction.

Staff Training

Staff need five things: how BLE payment works, including that the customer always reviews and confirms before any charge (a 3-minute overview); what the customer gets from it (speed, convenience, security, explicit control); when to mention it (regulars, tech-comfortable customers); how to troubleshoot the common problems (the phone not picking up the beacon, an authorization delay); and the fallback, which is a card, without fuss.

That takes 30 to 45 minutes per employee. Staff should also try BLE payment themselves on test accounts, so they know the authorization flow from the customer’s side.

Demographic Targeting

Adoption runs highest among regulars (two or more visits a week), people aged 18 to 45, smartphone users (every one of them is addressable) and early adopters. It runs at a medium level among occasional customers (two to four visits a month), people aged 45 to 60, and mobile banking users. It runs lowest among first-time customers who do not know the location, people over 60 with lower mobile banking adoption, and customers who prefer cash.

So start with the regular, tech-comfortable customers, build a base, and let social proof and word of mouth carry it from there.

Common Drive-Through Questions

”What if customer’s phone is off or dead battery?”

Then it is a card payment. The customer enters the lane, the phone does not pick up the beacon, the POS defaults to standard card payment, and the customer pays at the window as always. Nobody is excluded or inconvenienced.

BLE proximity is an enhancement, not a requirement. Every customer can still pay with a card.

”What about privacy - tracking customers in drive-through?”

A phone only responds to the beacons if the payment app is installed and BLE is enabled, so there is no tracking without opting in. The beacons broadcast a signal but have no awareness of nearby devices; the phone decides whether to respond. Location data is not kept past the end of the transaction.

The customer can switch proximity payment off at any time in the app, set it to ask every time rather than remember the location, and see their transaction history and where it was used. The app’s privacy policy spells out what is collected: transaction information only, no persistent location tracking.

”What if customer drives away before payment completes?”

Say the customer authorizes the payment and then drives off before getting the order. The payment is authorized (the funds are locked in the customer’s account), the customer leaves, staff mark the order as not fulfilled, the payment is refunded automatically within 15 seconds, and the customer gets a notification: “Order not received, payment refunded.”

The reverse fraud, authorizing, taking the order and claiming it never arrived, does not work either, because staff mark an order fulfilled only when it is handed over.

An operator that wants to eliminate the edge case entirely can move authorization to the window instead of earlier in the lane. It is slower. It is a trade between speed and edge-case prevention.

A family with one phone and several drivers is fine. BLE payment is tied to the app, not the vehicle. Whoever has the phone in the car sees the authorization request for that visit, and a driver without the app pays by card.

BLE never assumes that this vehicle means this payment method. The phone in the car picks up the beacon, whoever is driving.

Why Drive-Through Is Ideal for BLE Proximity

Time Sensitivity Amplifies Value

In a store the customer has finished shopping and the time pressure is low. In a car at peak hour it is high. The same 30-second saving is worth more in a drive-through.

Minimal-Interaction Context

The customer is in a car with the phone in a pocket or the cupholder, hands on the wheel, concentrating on rolling forward. Reaching for a wallet and handing a card through the window is awkward. With BLE the phone stays where it is; the customer glances at the notification, checks the amount and taps while waiting in the lane.

High-Frequency Customer Base

QSR drive-through customers often come two to four times a week. Core coffee customers come daily. Frequency builds habit. After three BLE payments, 89% of customers become regular BLE users, and 94% of regular BLE users prefer it to cards (payware deployment data).

Constrained Physical Environment

A drive-through lane is a straight, predictable path: enter (the phone detects the beacon), reach the speaker (order), roll forward (review the notification and authorize), reach the window (collect). That makes beacon placement easy and BLE performance reliable, unlike a store where customers wander and paths are unpredictable.

The Competitive Landscape

Early Movers Capture Regular Customers

Once a customer has enabled BLE proximity at one location, they use it every visit, and a competitor without it feels like a step backwards. A customer who frequents Coffee Chain A (with BLE) and Coffee Chain B (card only) starts preferring the faster one, and payware deployment data shows measurable shifts in visit frequency toward BLE-enabled locations.

BLE proximity payment becomes a reason to choose one drive-through over another.

Marketing Differentiation

The messages write themselves: “Fastest drive-through in town - proximity payment.” “Review and pay in one tap - no card needed.” “Zero-friction coffee - enable proximity payment once, use forever.” They land with time-conscious customers in the morning rush and the lunch break, with tech-forward early adopters, and with the regulars.

Throughput as Profit Center

The traditional view treats payment processing as a cost center to be minimized. BLE reframes payment speed as a profit center to be maximized. In the QSR case the processing saving was €70K a year and the throughput gain €106K. Throughput was worth 1.5 times the cost saving.

Implementation Roadmap

Months 1 and 2 are planning and pilot: pick 5 to 10 high-traffic locations with varied demographics, install the beacons, integrate the POS, test with staff and friendly customers, and measure the payment time reduction and customer feedback.

Months 3 and 4 optimize the pilot: adoption by location, beacon placement and the timing of the authorization zone, customer messaging and signage, staff training from the pilot’s lessons, and throughput at peak.

Months 5 to 7 are the chain-wide rollout, phased by region, with a customer marketing campaign, adoption and performance monitoring, and troubleshooting support for the locations.

Months 8 to 12 are optimization: adoption by customer segment, what the best locations do differently, those tactics applied to the laggards, and the financial impact measured across processing, throughput and abandonment.

From month 13, BLE proximity is the standard offering: continuous monitoring and maintenance, a beacon battery schedule, and every new location gets it from opening day.

Next Steps for Drive-Through Operators

Five things to do now:

Put a cost on payment time: average payment time, times transaction volume, times the throughput impact per hour.
Model the throughput gain: how many more vehicles could you serve at peak with 30 seconds off each payment?
Size the addressable market: what share of customers visit twice a week or more?
Check POS compatibility: can your POS integrate with a BLE beacon system?
Project the return: implementation cost against processing savings, throughput gains and recovered orders.

The decision framework: more than 30% high-frequency customers means strong adoption potential. A throughput-constrained peak means the throughput gains are worth more. Payment time above 30 seconds means more time to save. A tech-comfortable customer base means faster adoption.

For most QSR and coffee drive-throughs, BLE proximity payments pay back within 9 to 17 months depending on adoption and demographics.

Want to implement BLE proximity payments for your drive-through?

payware provides BLE beacon infrastructure and A2A payment processing for drive-through operations. Proximity-based payment with 0.5% flat fees, instant settlement, and 8-second transaction times.

Implementation timeline: 8-12 weeks
Hardware cost: €850 per lane
Processing fees: 0.5% (vs 1.0-1.5% for cards)
Payment time: 8 seconds (vs 25-40 for cards)
Throughput impact: 5-9% blended during peak hours

Learn more: payware.eu
Contact: Get in touch

About payware

payware is the neutral transaction resolution network for instant account-to-account (A2A) payments worldwide. Banks query payware to resolve transactions - receiving merchant name, amount, currency, and the optimal merchant bank account. Payment institutions keep full control of authentication, accounts, and funds movement. ISVs integrate payware to onboard merchants to the ecosystem. With 7 innovative payment initiation methods - QR code, NFC, BLE, soundbite, text, link, and barcode - payware delivers exceptional end-user experiences while offering fees as low as 0.5% and instant settlement. Founded in 2019, payware creates unprecedented value through domestic interoperability.

Related Posts