Payment aggregator

An entity that aggregates payments from multiple merchants under one master merchant account.

Definition

Payment aggregator is an entity that pools transactions from many merchants under one master account with card networks. Stripe, PayPal, Square are aggregators (despite Stripe being technically a payment facilitator).

Context

Aggregators simplify merchant onboarding; underlying merchants do not need their own merchant accounts with banks.

Example

A Delaware LLC accepts cards via Stripe (an aggregator) without applying for a traditional merchant account.

Common pitfalls

Aggregators have stricter underwriting than traditional merchant accounts.
Higher restrictions on certain industries (adult content, crypto, gambling).

What a payment aggregator actually does behind the scenes

When a Delaware LLC accepts a card payment through a service like Stripe or PayPal, the money does not travel through a merchant account that the LLC opened in its own name. Instead, the aggregator holds one large account with the card networks and the acquiring banks, and every customer payment to your business is recorded as a sub-transaction inside that pooled structure. This is the core mechanic that makes onboarding fast for a non-resident founder. You are not asking Visa, Mastercard, or a US bank to underwrite your specific company, which would normally require credit history, a physical presence, and a long application. You are being slotted underneath an arrangement that already exists and is already approved.

The practical effect for a single-member foreign-owned LLC is that the friction of accepting card payments collapses from weeks into minutes. A traditional merchant account application asks for tax returns, processing history, and sometimes a personal guarantee from a US resident. An aggregator asks for far less at signup because it is absorbing the relationship risk and managing it across thousands of merchants at once. The trade-off, which the glossary entry already flags, is that this convenience comes with stricter ongoing underwriting and the ability for the aggregator to freeze or close your sub-account quickly if its risk models flag your activity.

Understanding this structure helps you read the rest of your financial stack correctly. The aggregator is the layer that touches the card networks. Your business bank account, whether Mercury, Wise, Relay, Lili, or Payoneer, is a separate layer where the aggregator deposits your settled funds. Keeping these two roles distinct in your mind prevents a common confusion where founders assume the aggregator and the bank are interchangeable.

Why the aggregator model fits a non-resident founder

Non-resident founders form a Delaware LLC precisely because the entity gives them a clean US legal wrapper without requiring them to live in the country. The aggregator model mirrors that logic on the payments side. Just as the $110 Certificate of Formation buys you a recognized US company without a US address of your own, an aggregator buys you access to US and global card rails without a US merchant account of your own. The two systems were not designed together, but they pair well because both reduce the barriers that historically locked out international entrepreneurs.

Consider the alternative. A direct merchant account through an acquiring bank typically expects the applicant to have a US Social Security Number, a US business address that is more than a registered agent, and a banking relationship with processing history. A founder in Lagos, Karachi, or Buenos Aires usually cannot satisfy those expectations on day one. The aggregator side-steps this by underwriting at the portfolio level and by relying on identity verification rather than US-resident credit checks. That is why most guides for foreign-owned LLCs point new founders toward aggregators first.

This fit is not unconditional. Aggregators verify the human beneficial owner, which for a single-member LLC is you. They will ask for a passport, proof of address in your home country, and a description of what you sell. They are matching the company you formed with a real person they can hold accountable. Having your formation documents, EIN, and a clear business description ready makes that verification smoother and reduces the chance of an early hold.

A worked example: from formation to first card payment

Imagine a founder in Pakistan who sells a digital productivity course. She forms a Delaware LLC, pays the $110 Certificate of Formation, and receives her formation confirmation. She then files Form SS-4 to obtain a free EIN, which arrives in roughly eight to ten business days when filed by fax or mail as a non-resident without an SSN. With the EIN in hand, she opens a Mercury account, which lets her receive USD deposits. Only after these pieces are in place does she create a Stripe account and connect it to Mercury as the payout destination.

When her first customer in Germany buys the course for $90, the card network routes that charge through Stripe as the aggregator. Stripe deducts its processing fee, records the transaction under her sub-account, and then settles the net amount to her Mercury account on its payout schedule. At no point did she negotiate directly with Visa or open her own merchant account. The aggregator handled the network relationship and she simply received cleared funds in her business bank. This is the everyday reality the glossary describes when it says underlying merchants do not need their own merchant accounts.

