Processing History: What Underwriters Mean and How a New Merchant Builds It

Processing history is the monthly statements a processor issued to your entity: volume, average ticket, refunds, chargebacks, reserves and how long the account lasted. Without it, the acquirer prices the file on its assumptions for the vertical, so reserves and caps start conservative. Only statements issued to the applying entity count as its own history. You build it by processing the declared business cleanly under one entity.

Processing history is the record of what a merchant account actually did: the monthly statements a processor issued to your business, showing settled volume, average ticket, refunds, chargebacks, reserves held and how long the account stayed open. Underwriters read it as the best evidence of how your next account will behave. A new entity has none, so the acquirer prices the file on its assumptions for the vertical: typically a higher reserve, a lower monthly cap and closer monitoring until statements exist. You build history by processing cleanly under one legal entity, month after month, and keeping every statement. This guide covers what counts as history, what does not, and how to build a clean record from the first month; the document checklist guide covers the rest of the application file.

What underwriters mean by processing history

When an underwriter asks for processing history, they mean merchant statements: the monthly documents a processor or acquirer issues to the merchant of record, in the legal name of the entity that holds the MID. A statement is not a sales export and not a dashboard screenshot. It is the processor's own account of what it settled to you, what it charged you and what it held back. Underwriters ask for the most recent months, and for more of them when the vertical, the ticket size or the delivery gap raises the exposure.

• Settled volume by month: how much was processed, and whether it grew steadily or jumped.
• Average and highest ticket: what one dispute costs the acquirer, and whether the ticket matches the website.
• Refund count and ratio: how complaints were handled before they became chargebacks.
• Chargeback count and ratio: the number the card networks monitor.
• Reserves and fees: what the previous acquirer held back and charged.
• Longevity and closure: how long the account stayed open, and whether it closed by your choice, by the processor's, or for cause.

Why a file without history is priced more conservatively

An underwriter sizes three things at boarding: the merchant discount rate, the reserve and the monthly volume cap. All three are priced on expected loss, and the estimate is wider when there is no observed behaviour to narrow it. With statements, the underwriter prices against your observed refund ratio, chargeback ratio and volume. Without them, the file is priced on what the acquirer assumes about your vertical and billing model, and the assumption is deliberately conservative because the acquirer carries the loss if it is wrong. That is not a penalty for being new; it is the acquirer covering the outcomes it cannot yet rule out.

A fresh entity is the normal starting point. Each IBOCore package is a US LLC or C-Corp with an EIN, a nominee director, the Independent Business Operator (IBO), and a business bank account in the company's name, and the entity has never been used for processing. That is by design: there is no previous account to explain, no other merchant's disputes attached and no history that could taint the application. The first months of terms will reflect the missing statements; the rolling reserves guide on this blog covers what those terms look like and how to fund them.

What counts as processing history, and what does not

The test is simple: history belongs to the merchant of record. A statement counts when a processor issued it to the entity that is applying, in that entity's legal name, for an account that entity held. Underwriters have seen every substitute, and a substitute presented as history costs more credibility than the gap it was meant to fill.

Two of these need care. If you ran a merchant account under a previous company, its statements can be relevant, and an account that ended badly is a bigger problem when the underwriter finds it than when you explain it. But those statements do not become the new entity's history: they are attached with the relationship written out in the application, and the underwriter decides their weight. Aggregator dashboards are the other trap. If you processed through an aggregator, request the statements or account history the aggregator issued; a screenshot of a dashboard total, with no issuer and no dispute detail, is not a document an underwriter can rely on. The guide on preparing bank statements for underwriting covers the bank side of the same file.

Building a clean record from the first month

History is made of the statements you generate, so the first months of processing are the file you will hand to the next underwriter. The practices below are what a clean record looks like from the processor's side. All of them are easier to keep from day one than to repair later.

