The short answer to what are third-party payment processors: they are companies that let you take card payments under their merchant account rather than one issued in your business name. You sign up in minutes because you are joining an account that already exists. Everything else about them follows from that.

What are third-party payment processors?

They are also called aggregators or payment facilitators, and the model is exactly what the name suggests. The company holds one master merchant account with an acquiring bank, and every business that signs up sits underneath it as a sub-account.

The acquirer underwrote the aggregator, not you. That is why you were not asked for statements, why there was no application to speak of, and why you could take a card the same afternoon. It is also why the aggregator, rather than a bank, is the one deciding whether you stay.

Why signup takes minutes and closure takes seconds

Underwriting still happens. It just happens after you start, continuously, in software.

An aggregator manages risk across its whole merchant base. Its models are tuned to protect the pool, and a pattern that is ordinary for your business can be unusual against the average of everybody else’s. When a threshold trips, the response is automatic: a hold, a review, a limit, or a closure notice with a paragraph of explanation.

None of that is malice, and it is not a mistake in their design. It is the design. The same automation that let you skip underwriting is the automation that reviews you without a conversation. We wrote up the specific mechanics in why Stripe and Square close accounts.

The part nobody mentions at signup

An aggregator closing your account is not always the end of it. When a termination meets a card network’s criteria, the terminating party is required to report the business to Mastercard’s MATCH database, and that reporting duty applies to aggregators the same as to any other acquirer.

Mastercard’s published rules give the processor one business day to add a qualifying terminated merchant, listings run five years before Mastercard purges them automatically, and removal is available only from the acquirer that placed the listing, only where it was added in error or where reason code 12 for PCI non-compliance has since been resolved. Mastercard does not assess whether a listing is accurate.

That is the real asymmetry of the model. Onboarding took ten minutes and carried no scrutiny. The exit can carry a five year record that every future acquirer reads. Processing with a MATCH listing covers what happens next.

What to check before you rely on one

  • Read the acceptable use policy and the prohibited business list, in full, before you build. Both are published, and both are the actual contract.
  • Find out whether your product category appears anywhere in them, including as a component of what you sell rather than the headline.
  • Know where your payout account sits and what happens to funds already in flight if the account is limited.
  • Check whether your stored customer cards can be exported to another provider.
  • Have a second route to taking money that does not depend on the same company.

That last one is not paranoia. It is the reason a second merchant account exists as a normal business practice for anyone in a category that gets reviewed.

When an aggregator is genuinely the right answer

Testing something new. Low volume. A product category clearly inside the published policy. A business where a week without card payments would be annoying rather than fatal. Under those conditions the speed is worth having and the risk is small.

The calculation changes when card revenue is the business. At that point you want an account underwritten in your own name, with an acquirer who reviewed what you actually sell and cannot be surprised by it later. The differences in daily life are laid out in the aggregator versus dedicated account comparison, and your checkout does not need to change to make the switch if you are on a gateway that can route to more than one acquirer.

Frequently asked questions

Is a third-party payment processor the same as a payment gateway? No. The gateway moves the transaction message. A third-party processor also holds the merchant account your money settles through. Many aggregators sell both together, which is why the terms get used as if they were one thing.

Do third-party processors cost more or less? Their headline pricing is simple and flat, which suits low volume. A dedicated account prices your specific business, which usually suits higher volume. Compare written schedules rather than headline rates, and include reserve terms in the comparison.

Can I use an aggregator and a dedicated account at the same time? Yes, and plenty of businesses do. One handles a specific channel or a test product while core volume runs through the underwritten account. Keep the descriptors clear so customers recognise both on a statement.

If an aggregator closes me, can I just sign up with another one? Sometimes, briefly. If the closure produced a MATCH listing, the next aggregator sees it during screening. Stripe publishes that it generally cannot process for MATCH-listed businesses absent extenuating circumstances, and it is not alone in that stance.

Why did nobody warn me about any of this? Because the sales path is designed for speed, and the risk terms live in the policy documents rather than the signup flow. If your account has already closed, the order of operations after a termination matters more than the post-mortem.

Sources: Mastercard Security Rules and Procedures Merchant Edition, and Stripe published documentation at docs.stripe.com/disputes/match.