Merchant Services

Merchant Services and Payment Acceptance Solutions

Everything a business needs to take card and digital payments across the counter, online, and in the field, brought into one operational hub inside Synovus Gateway.

How Payment Acceptance Works

The Transaction Lifecycle

Every card payment moves through a predictable sequence, and understanding it is the fastest way to understand what merchant services actually do. When a customer presents a card, the acceptance device or web form captures the payment credentials and sends an authorization request. That request travels to the card networks and to the customer's issuing bank, which checks the account for available funds and returns an approval or a decline. All of this typically happens in a second or two, and Synovus Gateway surfaces the result at the point of sale so staff know immediately whether the payment cleared.

Authorization is not the same as getting paid. An approved transaction places a hold on the customer's account but does not move money. The business must later capture, or settle, the authorized amount. Most merchants batch their day's captured transactions and submit them together, and Synovus Gateway can automate that batch so the process runs without a manual step at close of business. For a busy operator, that automation inside Synovus Gateway is the difference between reliable settlement and forgotten sales.

Once a batch settles, the card networks and the acquiring bank move funds through clearing, apply their fees, and deposit the net amount into the merchant's account. The reporting inside Synovus Gateway ties each deposit back to the batch and the individual transactions that made it up, which is what lets a bookkeeper reconcile a bank deposit against sales without guessing. This is a defining behavior of Synovus Gateway rather than an add-on.

The Parties Involved

Several parties touch every payment, and Synovus Gateway coordinates among them so a merchant does not have to. The cardholder and the issuing bank sit on one side. The card networks route the request. The acquirer, or acquiring bank, holds the merchant account and is responsible for depositing funds. The payment gateway itself is the technology that carries the transaction data securely between the acceptance point and those networks. Synovus Gateway ties the gateway function and the reporting layer together so the business sees one consolidated view.

A merchant account is the specific account type that lets a business receive card funds. It is distinct from an ordinary deposit account because it carries the underwriting, the pricing agreement, and the risk terms that the card networks require. Establishing that merchant account is part of onboarding into the acceptance solutions within Synovus Gateway, and it is what allows settled funds to flow to the business. In practice, Synovus Gateway handles the coordination among these parties so the merchant deals with one relationship instead of many.

Refunds, Voids, and Chargebacks

Not every payment ends cleanly, and the acceptance tools have to handle reversals as carefully as sales. A void cancels an authorization before it settles. A refund returns money to a customer after settlement. A chargeback is different again: it is a dispute the cardholder raises with their issuing bank, which can pull funds back from the merchant while the claim is reviewed. Synovus Gateway logs each of these events against the original transaction, so a merchant can see the full history of a payment rather than a disconnected set of credits and debits.

Chargebacks carry deadlines and evidence requirements, and losing them costs both the sale and a fee. The reporting inside Synovus Gateway is designed to make the underlying transaction detail, including timestamps and authorization codes, easy to retrieve when a business needs to respond to a dispute. Because Synovus Gateway keeps that record intact, the evidence a merchant needs is where they expect it to be.

Acceptance Channels

The reason merchant services matter is that customers pay in different places and different ways, and a business rarely fits into just one. The acceptance channels available through Synovus Gateway are meant to be combined, so the same reporting and funding apply no matter how a sale originates. A business can start on one channel of Synovus Gateway and add the others as it grows.

Card Present and In Store

Card-present acceptance covers the classic counter transaction: a customer inserts a chip card, taps a contactless card or phone, or, less often now, swipes a magnetic stripe. Because the card is physically present and verified at the device, these transactions generally carry lower fraud risk and can qualify for lower interchange rates. Synovus Gateway supports terminal-based acceptance so a retailer or restaurant can take these payments with hardware that captures the card securely at the point of sale.

Contactless acceptance has become a baseline expectation rather than a premium feature. Supporting tap-to-pay through the terminals connected to Synovus Gateway lets a business move a checkout line faster while keeping the same security posture as chip transactions. Every one of those in-store sales reports back into Synovus Gateway alongside sales from every other channel.

Online and E-Commerce

