Why am I getting decline code 03 on all transactions?

An across-the-board 03 pattern means your merchant account is misconfigured, suspended, or terminated. Stop sending traffic and contact your acquirer before assuming anything about the cards.

Can decline code 03 be caused by my MCC?

Yes. Some issuers decline entire merchant category codes. If 03 clusters around particular issuing banks while other cards approve normally, the issuer is rejecting your category rather than your setup.

Does the customer need to do anything about a code 03 decline?

Usually not. This code points at the merchant configuration. Only involve the customer if their card type is restricted, for example an FSA card used at a non-qualifying merchant.

Decline code · Hard decline

Decline code 03: Invalid Merchant

The problem is on your side of the transaction, not the cardholder's. The issuer or network does not recognize or does not accept the merchant identifier attached to the authorization. Your merchant account setup, MCC, or acquirer configuration is being rejected.

Should you retry?

Do not retry the same card through the same route; nothing changes until the merchant configuration is fixed. Once the MID issue is resolved, or when routing through a correctly configured alternate MID, a new authorization is a fresh attempt rather than a retry of a doomed one.

Why code 03 happens

The merchant ID sent in the authorization is misconfigured, terminated, or not yet fully boarded with the acquirer.
The MCC on the account is one the issuer refuses to authorize, which several issuers do for categories like gambling or CBD.
The transaction was routed through a gateway profile pointing at a closed or suspended MID.
A recent acquirer migration left stale merchant credentials in one of your payment routes.
The card product itself prohibits your merchant category, such as an HSA or government purchasing card used outside allowed MCCs.

What to do about it

Check whether the 03 responses come from every card or only certain issuers; a universal pattern means your MID configuration is broken.
Contact your acquirer or payment provider immediately and confirm the MID is active, correctly boarded, and carrying the MCC you expect.
Audit gateway routing rules for any path still pointing at a decommissioned merchant account.
If declines are issuer-specific, ask your acquirer whether those issuers block your MCC and consider a secondary acquiring relationship.

Frequently asked questions

Why am I getting decline code 03 on all transactions?: An across-the-board 03 pattern means your merchant account is misconfigured, suspended, or terminated. Stop sending traffic and contact your acquirer before assuming anything about the cards.
Can decline code 03 be caused by my MCC?: Yes. Some issuers decline entire merchant category codes. If 03 clusters around particular issuing banks while other cards approve normally, the issuer is rejecting your category rather than your setup.
Does the customer need to do anything about a code 03 decline?: Usually not. This code points at the merchant configuration. Only involve the customer if their card type is restricted, for example an FSA card used at a non-qualifying merchant.

Related decline codes