The sequence matters. Founders who try to create the aggregator account before they have an EIN and a bank account often hit verification walls, because the aggregator wants a tax identifier and a destination for funds. Treating formation, EIN, banking, and payments as an ordered pipeline rather than parallel tasks tends to produce fewer holds and rejections.

Aggregator versus payment facilitator versus merchant of record

The glossary entry notes that Stripe is technically a payment facilitator even though people loosely call it an aggregator, and this distinction is worth unpacking because the words get used interchangeably in everyday conversation. A pure aggregator pools many merchants under a single master merchant account and treats them as sub-merchants of that one account. A payment facilitator, often shortened to PayFac, registers with the card networks to onboard and manage sub-merchants under its own facilitator identification, which gives it more structured obligations around underwriting and monitoring. The lived experience for a small foreign-owned LLC is similar, which is why the terms blur.

The merchant of record is a related but separate concept that matters a great deal for tax and compliance. A merchant of record is the legal entity that appears as the seller on the customer's statement and that takes on responsibility for collecting and remitting sales tax or VAT. Stripe, used as a plain payment processor, is not your merchant of record, which means your Delaware LLC remains the seller and bears the tax-collection responsibility. Services like Paddle or Lemon Squeezy act as merchant of record and shoulder that burden for you, at a higher fee.

For a non-resident founder, knowing which role a provider plays prevents a costly misunderstanding. If you use a plain aggregator, you are the seller of record and you handle indirect tax yourself. If you use a merchant of record, the provider is the seller to the end customer and your LLC sells to the provider. These are different tax pictures, and the related concepts of stripe-payments and merchant-of-record in this glossary are worth reading alongside this entry.

How aggregator funds connect to your business bank account

An aggregator does not store your money long term. It collects card payments, nets out its fees, and then pushes settled funds to the bank account you designate. For a foreign-owned Delaware LLC, that destination is typically a fintech business account such as Mercury, Relay, or Lili for USD, or a multi-currency account such as Wise or Payoneer when you also receive payouts in euros, pounds, or other currencies. The aggregator and the bank are two distinct links in a chain, and money flows from customer to card network to aggregator to bank.

Payout timing depends on the aggregator's schedule and your account's standing. New accounts often face a rolling reserve or a delayed first payout while the aggregator builds confidence in your transaction pattern. This is normal risk management rather than a sign of a problem, though it can surprise a founder who expected instant access. Planning your cash flow around a buffer of several days for early payouts avoids stress in the first weeks of selling.

Currency handling is a quiet detail with real cost implications. If your aggregator settles in USD and you withdraw to a USD account, conversion is minimal. If you settle in USD but in the end spend in your home currency, the conversion happens somewhere, and the rate matters. Multi-currency providers like Wise tend to offer transparent conversion, which is one reason founders pair them with aggregators that settle in several currencies.

Stricter underwriting and what triggers a freeze

The glossary entry warns that aggregators apply stricter underwriting than traditional merchant accounts, and the reason is structural. Because the aggregator pools many merchants under shared rails, one bad actor can create chargebacks and fraud exposure that touch the whole portfolio. To protect the pool, aggregators monitor each sub-merchant continuously and act quickly when patterns look risky. A sudden spike in volume, a wave of chargebacks, a mismatch between your stated business and your actual transactions, or customer disputes can all trigger a review or a hold.

For a non-resident founder, the most common avoidable triggers are vague business descriptions and unexpected volume jumps. If you tell the aggregator you sell consulting and then start processing large numbers of small subscription charges, the model may flag the inconsistency. Likewise, going from zero to thousands of dollars overnight, perhaps after a successful launch, can look like fraud to an automated system even when it is a genuine success. Communicating proactively with the aggregator before a large promotion can reduce the chance of a freeze.

When a freeze happens, the aggregator usually holds funds while it investigates, and access can be restored after you provide documentation such as invoices, fulfillment proof, or customer communications. Keeping clean records of what you sell and to whom turns a freeze from a crisis into a paperwork exercise. This is general information about how these systems behave and not a guarantee of any particular outcome, since each aggregator sets its own policies.

Restricted and high-risk industries

