Transaction Aggregation: When You Can Batch Charges

A transaction has to represent a single purchase. You can't batch several purchases into one charge to save on fees or tidy up a customer's statement, except in a narrow set of cases with hard limits attached. In the US those limits are USD 15 and 3 days.

That catches more businesses than it sounds like. Anyone selling small digital items, in-app purchases, per-article content or metered usage eventually has the idea of charging once at the end of the week. The rules have an answer, and it's mostly no.

The default rule#

A transaction must represent a single purchase by a cardholder, and a merchant must not aggregate multiple purchases into a single transaction except where the rules permit it (ID# 0002906).

That's the starting position. Aggregation is the exception, not a billing style you can adopt.

Where aggregation is permitted, and the limits#

The permitted cases are listed by region, and the US is stricter than everywhere else.

In the US Region:

• Electronic commerce: maximum USD 15, maximum 3 days between transactions
• Other transit transactions, for example MCCs 4111, 4112 and 4131: maximum USD 15
• Mobility and transport transactions: governed by their own authorization requirements rather than a flat cap

In the AP, Canada, CEMEA, Europe and LAC Regions:

• Electronic commerce: maximum USD 15 or local currency equivalent, maximum 7 days
• Other transit transactions: maximum USD 25 or local currency equivalent

So a European ecommerce merchant gets a full week to accumulate. A US one gets three days. If you run both, the aggregation window isn't a single global setting.

Marketplaces are carved out#

Worth knowing before you conclude your model is banned. The rule doesn't apply to a marketplace transaction, which counts as a single transaction even though it can represent multiple purchases from different retailers occurring at the same time.

The distinction is same time versus over time. A basket spanning several sellers, checked out at once, is one purchase. Accumulating a customer's separate purchases across three days and charging once is aggregation, and it needs to fit the table above.

What you must tell the customer#

If you do aggregate, three disclosures are required at the point of transaction. You must inform the cardholder:

• That transaction aggregation will occur
• The aggregation terms, including the maximum number of calendar days and the transaction value
• How to obtain details of the aggregated purchases

Notice that the limits themselves have to be disclosed, not just the fact of aggregation. "We may combine charges" doesn't meet this. The customer needs the ceiling and the window.

The 120 day record duty#

There's a retention obligation that sits alongside it. A merchant must make individual purchase information and aggregated transaction information available to a cardholder for at least 120 days after the processing date of the aggregated transaction.

Both layers. The breakdown of what was bought, and the detail of the aggregated charge itself, reachable by the customer for four months. If your system collapses the individual line items once the charge settles, that's a problem, and it's also the thing that makes a dispute defensible.

Two extra US requirements#

The US Region adds two conditions that don't appear elsewhere, and both are easy to miss.

You must participate in the Partial Authorization Service. That's the same service that returns an approval for an available balance instead of declining, which I covered alongside Honor All Cards. For aggregation it isn't optional.

For an electronic commerce transaction, you must obtain an authorization of no more than USD 15 at the start of each aggregation session. So the session opens with an authorization, capped at the same USD 15, and that governs the session. It pairs with the reversal obligations if the session closes for less or never completes at all.

Agentic payments cannot aggregate at all#

One more, effective 18 October 2025: an Agentic Payment Provider must not aggregate multiple purchases into a single agentic transaction.

No threshold, no window, no exception table. If you're building anything in the agentic payments space, aggregation is simply off the menu, which is a stricter position than the rules take for ordinary ecommerce.

What this means for your billing design#

• Don't confuse aggregation with recurring billing. A subscription charging monthly for continuing service isn't aggregating purchases. Installments and recurring are separate transaction types with separate rules.
• If you're over USD 15, you're not aggregating, you're breaking the rule. There's no higher tier for bigger merchants.
• Three days in the US, not seven. Copying a European implementation will put you over.
• Keep the line items for 120 days minimum, reachable by the customer, not just in your own database.
• Disclose the ceiling and the window up front, not in a help article the customer finds later.

Source: Visa Core Rules and Visa Product and Service Rules, 18 April 2026.