1. Process the business you declared: same products, same website, same billing model as the application. A new offer or billing model is disclosed to the acquirer before it goes live, not discovered on a statement.
2. Keep one billing model per MID. Mixing one-time sales and continuity billing on one account typically gets the whole account underwritten as continuity, and blurs the record.
3. Ramp volume steadily toward the projection and the cap. A flat start followed by a sudden spike is the shape underwriters associate with bust-out fraud, even when the cause is a campaign that worked.
4. Refund before the dispute. A refund issued on the first complaint appears on the statement as a refund; the same complaint left alone can become a chargeback, the number the networks count.
5. Use a billing descriptor the cardholder recognizes, and keep the support contact on it answered. Unrecognized descriptors are a common source of disputes.
6. Keep delivery proof, fulfillment records and customer correspondence for every order, so the disputes that do arrive can be represented with evidence.
7. Keep the settlement account clean: settlements land in the business bank account in the entity's name, with no personal transactions and no third-party deposits, so the bank statements corroborate the processor statements.
8. File every statement the month it arrives and read it the way an underwriter will: chargeback ratio against the network thresholds, refund ratio, average ticket drift, volume against projection and cap, reserve releases, fees and adjustments. A drift caught early is a conversation with your ISO; left for months, it is a risk review.

When to bring the record back to the underwriter

The record has two uses. The first is a review of your existing terms: reserve, cap and pricing. Ask for it with statements in hand, ratios inside the thresholds and volume stable, and ask the acquirer what it would need to see for the terms to move. Whether and when they move is the acquirer's decision, on its timeline. No number of clean months entitles a merchant to a change, and a provider who promises one is describing something it does not control. The second use is the next application. Statements in the entity's name let an additional MID at another acquirer be underwritten on evidence rather than assumptions. On an IBOCore package the director who signed the first application takes that call too, so the statements and the director have to tell the same story.

On the IBOCore side, the package gives the record one entity and one director to accumulate under: a director qualified in-house, with a clean record and a credit score of 650 or more, available for verification calls for the active life of the package; a bank account at Bluebanc or Relay with full operational access, so settlements and releases land where the statements say; and no clawbacks if an acquirer terminates a MID. The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model. Ongoing billing starts 30 days after delivery. Acquirer onboarding then typically takes 3 to 10 business days, on the acquirer's timeline, and the decision is the acquirer's.

Questions merchants ask

How many months of statements count as a processing history?

There is no fixed number an underwriter accepts as complete. A longer record inside the thresholds is read more favourably than a short one, but the shape matters more than the count: steady volume, low and stable ratios, no unexplained gap and no closure the application leaves out. A few clean months already change what the file is read against, because the acquirer now has observed behaviour instead of assumptions. How much weight that carries is the underwriter's call.

Can I use my previous company's statements for the new entity?

Not as the new entity's history. Statements belong to the merchant of record that received them. If you operated a merchant account under another company, its statements can be presented as context, with the relationship between the two businesses written into the application and the reason the previous account ended stated plainly. Decide with your ISO before filing whether and how to present them. What never works is attaching them silently or presenting them as the new entity's own.

Should I build history somewhere else before applying with a fresh entity?

History built under another entity does not transfer. The record you need is the one under the entity that will hold the MID, so start on the entity you intend to keep. A fresh IBO package begins where every new merchant account begins: on projections, the website, the description and the signer, with the reserve and cap set on the vertical's assumptions. What it brings is an entity with nothing to explain, a director who takes the verification call, and a settlement account in the company's name.

High-risk MID metrics acquirers watch

Once live, your chargeback ratio (CB ratio) is chargebacks divided by transactions; Visa VDMP and Mastercard ECP programs trigger when you breach network thresholds. Rolling reserves (often 10% for 180 days) protect the acquirer against future disputes. MATCH (Terminated Merchant File) is the industry blacklist after a forced termination. MCC (Merchant Category Code) must reflect your real vertical; miscoding is a scheme violation.

• Representment: fighting a chargeback with delivery proof and logs.
• RDR / Ethoca alerts: pre-chargeback refund tools that protect your CB ratio.
• Statement descriptor: keep it recognizable to cut "friendly fraud" disputes.
• Processing cap: volume limit until the acquirer trusts your history.

MID stacking without structure

Spreading volume across many MIDs without separate entities looks like ratio gaming or transaction laundering to risk teams. The durable pattern is one IBO package per MID, clean descriptors, honest MCC, and reserves treated as a cost of doing high-risk volume.

FAQ: quick answers

How fast can I get an IBO package on IBOCore?

Available inventory ships the same day after payment. You receive Articles, EIN letter, registered agent details, bank onboarding pack and signer contact through your merchant dashboard. Processor onboarding typically follows over the next one to two weeks.

Where can I look up payment-processing jargon?

Use the Resources glossary on IBOCore (/resources) for 580+ definitions: MID, chargeback ratio, MATCH, rolling reserve, MCC, RDR, KYB and high-risk vertical vocabulary.