Merchant Rails What happens to a card payment between the tap and the deposit.

Merchant Rails

DOWNGRADES

Card Not Present Downgrades and How to Stop Paying for Them

By Baruch Mackliff · · 6 min read

A downgrade is a sale clearing at a worse interchange category than it qualified for, and almost every cause is a field your gateway never sent.

You are paying a rate you were quoted, and your statement shows a category you have never heard of on a quarter of your online sales. Nothing went wrong with those sales. They cleared at a worse interchange category than they qualified for, which the industry calls a downgrade and nobody mentions during the sales call.

The fix is almost never a negotiation. Interchange categories are earned by the data attached to a transaction and the timing of when it settles, and a downgrade usually means a field your gateway did not send or a batch that closed a day late. Which is good news. It means this is fixable from your side, without changing anything about your pricing.

Why card not present is where this lives

A chip transaction at a counter qualifies mostly on its own. The terminal reads the card, proves it was there, and sends what the network wanted without asking you anything.

A card not present sale has none of that proof, so the network asks for substitutes: evidence you checked the address, evidence you asked for the security code, evidence the transaction settled promptly, evidence about what kind of order it was. Each of those is a field. Every field is a default somewhere in your gateway or your shopping cart, and defaults were set by whoever installed it.

Which raises a question worth asking out loud: who set those defaults, and when? On most small businesses the answer is a developer who finished the site three years ago, or a plugin update that quietly reset a configuration screen nobody has opened since. Nothing in your daily reporting will show you a missing field. The authorization succeeds, the customer is happy, the money arrives, and the cost of the omission surfaces a month later under a category name that means nothing to you.

Where the sale falls out of category

One item that belongs on no fix list: cards issued outside the United States. Those clear into different categories entirely and carry cross border charges, and no data you send changes that. Identify them so you stop chasing them.

If you sell to other businesses, start here

A corporate, purchasing or government card carries its own interchange categories, and reaching the better ones requires data that consumer sales never need.

Level 2 is the sales tax amount and a customer reference, usually the buyer's purchase order number. It is a small amount of work, it is supported by most gateways, and it is often a checkbox plus a habit at order entry.

Level 3 goes further, with a line for every item: description, quantity, unit of measure, unit price, product code, plus freight and duty. It requires your order data to reach the gateway properly, which usually means an integration rather than someone typing into a virtual terminal.

Here is the arithmetic, with the gap stated as an assumption rather than a fact, because the actual gap depends on your categories. Take a supplier running 120,000 dollars a month, of which 45,000 is on commercial cards clearing without level 2 data. If the difference between the category they reach and the one they could reach is six tenths of a point, that is 270 dollars a month. Over a year it is the cost of the integration, several times over.

Work out your own version before you commit to anything, using your real commercial card volume and the real category difference from your statement. If your processor cannot produce both numbers, that is its own finding.

Finding yours

Ask your processor for the interchange qualification detail for a full month: every category your volume landed in, the volume in each, and the count. Then sort it.

Downgrade categories tend to announce themselves. They sit at the expensive end, they carry generic names rather than the specific program names, and they collect a share of your volume that has nothing to do with what you sell. Look for the categories where your card not present volume piled up, and look at whether the same amount piles up there every month or arrived suddenly after somebody updated your cart.

If your statement does not show categories at all, only buckets with names like qualified and non-qualified, you cannot do this exercise. That is not your fault and it is not a reason to give up. It is a reason to ask what your account would look like on pass-through pricing, because the reporting is the thing you are buying.

The order to fix them in

  1. Turn address verification and the security code back on in the gateway, then run a test sale and read the response fields to confirm both were actually submitted.
  2. Close your batch every day, automatically, at a time that suits your operation rather than whenever someone remembers.
  3. Match settlement to authorization wherever your workflow allows, and ask your processor which of your transaction types support incremental or delayed authorization.
  4. Pass the authentication and stored card indicators. Usually a configuration change at the gateway, sometimes a change at the cart, occasionally a version upgrade that has been sitting undone.
  5. Add level 2 data if commercial cards appear anywhere in your mix. Then measure for a month before deciding whether level 3 is worth the integration.

Run the whole list against one test transaction before you trust any of it. Put a real card through your own checkout for a small amount, then pull that single transaction's detail from the processor and read which fields actually arrived. A setting that looks enabled on a configuration screen and a field that reached the network are two different claims, and only the second one is worth anything.

Then check the category report again after a full billing cycle. That report is the only proof that anything changed, and it is the one document to ask for by name every quarter from now on.

Common questions

what is a downgrade in credit card processing

A downgrade happens when a transaction clears at a more expensive interchange category than the one it could have reached, because something the card network wanted was missing, late or mismatched. The sale still goes through and the customer sees nothing, so the only place it shows up is on your statement. On pass-through pricing you can see the category by name, and on tiered pricing you cannot see it at all.

why do my keyed in transactions cost more

Keying a card removes the proof that the card was physically present, so the transaction is priced as a card not present sale and carries the higher risk that goes with it. It can drop further if the address verification request and security code were skipped while keying. Where a card is genuinely in front of you, reading the chip or the tap is worth the extra few seconds every time.

what is level 3 processing data

Level 3 is the line item detail sent with a commercial or purchasing card transaction, including item descriptions, quantities, unit costs and freight, on top of the tax amount and purchase order reference that make up level 2. Card networks price transactions carrying this data into better categories, because the extra detail is what corporate card programs need for their own reporting. It matters for businesses selling to other businesses and government buyers, and it does nothing for consumer card sales.

More on this