A payment aggregator collects money from many customers and moves it to a merchant's bank account in a single batch
A payment aggregator is a company that sits between customers and merchants. When you buy something online and enter your card details, the aggregator receives that transaction, holds the money temporarily, and then deposits it into the merchant's bank account—usually once a day or once a week, depending on the agreement.
The aggregator does not own the money while it holds it. That money belongs to you until the transaction settles, and it belongs to the merchant once it does. The aggregator is a middleman whose job is to collect, verify, and move payments reliably. They handle the technical work of connecting to card networks, managing fraud checks, and making sure the right amount lands in the right account.
Payment aggregators are common in e-commerce, subscription services, and marketplaces. If you have ever bought from a small online store that uses Stripe, Square, or PayPal, you have used a payment aggregator. The merchant does not need their own direct connection to Visa or Mastercard—the aggregator provides that connection for them.
Key Takeaways
- A payment aggregator collects transactions from customers, verifies them, and deposits the money into the merchant's bank account in batches rather than one at a time.
- The aggregator holds the money only briefly—it does not own or use customer funds—and passes it through to the merchant after deducting their fee.
- Merchants use aggregators because they avoid the cost and complexity of setting up their own direct connections to card networks like Visa and Mastercard.
- Payment aggregators are responsible for fraud detection, chargebacks, and compliance with payment card industry rules, which is why they charge a percentage of each transaction.
How money moves through a payment aggregator
When you enter your card information at checkout, the aggregator's system sends that data to the card network (Visa, Mastercard, American Express, or Discover). The network checks with your bank to confirm the funds are there. If the check passes, your bank temporarily holds that amount.
The aggregator receives confirmation that the transaction is authorized. At this point, the money is not in the merchant's account yet—it is still with your bank. The aggregator records the transaction and adds it to a batch of other transactions from that merchant.
Once a day or once a week, the aggregator sends all of that merchant's transactions to their bank in one file. The merchant's bank receives the batch, and the money moves from your bank to the merchant's bank. This is called settlement. The aggregator deducts their fee (usually 2 to 3 percent of the transaction total) and passes the rest to the merchant.
The entire process from your card swipe to the merchant's deposit typically takes one to three business days, depending on when the batch is sent and how fast the banks process it.
Why merchants choose aggregators instead of direct connections
Setting up a direct connection to Visa and Mastercard requires a merchant account with a bank or payment processor. That account comes with setup fees, monthly minimums, and strict underwriting—the bank wants to know your business model, your expected volume, and your history. Small merchants often cannot meet those requirements, or the costs are too high relative to their sales.
A payment aggregator removes that barrier. The aggregator already has the merchant account and the direct connection to the card networks. They let many small merchants use that single account, which spreads the cost across thousands of businesses. A new online store can start accepting cards within hours instead of weeks.
The trade-off is that the aggregator charges a higher percentage per transaction than a merchant would pay with their own account. But for a small business, paying 2.9 percent per transaction is cheaper than paying monthly fees, setup costs, and the time spent on underwriting.
The difference between aggregators and payment processors
The terms are often used interchangeably, but they are not quite the same. A payment processor is a broader category that includes any company handling payments. An aggregator is a specific type of processor that pools many merchants under one merchant account.
A payment processor might also be a payment gateway—the software that encrypts your card data and sends it to the card network. Some processors do both: they provide the gateway (the software) and the aggregation (the pooling of merchants). Stripe, for example, is both a gateway and an aggregator.
The key distinction is pooling. If a merchant has their own merchant account and their own connection to the card networks, they are not using an aggregator—they are using a processor or gateway directly. If they are sharing a merchant account with thousands of other small businesses, they are using an aggregator.
Fraud detection and chargebacks in aggregator systems
Because an aggregator handles thousands of merchants and millions of transactions, they invest heavily in fraud detection. They use machine learning to spot patterns—unusual card numbers, mismatched addresses, transactions from countries where the merchant does not ship, velocity checks (too many transactions in too short a time).
If a customer disputes a charge and files a chargeback with their bank, the aggregator is responsible for responding. They gather evidence from the merchant (shipping confirmation, customer communication, delivery proof) and submit it to the card network. If the chargeback is upheld, the aggregator deducts the amount from the merchant's next deposit and may charge a chargeback fee on top.
This is why aggregators require merchants to keep good records. A merchant who cannot prove they shipped an item or that the customer authorized the charge will lose the chargeback dispute, and the aggregator will hold them responsible for the loss.
Compliance and regulatory requirements aggregators must meet
Payment aggregators must comply with PCI DSS (Payment Card Industry Data Security Standard), a set of rules designed to protect card data. They cannot store full card numbers after a transaction is complete. They must encrypt data in transit. They must audit their systems regularly and report breaches to the card networks.
Aggregators are also regulated by the Financial Crimes Enforcement Network (FinCEN) under anti-money-laundering rules. They must verify the identity of merchants, monitor for suspicious activity, and report large or unusual transactions. This is why opening a merchant account with an aggregator requires providing a business license, tax ID, and bank account information.
These compliance costs are built into the fees aggregators charge. A merchant paying 2.9 percent is partly paying for the aggregator's fraud detection, chargeback handling, and regulatory compliance work.
When an aggregator model does not work
High-volume merchants often outgrow aggregators. Once a business is processing hundreds of thousands of dollars per month, the percentage fee becomes expensive. At that point, it makes sense to explore for their own merchant account and negotiate a lower flat rate or per-transaction fee with a processor.
Some business types are also restricted or prohibited by aggregators. Gambling, adult content, cryptocurrency exchanges, and high-risk categories like travel or financial services often cannot use standard aggregators because the fraud and chargeback rates are too high. These merchants need specialized processors that accept the risk in exchange for higher fees.
Aggregators also reserve the right to refuse service. If a merchant has too many chargebacks, processes suspicious transactions, or violates the aggregator's terms, the aggregator can close the account. This is a real risk for merchants—losing access to payments can shut down a business overnight.
Frequently Asked Questions
Is my money safe with a payment aggregator?
Your money is not held by the aggregator for long—it moves from your bank to the merchant's bank within one to three business days. The aggregator is required by law to keep customer funds separate from their own operating money. If the aggregator fails, your funds are protected because they are not the aggregator's assets.
Why does it take a few days for money to show up in a merchant's account?
The aggregator batches transactions and sends them to the merchant's bank once a day or once a week. Your bank and the merchant's bank then process the transfer, which takes one to two more business days. Weekends and holidays add delays. Some aggregators offer faster settlement for an extra fee.
Can a payment aggregator see my card number?
No. The aggregator's system receives encrypted card data, processes it, and then deletes the full number. They keep only the last four digits for record-keeping. PCI compliance rules forbid them from storing the full number after the transaction is complete.
What happens if a merchant goes out of business while holding my refund?
If you are owed a refund and the merchant closes, the aggregator is not responsible for paying it. You would need to dispute the charge with your bank as a chargeback. Your bank may recover the money from the merchant's account if it is still open, but if the account is closed, recovery depends on whether the merchant has other assets.
Do all online stores use payment aggregators?
No. Large retailers like Amazon and Walmart have their own merchant accounts and process payments directly. Small to medium businesses typically use aggregators because the setup is faster and cheaper. Some use both—an aggregator for their website and a direct processor for in-store payments.