A parking operator running a procurement today will notice something that was uncommon five years ago: the PARCS or mobile-payment vendor is not proposing to integrate with your processor. They are proposing to be your payments provider, with rates in the software quote and no separate acquirer relationship at all.
This is not parking-specific. Embedded payments revenue is projected to reach roughly $59 billion in 2027, up from about $32 billion in 2023, and software companies have become the primary distributors of payments in their verticals. Boards and investors now expect a platform to monetize its transaction flow. Parking software is simply arriving at the same place hospitality and healthcare software arrived at earlier.
What matters for an operator is that this changes the shape of the relationship in ways the pricing comparison does not capture.
The Models Behind the Pitch
“Embedded payments” covers several arrangements with materially different consequences. When a vendor says payments are included, the useful question is which of these they are running.
Referral or revenue share. The vendor introduces you to a processor and takes a share. You hold the merchant account, you have a direct acquirer relationship, and you can leave.
Registered ISO. The vendor is a registered reseller for a processor. More integrated, more of the service relationship runs through the vendor, but the underlying merchant account is still yours.
PayFac-as-a-service. The vendor embeds facilitation capability provided by another party — Stripe, Finix, Rainforest, Worldpay, and similar — without running the full program themselves. You are typically a sub-merchant.
True payment facilitator. The vendor holds the master merchant account and onboards you as a sub-merchant underneath it. They assume underwriting, fraud, and chargeback liability, and they control the relationship end to end.
The last two are where the operator’s position changes most, because in both you are a sub-merchant rather than a merchant.
What Sub-Merchant Status Actually Changes
Onboarding gets much faster. Facilitators onboard sub-merchants under their own master agreement, often with near-instant approval and no separate underwriting cycle. For an operator adding locations — a new garage, an event site, a management contract that starts in three weeks — this is a genuine operational gain. Traditional merchant account underwriting on a per-site basis is slow in exactly the situations where speed matters.
Funding timing is set by someone else. Your settlement timing is a function of the facilitator’s funding schedule and their risk view of your account, not a term you negotiated with an acquirer. For an operation with revenue-share obligations to municipalities or property owners on fixed dates, confirm the funding schedule in writing and ask specifically what triggers a hold.
Reserves become a live risk. Facilitators manage risk across a sub-merchant portfolio and can impose reserves or holds on an account whose pattern changes. Parking generates exactly the patterns that look anomalous to an automated risk model: a stadium event producing a hundredfold single-day volume spike, seasonal university surges, a new site coming online with no history. Ask directly how the facilitator’s risk engine treats event-driven volume, and get the answer before signing rather than during a playoff run.
Dispute handling moves. Chargeback response may run through the vendor’s process and interface rather than your acquirer’s. Parking has a distinctive dispute profile — unattended transactions, thin cardholder recall, LPR and entry/exit amount questions — and the vendor’s representment workflow needs to accommodate evidence types like gate events, plate reads, and session records. A generic e-commerce dispute form is a bad fit for this.
Switching cost concentrates. This is the structural point. When the software vendor is also the payments provider, changing processors and changing software become one decision instead of two. That is a substantial transfer of leverage at renewal, and it compounds if the terminals are also keyed to that provider’s encryption solution.
The Case For It Is Real
None of this is an argument against embedded payments, and operators should resist treating it as one.
A single integrated stack removes the reconciliation seam between the parking system and the payment system, which is where a meaningful share of revenue-reconciliation labor actually goes. Support gets simpler — one vendor owns the failure, rather than a PARCS provider and an acquirer each pointing at the other while a lane sits down. Rates bundled into a software deal are sometimes genuinely competitive, because the vendor is monetizing the relationship across two lines and can price either one aggressively.
For smaller operators especially, the alternative to embedded payments is not an optimally negotiated direct acquirer relationship. It is an under-negotiated one plus an integration project.
Questions to Put in the Procurement
Which model is this, precisely? Referral, ISO, PayFac-as-a-service, or true PayFac. Get it named in the agreement.
Am I the merchant or a sub-merchant? This single answer determines most of what follows.
Who is the merchant of record, and whose master agreement governs?
What is the funding schedule, and what triggers a hold or reserve? With a specific answer on event-driven volume spikes.
What is the full rate card? Interchange treatment, markup, per-transaction fees, chargeback fees, monthly minimums, and gateway charges — itemized, not bundled into one blended percentage.
Who handles disputes, in what system, and what evidence types are supported?
What happens at termination? If we keep the software and change payments, is that possible and at what cost? If we change software, what happens to tokenized stored credentials for monthly parkers? Token portability is the item most often discovered too late.
Is the encryption solution processor-coupled? If the pay stations are keyed to this provider’s P2PE solution, the software decision and the hardware decision are now the same decision.
The Framing That Helps
The useful posture is neither resistance nor default acceptance. It is recognizing that a bundled payments offer is a second contract wearing the first one’s cover page.
Price it separately even when it is sold together. Ask what the software costs without payments, and what payments cost through a direct relationship. If the vendor cannot or will not unbundle for the purpose of the comparison, that itself is information about how much of the deal’s economics live in the transaction flow — and about how much leverage you will have the next time it comes up for renewal.