The glossary flags higher restrictions on certain industries, naming adult content, crypto, and gambling, and this list extends to other categories the card networks treat as elevated risk. Aggregators publish prohibited and restricted business lists, and these lists exist because card networks impose fines and chargeback thresholds on the aggregator when high-risk merchants misbehave. To protect the whole pool, the aggregator simply declines or limits these categories rather than underwriting each case individually as a specialized high-risk processor might.

A non-resident founder building in one of these spaces faces a real strategic choice. Trying to disguise the nature of the business to slip past onboarding tends to end badly, because the eventual discovery usually means a frozen account and held funds. The more durable path is to seek a processor that explicitly supports the category, even at higher fees and stricter terms, or to restructure the offering so it falls within accepted categories. Honesty at signup is the cheaper option over time.

It is worth noting that the boundaries shift. Categories that aggregators once refused outright, such as certain crypto on-ramps, have in some cases moved into supported-with-conditions territory as networks developed rules. A founder in a borderline category should read the current restricted list of any aggregator before building a business model that depends on it, rather than assuming yesterday's rules still hold as of 2026.

Aggregators and your US federal tax obligations

Using an aggregator does not change the federal filing duties that come with owning a foreign-owned single-member Delaware LLC. Such an LLC is by default a disregarded entity for US tax purposes, and a foreign-owned disregarded entity must file Form 5472 together with a pro forma Form 1120 each year to report reportable transactions with its owner. The penalty for failing to file Form 5472 starts at $25,000, which makes this one of the more consequential compliance items for a non-resident founder. The aggregator sits upstream of all this and simply moves money into the entity.

What the aggregator does affect is your recordkeeping. Every payout, fee, and refund flowing through the aggregator is part of the financial story your filings rest on. Reportable transactions on Form 5472 are generally between the LLC and its foreign owner, such as capital contributions and distributions, rather than ordinary customer sales, but clean aggregator records help you reconstruct the full picture accurately. Treating the aggregator dashboard as a source document, exporting statements regularly, keeps your year-end filing grounded in real data.

Separately, an aggregator may issue an information return such as a 1099-K when thresholds are met, and the rules around those thresholds have been in flux. None of this constitutes tax advice, and a non-resident founder with meaningful volume generally benefits from a cross-border accountant who understands both the disregarded-entity mechanics and how aggregator reporting interacts with them.

Aggregators and sales tax, VAT, and indirect taxes

A frequent and expensive misunderstanding is that the aggregator handles sales tax or VAT for you. A plain aggregator like Stripe used as a processor does not become the seller of record, which means your Delaware LLC remains responsible for determining where it has a tax-collection obligation and for collecting and remitting accordingly. The aggregator moves money and reports certain data, but it does not assume your indirect-tax liability the way a merchant of record does.

For a non-resident founder selling digital products to customers around the world, this can be genuinely complex. US sales tax depends on economic nexus rules that vary by state and by sales volume. Selling to consumers in the European Union or the United Kingdom can create VAT obligations on digital services regardless of where your LLC is formed. The aggregator will happily process every one of these sales without warning you about the tax consequences, because that is not its role. The responsibility sits with the seller, which is your company.

This is exactly where the merchant of record alternative earns its higher fee. A merchant of record steps into the seller position and takes on the indirect-tax collection and remittance for the jurisdictions it supports, which can dramatically simplify life for a solo founder selling globally. Choosing between a plain aggregator and a merchant of record is therefore partly a tax-operations decision, not only a payments decision, and it deserves thought before you scale.

Where aggregators fit in the formation timeline

The payments layer is one of the last pieces a founder assembles, and the order is deliberate. The typical sequence for a foreign-owned Delaware LLC starts with the $110 Certificate of Formation to create the entity, moves to obtaining a free EIN through Form SS-4 in roughly eight to ten business days, then to opening a business bank account at a provider like Mercury, Wise, Relay, Lili, or Payoneer, and finally to connecting an aggregator for card acceptance. Each step feeds the next, since the aggregator needs the EIN and the bank account to function.

