How Value-Added Reseller (VAR) Works
A Value-Added Reseller is not simply a middleman passing products along a supply chain. The "value-added" designation is the operative distinction: VARs integrate, configure, and extend a base product before it reaches the end merchant. In the payments context, this means wrapping a payment terminal or processing platform inside a larger commerce solution tailored to a specific industry or use case.
The typical lifecycle of a VAR engagement follows a repeatable pattern, from sourcing technology to long-term merchant support.
Source hardware and software
The VAR establishes wholesale relationships with payment terminal manufacturers such as Ingenico, Verifone, or PAX, as well as POS software vendors and processors. They negotiate volume pricing and acquire hardware or software licenses at a discount to their resale price, forming the margin foundation of the business.
Configure and integrate
Raw hardware is loaded with certified payment applications, integrated with the VAR's proprietary or licensed software, and tested against the target acquirer's processing environment. This configuration stage—custom receipt templates, inventory system connections, loyalty integrations, industry-specific payment flows—is where genuine differentiation is created.
Bundle and price the solution
The VAR packages hardware, software licenses, installation services, and an ongoing support contract into a single offer. Payment processing is typically included via a referral arrangement with an independent sales organization or through a direct ISO registration the VAR holds with an acquiring bank.
Onboard the merchant
Installation technicians or remote support teams deploy the solution at the merchant location. Staff are trained on both the software and payment workflows, and the environment is tested end-to-end before going live. Merchant underwriting is handled by an acquirer, a payment facilitator, or a processor partner depending on the VAR's channel structure.
Provide ongoing support and earn residuals
Post-deployment, the VAR becomes the merchant's primary contact for hardware, software, and payment issues. In exchange for bringing merchants onto a processing network, the VAR earns monthly residuals based on payment volume—building a recurring revenue stream that compounds as the installed merchant base grows.
Why Value-Added Reseller (VAR) Matters
VARs are a foundational layer of how payment infrastructure reaches the market. Processors and acquirers rarely have the local knowledge or vertical-specific expertise needed to serve every restaurant, clinic, or auto dealership directly—VARs fill that distribution gap at scale, acting as the last mile of payment technology deployment.
The economics are substantial. Industry research consistently shows that channel partners including VARs account for more than 60% of payment terminal placements in North American SMB and mid-market segments, with direct sales reserved for only the largest enterprise accounts. A Nilson Report analysis found over 1.1 billion payment cards accepted at merchant locations served predominantly through indirect channel partners—the category that includes VARs, ISOs, and dealer networks. The global POS terminal market exceeded $105 billion in 2023 (Straits Research) and is forecast to grow at a compound annual rate above 8% through 2031, with VARs as the primary distribution mechanism for that hardware.
Embedded payments trends are reshaping VAR economics further. Software-led VARs increasingly monetize payment flows natively within their platforms, capturing interchange revenue that was previously left with the processor. This shift is accelerating VAR consolidation and pushing the channel toward higher-margin, software-centric business models.
Channel economics
Processors estimate that serving SMB merchants via direct sales costs 4–6× more per merchant than reaching them through a VAR or ISO channel. The indirect channel model is not just convenient—it is economically necessary for the payments industry to serve businesses at scale.
Value-Added Reseller (VAR) vs. Integrated Software Vendor (ISV)
VARs and integrated software vendors are both technology-led channel partners, and their roles are frequently conflated. The distinction matters because the two models carry different payment integration depths, compliance obligations, and revenue structures. Understanding which model a vendor operates under helps merchants anticipate how payments will be supported over time.
| Dimension | Value-Added Reseller (VAR) | Integrated Software Vendor (ISV) |
|---|---|---|
| Primary product | Hardware + configured software bundle | Software application (SaaS or on-premise) |
| Payment integration | Embedded at hardware level, terminal-centric | API-level integration within software |
| Revenue model | Hardware margin + software fees + residuals | SaaS subscription + payment referral or rev-share |
| Merchant relationship | On-site installation and hands-on support | Software support, typically remote |
| PCI scope | Terminal hardware compliance (P2PE, SRED) | Payment SDK/API compliance, PA-DSS if applicable |
| Vertical focus | Retail, hospitality, healthcare POS | Often horizontal or multi-vertical |
| Onboarding speed | Moderate—hardware shipping and installation required | Fast—cloud software, no hardware dependency |
| Switching cost for merchant | High—hardware and software replacement | Moderate—software migration only |
The boundary between VARs and ISVs is narrowing. Software-first vendors increasingly offer hardware bundles, while hardware-led VARs are building or acquiring proprietary software platforms to reduce commoditization and improve merchant retention.
Types of Value-Added Reseller (VAR)
VARs span a wide range of business models, each with distinct implications for how payments are integrated, monetized, and supported. Understanding which type of VAR you are dealing with—or which model to adopt—clarifies both the opportunity and the compliance requirements.
Hardware-led VARs focus primarily on payment terminals and POS hardware. Their value-add is configuration, certification, and deployment. They partner with an ISO or processor for the payment component and earn residuals through referral arrangements. Margins are thinner and switching risk is higher because the software layer is often a third-party product.
Software-led VARs build or license a vertical-specific platform and resell it bundled with hardware. The software creates stickiness; hardware is the delivery mechanism. Many evolve toward a PayFac-lite or referral ISO structure to capture more of the payment economics directly.
Managed service VARs operate on a recurring monthly fee model, bundling hardware, software, payment processing, and full support under a single contract. This model is common in healthcare and hospitality, where merchants value predictable total cost of ownership.
Micro-VARs and dealer networks are smaller regional operators that resell solutions from a national VAR or hardware distributor. They provide hyper-local installation and support that larger channel partners cannot efficiently deliver, and they typically operate under a master ISO or sub-ISO agreement.
Cloud-integrated VARs combine traditional POS hardware with cloud-based software and API-driven payment processing, enabling modern embedded payments experiences within vertical SaaS platforms. This category is growing fastest as merchants increasingly expect unified commerce across in-store and online channels.
Best Practices
VARs operating in payments face a combination of technical, regulatory, and commercial obligations that generic channel partner playbooks do not address. Establishing clear practices across the merchant lifecycle determines whether a VAR builds durable, profitable relationships or faces chronic churn and compliance exposure.
For Merchants
Scrutinize the processing relationship before signing any VAR agreement. Confirm whether the VAR is a registered ISO, a sub-ISO, or a referral agent—this determines your recourse options in the event of pricing disputes, reserve holds, or service failures. Request full transparency on the payment cost stack: hardware purchase or lease terms, software subscription fees, processing rates, PCI compliance fees, and any support tier charges. Verify that terminal hardware is P2PE validated if reducing your PCI scope is a priority. Establish in writing who provides Level 1 support for payment failures during peak trading hours and request references from merchants of similar size and vertical before committing to a multi-year term.
For Developers and Integration Teams
Design for multi-acquirer portability from the first line of code. Hardcoding to a single processor creates lock-in that prevents the VAR from renegotiating rates or switching processors when better economics become available. Implement tokenization and point-to-point encryption at the hardware level to minimize PCI scope across the entire merchant chain. Maintain rigorous API versioning: VAR-deployed hardware cannot be patched as rapidly as cloud software, and breaking changes strand large hardware fleets in the field. Document integration flows thoroughly, because VARs often operate with tiered technical teams—your SDK or API must be accessible to a regional dealer with limited engineering resources, not just the VAR's core development team.
Common Mistakes
VARs entering or scaling in the payments channel repeatedly encounter the same avoidable errors. Each one carries financial, regulatory, or reputational consequences.
Misclassifying the payment relationship. VARs that earn revenue from processing referrals without formally registering as an ISO or agent with the acquiring bank risk card network violations and potential fines. Registration requirements vary by card network and acquirer, but the obligation is nearly universal for any entity earning payment residuals.
Overlooking residual contract terms. VAR residual agreements with ISOs or processors frequently contain clawback clauses, minimum volume commitments, and exclusivity provisions. A VAR that loses a single large merchant can trigger a clawback that eliminates months of accumulated residuals. Legal review before signing any processing partnership is not optional.
Treating hardware as a one-time sale. VARs that optimize for hardware margin without building recurring software and support revenue struggle to maintain merchant relationships. Merchants who feel unsupported after installation are easy targets for competing VARs offering better service at comparable cost.
Underestimating PCI obligations. Assuming that a certified terminal eliminates all PCI responsibility is a costly mistake. The VAR's configuration practices, remote access procedures, software update processes, and support workflows all fall within scope. A single misconfigured terminal or insecure remote access session can expose an entire merchant cohort to audit risk and potential fines.
Neglecting the merchant acquirer relationship. VARs that resell processing without maintaining a direct relationship with the acquiring bank have limited visibility into underwriting decisions, reserve holds, and chargeback management. This leaves merchants exposed and the VAR unable to advocate effectively when payment issues arise.
Value-Added Reseller (VAR) and Tagada
VARs building or modernizing their payment stack face a persistent challenge: they need multi-processor flexibility, fast merchant onboarding, and unified reporting without rebuilding infrastructure for each new acquirer relationship. A payment gateway alone does not solve this—orchestration does.
Tagada's payment orchestration layer lets VARs connect to multiple acquirers and processors through a single API integration. VARs can route transactions dynamically by cost, geography, card type, or authorization rate—optimizing outcomes for merchants without maintaining separate processor integrations. Combined with Tagada's sub-merchant management and consolidated reporting tools, VARs can scale their installed base while keeping development overhead low and switching costs minimal.
VARs exploring PayFac-lite models can use Tagada's orchestration infrastructure to offer faster merchant onboarding and unified settlement reporting, capturing more of the payment economics without taking on the full regulatory burden of a licensed payment facilitator registration. This is particularly valuable for software-led VARs that want to monetize payment volume at scale while keeping their engineering team focused on the vertical application rather than processor integrations.