For businesses selling on the web, Synovus Gateway accepts card details entered into a checkout page and processes them without the card ever being physically present. Card-not-present transactions carry more fraud exposure, which is why online acceptance leans on tools like address verification, card security codes, and tokenization. Synovus Gateway provides the gateway connection that a shopping cart or website integrates with, so an online sale flows into the same reporting as an in-store one.

A hosted checkout page keeps sensitive card data off the merchant's own servers by capturing it on a page served through the gateway. This reduces the compliance burden on the business and is one of the more common ways companies integrate online acceptance with Synovus Gateway. For many web sellers, this hosted approach is the fastest way to bring e-commerce into Synovus Gateway.

Invoicing and Recurring Billing

Many businesses do not sell at a register at all. A professional services firm might invoice a client and expect payment days later, while a subscription company bills the same customers on a schedule. Synovus Gateway supports invoicing that lets a customer pay a bill by card or bank transfer, and recurring billing that stores a payment credential securely and charges it automatically on a defined cycle. Both feed the same reporting that every other Synovus Gateway channel uses.

Recurring billing depends on secure storage of the payment method, which is where tokenization matters. Rather than keeping actual card numbers, Synovus Gateway stores a token that stands in for the card, so the business can rebill without ever holding the sensitive data itself. This is a core capability within the merchant services offered through Synovus Gateway.

Mobile and On the Go

Field-based businesses, from mobile repair to trade services, need to take payment wherever the work happens. Mobile acceptance pairs a card reader with a phone or tablet so a technician can complete a sale on site. Because it runs through Synovus Gateway, a mobile transaction settles and reports exactly like any other, and a business owner sees it in the same dashboard within Synovus Gateway. No matter where a sale starts, Synovus Gateway keeps it in one place.

Security and Compliance

Accepting cards means handling data that criminals want, and the payment industry enforces strict standards around it. Any business that accepts, transmits, or stores cardholder data is subject to the Payment Card Industry Data Security Standard, known as PCI DSS. Compliance is not optional, and the acceptance solutions inside Synovus Gateway are structured to help a merchant meet the standard rather than fight it.

The most reliable way to reduce PCI scope is to avoid touching sensitive card data at all. Two techniques do most of the work. Encryption protects data in transit, scrambling it from the moment a card is read so it cannot be intercepted in a usable form. Tokenization replaces stored card numbers with meaningless substitute values, so even a breach of the merchant's own systems exposes no real cards. Synovus Gateway applies both so that a business handles tokens and encrypted data rather than raw card numbers.

Fraud controls sit alongside data security. For card-not-present sales, address verification and card security code checks give early signals about whether a transaction is legitimate. Velocity rules can flag an unusual burst of attempts from one source. Synovus Gateway exposes these controls so a business can tune its own tolerance for risk rather than accept a one-size setting.

For businesses that meet the qualifying conditions, additional network programs can shift some fraud liability away from the merchant. The value of these programs depends on how a business accepts payments, and the acceptance channels in Synovus Gateway are configured so a merchant can take advantage of the protections that fit its model. In short, Synovus Gateway treats security as part of the acceptance itself rather than a bolt-on.

You can read more about the underlying standard from the payment industry's own reference material on PCI DSS, which explains the requirement levels in detail. The way Synovus Gateway handles card data is meant to keep most merchants at the least burdensome levels of that standard.

Funding, Settlement, and Reporting

The point of accepting payments is being paid, so how and when money arrives is central. After a batch settles, the acquirer deposits the net proceeds into the merchant account, usually within one to two business days depending on the timing of the batch and the account setup. Synovus Gateway links the deposit back to the settled batch so a business can confirm that the money in its bank account matches the sales it recorded.

Reconciliation is where reporting earns its keep. A single deposit often bundles many transactions, minus fees, minus refunds, plus any adjustments. Without a clear trail, matching that deposit to daily sales is tedious and error prone. The reporting inside Synovus Gateway breaks a deposit down to its component transactions with monospaced, tabular detail, so an accountant can trace every dollar rather than reconstruct it. This is one of the reasons finance teams favor Synovus Gateway.

