A VAR sheet, short for Value Added Reseller sheet, is a configuration document used to connect a merchant account with a payment gateway or point of sale system. It contains the technical and account details that allow transactions to be authenticated, routed, settled, and reported correctly.
Without a VAR sheet, a merchant may technically have an approved merchant account and a live gateway, but the two will not be able to communicate properly. This often leads to failed transactions, settlement issues, or data mismatches that slow down onboarding and revenue.
At Corepay, VAR sheets are part of nearly every direct merchant account deployment, especially for businesses using independent gateways or specialized integrations like high risk ecommerce, telemedicine, or multi-mid setups.
This guide walks through what a VAR sheet is, when you need one, what it includes, and how Corepay helps merchants handle this without friction.
What Is a VAR Sheet?
A VAR sheet is a structured file or document that contains all the processing parameters a payment gateway or terminal needs to communicate with a merchant account.
Think of it as the translator between your gateway and your acquiring bank.
It tells your system things like:
- Where transactions should be routed
- Which merchant account should receive funds
- What security and encryption rules apply
- How settlement and batching should work
VAR sheets are most common for:
- Merchants using a separate gateway and processor
- Merchants onboarding with a direct processor
- Enterprise or multi-location businesses
- High risk merchants with specific routing or compliance needs
If you are using an all in one aggregator like Stripe or PayPal, you usually do not receive a VAR sheet because those platforms control both the gateway and the processing.
But if you want true control, better approval stability, and long term scalability, a standalone setup with a VAR sheet is often required.
What Information Is Included in a VAR Sheet?
A VAR sheet includes the core configuration details that allow your payments system to function. The exact formatting can vary depending on the gateway and processor, but the core data points are consistent.
Here is the most common information you will find on a VAR sheet.
| Field | Description |
|---|---|
| Merchant ID (MID) | The unique identifier for your merchant account |
| Terminal ID (TID) | Identifies your payment terminal or virtual terminal |
| Acquiring Bank | The bank that sponsors and settles your transactions |
| Processor Name | The back end processing platform |
| Gateway Information | The gateway or bridge connecting to your processor |
| MCC Code | Your merchant category code |
| Currency Code | The currency you will settle in |
| AVS and CVV Settings | Fraud prevention and verification rules |
| Batch Cutoff Time | When daily transactions are settled |
| Settlement Parameters | How and when funds are deposited |
| Encryption Specs | Tokenization and security format settings |
| Descriptor Settings | What appears on customer statements |
| 3DS and SCA Rules | If applicable, for authentication and compliance |
For high risk merchants, the VAR sheet may also include:
- Multi MID routing rules
- Whitelisted IP address ranges
- Redundancy and fallback logic
- Chargeback monitoring integration references
At Corepay, this is especially important for industries like telemedicine, nutraceuticals, GLP-1 providers, and digital services where compliance and transaction routing must be extremely precise.
What Is a VAR Sheet Used For?
A VAR sheet acts as the backbone of your payment system setup.
It ensures that:
- Your gateway sends transactions to the correct processor.
- Your processor knows exactly which account they belong to.
- Your transactions follow the correct security, settlement, and reporting rules.
- Your funds reach the correct bank account.
Without this configuration, you may experience:
- Declined transactions with no clear reason
- Transactions going to the wrong processor
- Settlement delays or misdirected deposits
- Incorrect statement descriptors
- Increased risk flags due to misconfigured data
A properly configured VAR sheet reduces onboarding risk and helps avoid costly technical errors that can hurt approval rates and revenue flow.
Do You Need a VAR Sheet?
Not every business needs a VAR sheet, but many do.
You will need a VAR sheet if:
- You use a standalone payment gateway
- You have a direct merchant account
- You are using custom or enterprise integrations
- Your business operates in a regulated or high risk industry
- You process across multiple brands or websites
- You require multi MID or multi acquirer setups
You typically do not need a VAR sheet if:
- You use Stripe, Square, or PayPal in their pure aggregator form
- You use a closed ecosystem like Shopify Payments
- You do not control your own merchant account
However, many businesses eventually outgrow aggregator systems. When chargebacks, freezes, or account risk increase, moving to a direct setup with a VAR sheet becomes a long term stability strategy.
VAR Sheet vs. Aggregator Setup
Many businesses start with aggregators because they are fast and simple. But there are key differences.
Aggregator Model
- The platform owns the merchant account
- You are a sub-merchant
- Limited configuration control
- Higher risk of sudden account freezes
- Limited custom routing options
VAR Sheet Model
- You own your merchant account
- Full control over processing
- Custom fraud rules and routing
- Multi acquirer redundancy possible
- Built for scale and longevity
For high risk businesses, the VAR sheet model is often the only sustainable path, especially as card networks tighten rules through programs like VAMP and BRAM.
How to Get a VAR Sheet
A VAR sheet is usually issued by your processor or acquiring bank once your merchant account is approved.
Here is how the process typically works.
- You complete merchant underwriting and approval.
- Your processor generates the VAR sheet based on your account.
- The VAR sheet is delivered to your gateway provider or integration team.
- Your system is configured and tested.
- You run test transactions to verify everything is working.
Once live, your VAR sheet may be updated if you:
- Add new MIDs
- Add new currencies
- Change descriptor information
- Integrate new gateways
- Add risk or fraud tools
- Expand into new regions
At Corepay, we handle this entire process for our merchants to avoid errors, delays, and integration headaches.
Common VAR Sheet Mistakes That Cause Problems
A VAR sheet is only as good as the data inside it. Some of the most common issues we fix for merchants are:
- Incorrect MCC codes leading to compliance problems
- Mismatched MID or TID values causing failed routing
- Improper settlement cutoff times creating deposit confusion
- Misconfigured descriptors increasing chargeback risk
- IP whitelisting issues blocking gateway connections
- Wrong currency or region codes for cross border merchants
These mistakes can slow down go live timelines and sometimes trigger risk flags with acquirers.
That is why Corepay assigns a technical onboarding specialist to every direct merchant account so VAR sheets are built and deployed correctly the first time.
Why VAR Sheets Matter More for High Risk Merchants
For low risk retail or card present environments, VAR sheets are often simpler.
For high risk industries, they are critical.
Industries where VAR sheets are especially important include:
- Telemedicine and online healthcare
- Nutraceutical and supplement sales
- GLP-1 and peptide providers
- Digital services and subscription billing
- International ecommerce brands
- CBD and regulated products
These businesses often require:
- Multiple MIDs across regions
- Advanced fraud filtering rules
- Routing across multiple acquirers
- Backup processing logic
- Integration with compliance systems
Without a properly structured VAR sheet, even an approved merchant account can fail to perform effectively.
How Corepay Helps With VAR Sheets
At Corepay, we do not just hand you a VAR sheet and leave you to figure it out.
We manage the full process.
That includes:
- Coordinating with acquiring banks
- Building VAR sheets tailored to your business model
- Working with your gateway provider or dev team
- Setting up multi MID routing if needed
- Configuring fraud and chargeback tools
- Testing transactions before launch
- Monitoring performance after deployment
For merchants using Corepay’s Netvalve gateway or third party platforms, we ensure your VAR configuration supports both approval performance and long term risk management.
This is especially important in a post VAMP and post BRAM environment where processing mistakes lead to higher monitoring risk.
VAR Sheet Checklist for Merchants
Here is a simple checklist you can use when reviewing a VAR sheet.
- Does the MID match your approved merchant account?
- Is the MCC code correct for your industry?
- Do descriptor settings match your website and brand?
- Are AVS and CVV rules configured correctly?
- Is the currency correct for your settlement region?
- Are gateway and processor details accurate?
- Is your batch cutoff aligned with your business model?
- Have redundancy and fallback options been set if needed?
If you are unsure about any of these, Corepay can review and validate your VAR sheet before you launch.
Final Thoughts
A VAR sheet might seem like a small technical document, but it is one of the most important pieces of a scalable payment system.
It is the bridge between your technology and your money flow.
If built properly, it helps:
- Increase authorization rates
- Reduce processing errors
- Improve stability
- Support long term growth
If built incorrectly, it can slow down your entire operation and expose you to unnecessary risk.
If you are setting up a new merchant account or migrating away from an aggregator, Corepay can guide you through every step, from underwriting to VAR configuration to live processing.
