Error:
9822 Card [card type\blank] for Merchant Id XXXXX not found
or
9822 Card [card type] not found for Merchant Id XXXXX
Meaning:
This error occurs when the merchant is attempting to process a form of payment they do not accept.
- If no card type is shown on the error see the special case(s) at the bottom.
- If performing Shift4 Bridge 3700 setup see the special case(s) at the bottom.
Example:
UTG\Datacenter Processing,
i4Go Tokenization,
Resolution:

If it is not an accepted card type then the merchant will need another form of payment. If the merchant would like to be able to accept these card types in the future, then follow the Customer Request Handling Document which can be located in support favorites or policy and procedures> escalation> customer request handling. Place the case in account setup priority and notify the merchant someone will be reaching out to them.
If it is an accepted card type, then this error should not have occurred but it is possible that if they were manually entering the card number, and that it was mistyped. Have the merchant try the transaction again.
Special Cases:
[No Card Type Shown]
If no card type is shown on the error context then this error can occur if the merchant attempts to activate a chip card reader and does not have a valid API TID being passed in the request.
To resolve this, the API TID will need to be defined by the POS/PMS or the merchant, once the API TID is verified, either update the UTG Tune up to match or update the POS to match the pin pad device's API TID in the UTG.
Restaurant Manager
- The Shift4 Gateway setting's in Station Configuration require RM administrative privileges. Open the RM Back Office Module using a RM administrative account and navigate to Setup > Station Configuration. Click "Admin Settings" to access the RM Gateway / Payment Processing Interface on the station list tree. Make sure you are on the correct Station Number
- RM Gateway / Processing Interface tree:
- Credit Card System = No Interface
- Credit Card Processor (for NetEPay) = Generic
- Shift4 Gateway Integration Options
- Terminal ID
Future POS
- Navigate to Future POS Back Office on the Server
- Select Settings > System Devices
- Select the Terminal Tab then the Credit / EMV Tab
- Enter the following information. Each workstation must be configured.
- Select Device Settings
- Address: Enter UTG IP address
- http://127.0.0.1
- Port: Enter UTG Network Port
- 16448
- Terminal ID: Terminal ID must match UTG Configuration Sheet and API terminal ID that was input in the UTG Device
POSitouch
Should a site need to use an API TID with a terminal, where the terminal number and API TID does not match, set the option in Backoffice Setup
- Backoffice Setup
- Hardware
- Terminal Stations
- S4 TID.
This issue can also be caused by the interface passing back an incorrect access token. Correcting the access token (either sending the proper one or generating a new one if need be) resolves the error.
- Access tokens can be checked in my portal under the Support section by click on “DOTN Access Tokens” and searching for the property.
- Agents can use this as a reference when reaching out to the interface to see if the access token they’re sending matches.
If for whatever reason, the interface cannot tell us what access token is being sent, we should be able to get it out of trace (at which point escalating to a TA would be required)
InfoGenesis / RGuestPay
API TID mismatches with InfoGenesis / RGuestPay can produce a similar 'Invalid card for merchant ID' error. The error in question does not necessarily appear in Citadel and will likely report in the interface.
For more information on assigning API TIDs with RGuest Pay, see Interface: Agilysys RGuestPay.
[New Setup for Micros RES 3700\Bridge Only]
This error can occur on an accepted card type in Micros 3700 RES if there is preamble data attached to the assigned tender type. You will need to access the POS Configurator and clear the preamble data and save the tender type.
To start, navigate to ...\MICROS\Res\Pos\Bin on the Micros Server and open poscfg. This opens the POS Configurator. At this time you will be prompted to log-in, use a Micros User with read\write privileges to the database.
- Select the Sales Tab, then select Tender / Media.
- On left is the Tender Record List, click on the assigned tender type experiencing the issue.
- Select the Credit Auth sub-tab, then the Preambles sub-tab.
- Clear all data listed here.
- Save the Config when done by pressing the green checkmark.
- Reboot and test a transaction.