Merchant services can do much more for a bank than add another line to its business product menu. When payments, deposits, reporting, and cash management work together, merchant services can become part of a much broader commercial banking relationship.
The challenge is deciding how to build the program.
A community bank may want to offer card acceptance without assuming the technology and compliance burden of becoming an acquirer. A larger institution may want more control over pricing, branding, underwriting, and the merchant experience. Others fall somewhere between those two positions.
There is no single merchant services model that works for every financial institution. Banks need to weigh control, cost, risk, technology requirements, merchant expectations, and long-term strategy before deciding how deeply they want to participate in payment processing.
Key Takeaways
- Banks generally approach merchant services through referral relationships, white-label partnerships, or more deeply controlled acquiring models.
- The right structure depends on the bank’s resources, risk appetite, technology environment, commercial strategy, and desired level of control.
- Merchant pricing should be evaluated by model, including flat-rate, interchange-plus, and tiered pricing, rather than assuming that one type of provider always uses a particular structure.
- Integration with business checking, treasury management, lending, reporting, and other banking services can create a more connected experience for commercial customers.
- Risk management, merchant onboarding, technical support, payment security, reporting, and pricing transparency should all be evaluated before a bank launches or expands a program.
Why Do Merchant Services Matter to Banks?
Businesses increasingly expect their financial partners to help them manage more than deposits and loans. Payment acceptance is a daily operational need for retailers, restaurants, professional services firms, contractors, healthcare practices, online sellers, and countless other businesses.
That gives banks an opportunity to participate in one of the most frequent financial activities their commercial customers perform.
When payment processing connects directly with a business checking account, the merchant can receive settlement funds within the same financial relationship used for payroll, vendor payments, financing, and cash management. Instead of treating payments as a separate system, the business gains a more connected view of its money.
For banks, merchant services can also generate fee income and create additional opportunities to support customers with treasury management, commercial lending, fraud controls, and other financial products.
The strategic question is not simply whether a bank should offer merchant services. It is how much of the merchant relationship the bank wants to own.
What Is a Bank Merchant Services Program?
A merchant services program gives business customers the tools they need to accept and manage electronic payments.
Depending on the program, that can include in-person card acceptance, online payments, mobile payments, virtual terminals, payment gateways, settlement reporting, chargeback management, fraud controls, recurring billing, and point-of-sale technology.
Several organizations may participate in a single transaction.
The processor handles transaction routing and processing. Card networks provide the infrastructure and operating rules connecting the parties involved in the transaction. The issuing bank represents the cardholder, while the acquiring side supports the merchant accepting the payment.
Payment gateways provide an important technology layer for online and other card-not-present transactions. They securely transmit transaction information between the merchant’s checkout environment and the processing infrastructure.
Banks do not necessarily have to provide every part of this ecosystem themselves. That is why choosing the right merchant services program model is so important.
What Are the Main Merchant Services Program Models for Banks?
Banks typically have three broad strategic options: referral programs, white-label partnerships, and more comprehensive in-house acquiring models.
The differences are largely about control.
Referral Programs
A referral model offers one of the simplest ways for a bank to enter merchant services.
The bank introduces business customers to a merchant services provider, while the provider handles much of the underwriting, processing, technology, servicing, and payment infrastructure.
This structure can work well for banks that want to offer payment acceptance without making a significant technology investment.
The tradeoff is control. The merchant may interact primarily with the third-party provider after the referral, and the bank may have limited influence over pricing, servicing, technology, and the overall customer experience.
White-Label Merchant Services
A white-label relationship moves the bank closer to the center of the experience.
The underlying processing and technology may still come from an outside provider, but the merchant-facing program can operate under the bank’s brand. Depending on the agreement, the bank may have greater influence over pricing, onboarding, product configuration, reporting, and customer support.
This approach can provide a middle ground for institutions that want more control without building an acquiring platform from the ground up.
The exact division of responsibilities varies considerably by provider and contract, so banks need to understand which party handles underwriting, PCI responsibilities, fraud monitoring, technical support, chargebacks, merchant servicing, and other operational functions.
In-House Acquiring
Banks seeking the greatest degree of control can take on more of the acquiring function internally.
This can give the institution greater control over merchant underwriting, pricing, risk policies, technology decisions, customer relationships, and product development.
It also comes with substantially greater operational demands.
An institution taking on these responsibilities needs appropriate payment infrastructure, experienced personnel, regulatory oversight, fraud controls, security processes, merchant risk management, and ongoing operational support.
For that reason, a deeply controlled acquiring model tends to make the most sense when processing volume and strategic value justify the additional investment.
How Do the Merchant Services Models Compare?
| Consideration | Referral Program | White-Label Partnership | In-House / Bank-Controlled Acquiring |
| Initial investment | Lower | Moderate | Highest |
| Speed to market | Generally fastest | Moderate | Generally longest |
| Brand control | Limited | High | Very high |
| Pricing control | Limited to moderate | Greater flexibility | Extensive control |
| Technology responsibility | Primarily provider | Shared | Primarily bank |
| Merchant risk exposure | Typically lower | Depends on agreement | Higher |
| Compliance workload | Primarily oversight | Shared responsibilities | Significant internal responsibility |
| Customer relationship | Shared with provider | More bank-centered | Bank-controlled |
| Best suited for | Institutions seeking a simpler entry point | Banks wanting stronger branding and control | Institutions with substantial payments expertise and infrastructure |
Banks should treat this table as a strategic starting point rather than a rigid formula. Two providers offering the same general program model may divide responsibilities very differently.
The underlying contract matters just as much as the label attached to the program.
How Should a Bank Choose a Merchant Services Model?
The decision should begin with the bank’s broader commercial strategy.
A bank that primarily wants to keep payment acceptance within the broader commercial relationship may be comfortable with a referral relationship.
An institution that views payments as an important part of its commercial banking experience may prefer a white-label program that gives relationship managers greater visibility and keeps the bank’s brand in front of the customer.
Banks considering deeper control should examine whether processing revenue and merchant volume justify the technology, staffing, compliance, and operational investment required.
Risk tolerance is another major factor. Merchant acquiring involves exposure to chargebacks, fraud, business failures, refund activity, and other payment risks. The more responsibility the bank assumes, the stronger its risk infrastructure must be.
What Should a Merchant Services Product Set Include?
The right product mix depends on the businesses the bank serves.
- A neighborhood restaurant does not have the same payment needs as an accounting firm, e-commerce retailer, plumbing company, or medical practice.
- An in-person merchant may need EMV and contactless terminals, receipt printing, tip functionality, inventory tools, and integrated point-of-sale software.
- A field-service business may care more about mobile readers, invoicing, payment links, and the ability to accept payments at a customer’s location.
- Professional services firms may need recurring billing, virtual terminals, saved payment credentials, and invoice management.
- E-commerce merchants need payment gateways, checkout integrations, tokenization, fraud screening, digital wallet compatibility, and reliable card-not-present processing.
Instead of building one generic package, banks can evaluate merchant segments and design options around the workflows customers actually use.
How Should Banks Approach Merchant Services Pricing?
Pricing deserves particular attention because businesses often struggle to understand what they are actually paying for payment processing.
Banks and merchant services providers may offer several different pricing structures. The three common approaches are flat-rate pricing, interchange-plus pricing, and tiered pricing.
No single model belongs exclusively to banks, fintech companies, or independent processors. Different organizations may offer one or several of these options.
Merchant Services Pricing Models
| Pricing Model | How It Works | Potential Advantages | Potential Considerations |
| Flat-rate pricing | Merchant pays a consistent percentage and sometimes a fixed amount per transaction | Simple to understand and forecast | May cost more for some merchants depending on transaction mix |
| Interchange-plus | Merchant pays underlying interchange and network costs plus an agreed processor markup | Provides greater visibility into processing costs | Statements may be more complex |
| Tiered pricing | Transactions are grouped into pricing categories such as qualified and non-qualified | Can appear simple at a high level | Tier classifications can make true processing costs harder to evaluate |
Pricing should also be evaluated beyond the headline transaction rate.
A merchant may encounter gateway charges, monthly service fees, PCI-related fees, chargeback fees, hardware costs, minimum processing requirements, or other expenses depending on the provider and agreement.
Transparency matters.
Banks that make pricing easier to understand can help customers evaluate their total payment cost rather than forcing them to decipher a long statement filled with unfamiliar fee categories.
Higher-volume merchants may also require customized pricing. Transaction mix, card type, sales channel, average ticket size, chargeback exposure, and overall processing volume can all influence the economics of an account.
What Role Do Risk, Compliance and Underwriting Play?
Merchant services introduce risks that are different from those associated with a traditional deposit account.
Banks and their merchant services partners need a clear process for evaluating the businesses they onboard.
That includes verifying the business and its ownership, understanding expected transaction volume, reviewing average ticket size, evaluating industry risk, identifying card-not-present exposure, and assessing potential fraud and chargeback activity.
Higher-risk industries may require additional underwriting, reserves, monitoring, or other controls.
Risk management does not stop after onboarding.
Transaction patterns can change. A merchant may suddenly process substantially more volume than expected, experience an unusual increase in refunds, receive more chargebacks, or begin processing transactions in ways that differ from its original business model.
Ongoing monitoring helps the bank or provider identify those changes before they become larger problems.
Payment security is equally important.
PCI DSS requirements, tokenization, encryption, point-to-point encryption where applicable, secure payment pages, access controls, and fraud-monitoring tools all play a role in protecting payment information.
When responsibilities are outsourced, banks still need to understand what their partners provide and what oversight obligations remain with the institution.
How Can Merchant Services Integrate With Other Banking Products?
This is where merchant services can become more valuable than a standalone card-processing product.
A business may receive card settlements into the same checking account it uses to pay employees and vendors. Treasury tools can help the customer manage liquidity. Lending products can address working capital needs. Reporting can provide a clearer picture of inflows and outflows.
Payment data can also contribute to a richer understanding of the customer’s business activity when the appropriate systems and permissions are in place.
Useful integration points can include unified transaction reporting, reconciliation tools, settlement visibility, treasury management dashboards, and connections to accounting or enterprise systems.
These integrations can deepen the primary banking relationship by giving businesses a more connected view of payments, deposits, lending, and cash management.
The goal should not simply be to make it difficult for a customer to leave. The stronger proposition is to make the relationship useful enough that the customer has good reasons to stay.
What Should Banks Look for in Merchant Onboarding and Support?
A strong merchant services strategy can be undermined by a poor onboarding experience.
Business owners generally want to start accepting payments quickly, but speed should not come at the expense of appropriate underwriting and risk controls.
Banks should look at the full onboarding process from the merchant’s perspective.
How easy is the application to complete? Can information already held by the bank reduce duplicate data entry? How quickly are routine applications reviewed? How are equipment, gateways, and user credentials delivered? Who helps the merchant when something goes wrong?
Technical support deserves close scrutiny during provider selection.
Banks should evaluate support hours, escalation procedures, device troubleshooting, gateway assistance, response expectations, and access to knowledgeable support resources.
The right level of coverage will depend on the merchant base.
A bank serving restaurants and e-commerce businesses may need broader support availability than an institution serving primarily professional-service firms operating during traditional business hours.
What Metrics Should Banks Use to Measure Program Performance?
Processed volume and revenue matter, but they do not tell the entire story.
Banks should evaluate merchant services as both a payment product and part of the broader commercial relationship.
Useful measures include active merchant accounts, processing volume, net fee income, merchant attrition, chargeback activity, adoption among existing business customers, support trends, and the number of merchants using additional banking services.
Banks can also examine how quickly new accounts become active, how many merchants abandon onboarding, which product bundles generate the most adoption, and whether customers are successfully moving between in-person, mobile, and online payment channels.
A dashboard combining financial, operational, risk, and customer metrics can provide a more complete picture than revenue alone.
What Trends Are Changing Bank Merchant Services?
Payments continue to move toward faster settlement, greater integration, and more flexible acceptance options.
Businesses increasingly expect to manage in-person, online, mobile, recurring, and account-to-account payments through connected systems rather than separate platforms.
Real-time payment infrastructure also creates new possibilities for moving money and managing liquidity.
Embedded payments are another important development. Industry software platforms increasingly incorporate payments directly into the applications businesses already use to schedule appointments, manage restaurants, run field-service operations, or sell products online.
For banks, that creates both competition and partnership opportunities.
Institutions evaluating merchant services platforms should consider API capabilities, integration flexibility, reporting, data portability, security, and the provider’s ability to support new payment methods without requiring a complete technology replacement.
How PayTech Trust Helps Financial Institutions Evaluate Merchant Services
Building or improving a merchant services program requires more than selecting a processor.
PayTech Trust helps financial institutions evaluate payment acceptance and merchant-services strategies, workflows, integrations, reporting, pricing transparency, support requirements, and other operational considerations that affect both the bank and its business customers.
That evaluation can help institutions determine where greater control adds value, where third-party expertise may be more efficient, and how merchant services fit into the broader commercial banking relationship.
Available capabilities depend on the selected processor, gateway, banking systems, contractual structure, and implementation scope. Learn more about how PayTech Trust works with financial institutions to support payment processing programs, integrations, reporting, and ongoing service.
Building a Merchant Services Program That Fits the Bank
The best merchant services strategy is not automatically the one that gives a bank the most control.
It is the one that fits the institution.
For some banks, that may mean a straightforward referral relationship that allows them to offer payment acceptance without building extensive internal infrastructure. Others may benefit from a white-label program that places the bank’s brand and relationship managers closer to the merchant experience. Institutions with significant volume, payments expertise, and technology resources may pursue much deeper control.
The important part is making that decision deliberately.
Banks should evaluate pricing, customer experience, risk allocation, payment security, integrations, reporting, support, technology requirements, and long-term scalability before choosing a structure.
A well-designed merchant services program for banks can become more than a way for customers to accept card payments. It can connect payments with the broader financial relationship and give business customers a simpler way to manage how money enters, moves through, and supports their operations.
Frequently Asked Questions
What is a merchant services program for a bank?
A merchant services program allows a bank’s business customers to accept and manage electronic payments. Depending on the program, services may include card processing, point-of-sale systems, payment gateways, mobile acceptance, virtual terminals, settlement reporting, fraud controls, recurring billing, and chargeback management.
Does a bank have to process merchant transactions itself?
No. Banks can refer customers to third-party processors, use white-label partnerships, or assume more direct responsibility for acquiring and processing. The appropriate structure depends on the bank’s strategy, resources, risk appetite, and desired control over the merchant relationship.
What is the difference between a referral and white-label merchant services program?
In a referral program, the third-party provider typically owns more of the merchant experience after the introduction. In a white-label program, the underlying provider may still operate the processing technology, but the program can be presented more closely under the bank’s brand. Exact responsibilities vary by agreement.
Which merchant services pricing model is best?
There is no single pricing model that is best for every merchant. Flat-rate pricing offers simplicity, interchange-plus provides greater visibility into underlying processing costs, and tiered pricing groups transactions into rate categories. Transaction volume, card mix, sales channels, average ticket size, and other factors affect which approach may be appropriate.
How should banks address merchant concerns about hidden fees?
Banks can make pricing easier to evaluate by clearly explaining processor markup, interchange and network costs where applicable, monthly fees, gateway charges, hardware expenses, PCI-related fees, chargeback fees, and other potential costs. Providing merchants with a clear picture of total payment cost can reduce surprises.
What role does a business checking account play in merchant services?
Merchant settlement funds can be deposited into the business’s checking account, giving the customer a more connected view of incoming payments and other banking activity. When payments, deposits, lending, and treasury services work together, businesses may also gain simpler reconciliation and cash-flow management.
Can community banks offer competitive merchant services?
Yes. A community or regional bank does not have to build its own processing infrastructure to offer merchant services. Referral and white-label relationships can allow smaller institutions to combine third-party payment technology with the bank’s existing business relationships, local service, lending capabilities, treasury products, and deposit accounts.