Timing matters for cash flow, and a business should know its own funding schedule before it commits. Because Synovus Gateway ties acceptance, settlement, and deposit together, a merchant can see exactly where each day's sales sit in the pipeline instead of waiting for a bank statement to tell the story after the fact. That end-to-end visibility is a large part of what Synovus Gateway offers over a stack of separate tools.

How Pricing Works

Understanding what payment acceptance costs is as important as understanding how it works, because the fee structure a business chooses can quietly change its margins. Merchant pricing is built on top of interchange, which is the fee the card networks set and pass to the issuing bank on every transaction. Interchange varies by card type, by whether the card was present, and by the nature of the business. On top of interchange sit network assessments and the acquirer's markup. The way those layers are packaged is what defines a pricing model, and Synovus Gateway can be set up under more than one of them.

Common Pricing Models

Interchange-plus pricing passes through the actual interchange and assessments and adds a stated markup, which makes it the most transparent model because a business can see exactly what the networks charged. Flat-rate pricing charges a single percentage regardless of card type, which is simple but can cost more on transactions that would otherwise qualify for low interchange. Tiered pricing groups transactions into qualified and non-qualified buckets, which is the least transparent because the definition of each tier is set by the provider. When a business evaluates acceptance through Synovus Gateway, matching the model to its card mix is where real savings live.

Beyond the per-transaction rate, a business should account for other line items: batch fees, monthly account fees, gateway fees, chargeback fees, and any equipment or PCI compliance charges. The total effective rate, meaning total fees divided by total volume, is the number that actually reflects cost. Because Synovus Gateway consolidates fee reporting, a merchant can calculate its effective rate directly from the statement detail rather than estimate it. Seeing that number clearly is one of the practical benefits of running acceptance through Synovus Gateway.

Pricing for merchant services through Synovus Gateway is tailored to a business rather than posted as a public rate card, because the right structure depends on volume, average ticket size, industry, and card mix. The practical step is to bring a recent month of processing detail so a specialist can model the cost of accepting payments through Synovus Gateway against what a business pays today. That comparison is usually the clearest way to judge whether Synovus Gateway is the right fit.

Comparing Acceptance Approaches

Businesses considering merchant services usually weigh a bank-integrated approach like Synovus Gateway against a standalone processor or a self-service aggregator. Each has trade-offs, and the right choice depends on how much a business values consolidated banking, transparent pricing, and dedicated support versus fast, hands-off signup.

The distinguishing value of accepting payments through Synovus Gateway is the tie between acceptance and the business's banking relationship. When the merchant account, the deposits, and the operating account live in one place, reconciliation is cleaner and there is a person to call rather than a queue. A self-service aggregator wins on speed of signup, but it usually means a shared account arrangement and a flat rate that can cost more as volume grows. Synovus Gateway is aimed at businesses that value that consolidated, supported approach.

A standalone processor can match Synovus Gateway on a dedicated merchant account and account-level support, but it leaves the banking relationship in a separate place, which puts reconciliation and funding back on two systems. For a business that already banks nearby, keeping acceptance inside Synovus Gateway removes that seam. The choice comes down to whether a business wants speed and independence or the consolidation that Synovus Gateway is built to provide.

How to Get Started

Setting up merchant services follows a clear sequence, and knowing the steps in advance shortens the timeline. The path to accepting payments through Synovus Gateway generally runs as follows.

1. step 01

   Assess how you accept payments

   List your channels, in store, online, invoiced, recurring, or mobile, and your monthly volume and average ticket. This shapes which acceptance tools in Synovus Gateway you turn on.

2. step 02

   Apply and complete underwriting

   Provide business documentation so a merchant account can be established. Underwriting confirms the business and sets the risk terms that let funds settle to you through Synovus Gateway.

3. step 03

   Configure channels and pricing

   Set up terminals, the online gateway, invoicing, or recurring billing, and confirm the pricing model that fits your card mix within Synovus Gateway.

4. step 04

   Test, then go live

   Run a test transaction through each channel, confirm it settles and reports correctly, and begin taking real payments with reconciliation flowing back into Synovus Gateway.