Trying to compress this timeline by skipping ahead usually backfires. An aggregator account created before the EIN exists will stall at verification. A bank account is needed as the payout destination before any aggregator settlement makes sense. Founders who respect the dependency chain tend to reach their first live payment faster than those who open everything at once and then untangle the rejections. With a flat one-time formation price of $297 covering the setup work, the value comes from getting the sequence right the first time.

It also helps to remember what is no longer a blocker. Since the FinCEN Interim Final Rule of March 26 2025, US-formed LLCs are exempt from the beneficial ownership information reporting that once loomed over new formations. That removed one compliance worry from the early timeline, though it does not change anything about how aggregators verify the human owner behind the account, which they continue to do on their own terms.

Fees, reserves, and the real cost of convenience

Aggregators trade convenience for a per-transaction fee that is typically higher than what a large established merchant could negotiate on a direct account. A common structure is a percentage of each transaction plus a small fixed amount, with surcharges for international cards, currency conversion, and chargebacks. For a non-resident founder, these fees are the price of skipping a merchant-account application that would likely be denied anyway, so the comparison is rarely aggregator versus cheaper direct account but aggregator versus no card acceptance at all.

Reserves are a less obvious cost. An aggregator may hold a percentage of your volume in a rolling reserve, releasing it after a set period to cover potential chargebacks. For a new business with no processing history, this is a standard precaution. The effect on cash flow can be meaningful in the early months, so budgeting as if a slice of revenue arrives on a delay keeps you from over-committing funds you have technically earned but cannot yet touch.

Chargeback fees deserve specific attention because they compound. A single disputed transaction can cost you the sale amount plus a fixed dispute fee, and a high chargeback ratio can push the aggregator to raise your reserve or close your account. Managing chargebacks through clear product descriptions, responsive customer support, and prompt refunds is therefore both a service practice and a way to protect your aggregator relationship and your effective cost of processing.

Edge cases that surprise foreign founders

Several edge cases catch non-resident founders off guard. The first is the country-of-availability mismatch. Some aggregators support a Delaware LLC but require the human owner to reside in a supported country, and a founder in an unsupported country may find the aggregator accepts the company but not the person behind it. Checking both the company eligibility and the personal-residence eligibility before building on a particular aggregator avoids a late and frustrating rejection.

A second edge case is the platform-within-a-platform problem. If your Delaware LLC runs a marketplace where you collect money and pay out to other sellers, you may be acting as a payment facilitator yourself in the eyes of the networks, which carries obligations a simple direct-sales business never touches. Aggregators offer connected-account or platform products for exactly this scenario, and using a plain account for marketplace flows can trigger a freeze when the aggregator notices money moving onward to third parties.

A third surprise is account linkage across entities. If you form multiple Delaware LLCs and an aggregator closes one for a policy violation, its risk systems may associate the shared human owner and restrict the others as well. The single beneficial owner ties the accounts together in the aggregator's view. Founders who run several ventures should understand that a clean compliance record on each protects all of them, because the aggregator sees the person, not only the entity.

Common misunderstandings, corrected

The most persistent misunderstanding is that an aggregator account is the same thing as a bank account. It is not. The aggregator processes card payments and settles funds onward, while the bank holds your operating balance and lets you send and receive transfers, pay expenses, and manage cash. A founder needs both, and conflating them leads to confusion about where money lives and why a payout has not yet arrived. The aggregator is a processing layer, and the Mercury, Wise, Relay, Lili, or Payoneer account is where settled money rests.

A second misunderstanding is that forming the Delaware LLC guarantees aggregator approval. The entity is a prerequisite, not a promise. The aggregator still verifies the owner, evaluates the business model against its restricted list, and applies its own risk judgment. A clean, well-described, accepted-category business with a verified owner has a smooth path, but the formation alone does not compel any aggregator to accept the account. The two systems are independent and each makes its own decision.

A third misunderstanding is treating a frozen account as permanent. Freezes are frequently temporary holds pending documentation rather than final closures, and many resolve once the founder supplies invoices, fulfillment evidence, and clear answers. Panic and silence make things worse, while organized records and prompt responses usually restore access. This is general information about typical aggregator behavior and not a guarantee, since outcomes depend on each provider's policies and the specifics of the situation.

Related terms

Related glossary terms & guides

Form your LLC WhatsApp

WhatsApp Form your LLC