Payments basics
Invalid merchant ID (decline code 03) on a card terminal: what to check
Invalid merchant or code 03 on every card usually means the terminal's merchant or terminal ID does not match the processor. What to check and who must reprogram it.
- Applies to
- All payment terminals
- Last reviewed
- Oct 27, 2026 by Abdul Rashid
Exact messages this covers
Invalid merchantInvalid merchant number03
Check first
- Does every card fail with the same message, or only one card?
- Did this start with a new or replacement terminal, a reprogramming or download, or a change of processor or bank account?
- Has the processor confirmed the merchant account is open and active?
"Invalid merchant" (response code 03) means the card network or processor does not recognize the merchant the terminal is sending. When it happens on every card, the terminal's merchant ID or terminal ID usually does not match what the processor has on file, or the account is not active yet. Allstar or your processor must fix the terminal setup; it is not something to change at the counter.
Before you start
- Have your processor's name and phone number ready.
- Think about what changed recently: a new or replacement terminal, a reprogram or download, a change of processor or bank account.
- Worldpay's interface guide says a terminal can only connect when it is configured with valid bank, merchant and terminal numbers. A mismatch on any of them causes rejections.
Steps
- Run a second card from a different bank. Expected: if it approves, this is not a merchant ID problem (see the decline codes guide). If it fails the same way, continue.
- Write down when it started and what changed just before. Expected: you have the likely trigger for the support call.
- Call your processor. Ask them to confirm the merchant account is active and that this terminal is set up on their host under your merchant ID and terminal ID. Expected: they find the problem on their side, or confirm the terminal is sending the wrong IDs.
- If the terminal needs new settings, contact Allstar support to reprogram it. Do not type merchant or terminal values into the setup menus yourself. Expected: Allstar reprograms or downloads the correct setup for your processor.
- After reprogramming, run your next sale as normal. Expected: approval.
- Never read out your merchant ID or terminal ID to an unexpected caller who says they are fixing this. Call your processor or Allstar on a number you already know. Expected: your IDs stay private. Visa warns that criminals use merchant and terminal IDs to clone terminals.
If that did not work
If the processor confirms everything on their side and the terminal still shows Invalid merchant, contact Allstar support with the model, serial number, payment application, processor and the exact message on screen. If the terminal asks for a setup password, stop: setup passwords are never shared here.
Sources
- Worldpay Merchant Batch Authorization and Deposit File Reference Guide, Appendix D (V2.10, February 2024)
- Worldpay 610 Interface Reference Guide (V2.51, April 2025)
- Mastercard Developers: Network Response Codes
- Visa: Updates to Rules for Declined Transaction Resubmission and Use of Authorization Response Codes (3 September 2020)
- Visa Payment Facilitator and Marketplace Risk Guide (April 2021)
Stop and contact support if
- The terminal asks for a setup or admin password: stop and contact Allstar support. Passwords are never given here.
- Any tamper or security message on screen: stop, do not reboot repeatedly, contact support.
Contact Allstar support (support@allstarterminals.com, 888-403-7066, Monday to Friday 9 AM to 5 PM Central) with the model, serial number, payment application, processor and the exact message on screen.
Notes
- Code 03 is 'Invalid merchant' on Visa, Mastercard and Discover (Worldpay and Mastercard tables). The screen may show the words, the code, or a processor-specific message.
- Visa moved code 03 into its 'cannot approve at this time' category in 2021, so it can be temporary. If it clears on its own within minutes, it was likely a host-side issue.
- That the terminal's IDs must match the processor is stated by Worldpay for its own host ('valid bank, merchant, and terminal numbers'). Other processors work the same way, but their setup steps are not documented here.
- No parameter values are given. Setup is done by Allstar or the processor.
Sources
- Worldpay Merchant Batch Authorization and Deposit File Reference Guide, Appendix D: Network Response Codes · V2.10 · 2024-02 · read 2026-10-26 · card network, standards or processor documentation
- Worldpay 610 Interface Reference Guide, Chapter 1 (TLS connection criteria) · V2.51 · 2025-04 · read 2026-10-26 · card network, standards or processor documentation
- Mastercard Developers: Network Response Codes (Mastercard Send Disbursements) · read 2026-10-26 · card network, standards or processor documentation
- Visa: Updates to Rules for Declined Transaction Resubmission and Use of Authorization Response Codes · Article ID AI10325 · 2020-09-03 · read 2026-10-26 · card network, standards or processor documentation
- Visa Payment Facilitator and Marketplace Risk Guide, section 4 (Merchant Cloning) · Visa Public · 2021-04 · read 2026-10-26 · card network, standards or processor documentation
Was this guide helpful?
Thanks. The team reviews this feedback.
