Appendix D: Common Notes Field Values

Note	Description	Likely outcome of transaction	Action/ Troubleshooting
Accepted by EHI	Authorisation accepted by the external host.	Accepted	No action required.
Accepted by EHI Gen: Pre-Authorization Request	Pre-authorisation request accepted by the external host.	Accepted	No action required.
Accepted by EHI ASI card	ASI (Account Status Enquiry) authorisation accepted by the external host.	Accepted	No action required.
Accepted with load via EHI	Authorisation accepted by the external host with load.	Accepted	No action required.
ASI.... AVS check ASI card	Account Status Enquiry – Address verification system.	Usually accepted	No action required.
ASI.... CVC check ASI card	Account Status Enquiry – CVC (Card verification Code) check.	Usually accepted	No action required.
Auth Reversed on [Transaction Date]	The authorisation was reversed on a particular date.	Nothing changes on this transaction line.	Find reversal on the mentioned date and see notes field.
AUTOMATIC AUTHORISATION REMOVAL BillAmt – [Billed amount] Location – [transaction Location]	Authorisation has been reversed. Usually this note refers to the hanging authorisation filter.	Credits bill amount to available balance.	No action required.
BLACKLIST	This merchant (card acceptor id) is not allowed as per the card acceptor blacklist assigned to the card.	Always declined	Remove Card acceptor id from the blacklist via Smart Client or web services.
C01 - Person-to-Person	Type of credit authorisation that is person to person. These values are received in DE48 subelement 77 known as Transaction Type Identifier. Note that the values are discontinued.	Accepted or declined based on usage group rules.	Check usage group Rules.
C04 - Gaming Re-pay	Type of credit authorisation for gaming and gambling. These values are received in DE48 subelement 77 known as Transaction Type Identifier. For more details, refer to Mastercard's Customer Interface Specification.	Accepted or declined based on usage group rules.	Check usage group Rules.
CardRequest.XML load by	Card Load performed by CRI file.	Accepted Load	No action required.
CB:Charged Back on CBC: Chargeback Credit confirmed on	This shows when a presentment is charged back.	Either an accepted Chargeback or rejection.	Check the Chargeback screen to show all Chargeback information.
Declined by Ext Auth	The authorisation was declined by the external host operating external authorisation.	Always declined	Check external host for decline reason.
Declined by EHI	The external host has declined the authorisation.	Always declined	Check decline reason on External Host.
DR: AF:Mag ATM attempt	Magnetic stripe used at an ATM. The hard-coded block is still applied to this product.	Always declined	To remove block, gain issuer sign off and raise a change request with Thredd via Jira.
DR: ARQC not matching	The ARQC (Authorization ReQuest Cryptogram) generated by the card does not equal the ARQC generated by Thredd.	Always declined	This can be due to issue with the Card manufacturer, network, Thredd, Terminal etc. If this is a recurring issue, please raise to Thredd.
DR: Auth Amount	The card does not have enough available funds for the authorisation.	Usually declined, unless the external Host overwrites and accepts the authorisation.	Load the card with the required amount. If enough Available funds please check the value of fees applied etc.
DR: Auth Amount Total : Available Amount : ==> Decline! Declined by Thredd Accepted with load by EHI	Authorisation declined by Thredd but accepted with load by EHI.	Accepted	No action required.
DR: AVS Failed because of: Address not Matching	Address verification system failure. The address sent to Thredd in the authorisation message does not match the address details held.	Usually declined. Thredd can configure to accept if AVS is wrong.	Ensure the cardholder is using the address registered in the ‘Cardholder details’ held under the card details on Smart Client.
DR: AVS Failed because of: House No not Matching	Address verification system failure. The house number of the address sent to Thredd in the authorisation message does not match the details held by Thredd.	Usually declined. Thredd can configure to accept if AVS is wrong.	Ensure the cardholder is using the address registered in the ‘Cardholder details’ held under the card details on Smart Client.
DR: Bad Retailer	This retailer has been blocked via the merchant blacklist.	Always declined	Merchant has been blocked for fraudulent behaviour. Contact Thredd for details.
DR: Card expiry check failed with Emboss Expiry date (DE014)	The expiry date sent to Thredd in the authorisation message does not match the expiry date held by Thredd (This is the embossed expiry of the card),	Always declined	Advise the cardholder to use embossed Expiry. If issue persists there could be an expiry misalignment, if so raise a Jira for Thredd Operations.
DR: Card Service Code check failed, Txn MSR Track 2 service code=xxx but Thredd service code=xxx Declined by Thredd	The service code in the track 2 data of the authorisation message does not match the service code held by Thredd.	Always declined	Validate transaction with cardholder as this can indicate a fraudulent card transaction attempt involving card skimming. If persists and is a valid transaction contact Thredd/merchant.
DR: Card usage group check…. Card Acceptance Method (A) - (Rule causing decline specified)	The POS (Point of Sale) entry mode used (DE22) is not allowed as per the card usage group assigned to the card.	Always declined	Change the usage group assigned to the card, gain issuer sign off and raise a change request to allow this Entry mode or tell the cardholder to use a different POS Entry mode.
DR: Card usage group check…. Transaction type (T)	The transaction type (processing code) is not allowed as per the card usage group assigned to the card.	Always declined	Change the usage group assigned to the card, gain issuer sign off and raise a change request to allow this transaction type.
DR: CAVV incorrect (checked by	The cardholder Authentication Verification Value was incorrect.	Always declined	Potential attempted Fraud as incorrect authentication value has been passed.
DR: CVC1 does not match	The CVC1 sent to Thredd Does not match what we hold.	Always declined	Potential fraud due to card skimming. Contact cardholder to confirm.
DR: Declined due to Expired card	The card is expired.	Always declined	Check if the card expired correctly as per the configuration detailed on the Product Set up Form.
DR: Declined due to Card Destroyed (Original status 83, changed to 05)	Card status is set to 83 -destroyed.	Always declined	Order new card Via WS_Regenerate.
DR: Declined due to Do not honour	Card Status is set to 05 - to do not honour.	Always declined	Change status to 00 – All good or order new card.
DR: Declined due to Do not honour Declined by Thredd (EHI sent decline notification)	Card Status is set to 05 - to do not honour.	Always declined	Change status to 00 – All good or order new card.
DR: Declined due to GroupMCCCheck	The MCC (Merchant Category Code) passed in this authorisation is not allowed as per the MCC group assigned to the card.	Always declined	Remove this MCC from the MCC group or advise the cardholder to use a merchant with a different MCC.
DR: Declined due to Invalid card number (no such number) card not found	The Card number (PAN) passed in DE 2 is not recognized by Thredd.	Always declined	Either an accidental entry by the cardholder or attempted Fraud. No action required.
DR: Declined due to Limited network Check	This merchant is not included in the limited network assigned to the card.	Always declined	Advise the the cardholder to use the card within the allowed limited network.
DR: Declined due to Lost Card (Capture)(Original auth resp status 41, changed to 05)	Card Status is set to 41 – Lost card.	Always declined	Order new card via Webservices. (WS_regenerate)
DR: Declined due to Restricted card (Card is not active)	This card has not been activated.	Always declined	Activate card via Smart Client, Webservices or phone/IVR line, (Activation methods available depend on the product set up).
DR: Declined due to technical fallback transactions	The transaction declines due to the phasing out of the magstripes.	Always declined	Advise the cardholder to use the chip/contactless.
DR: Declined due to voided card (Original auth resp status 99, changed to 05)	Card Status is set to 99 – Voided card.	Always declined	Change status to 00 – All good or order a new card.
DR: Emboss CVC2 not matching with CVC2 on PDS92	The CVC2 sent to Thredd in the authorisation message does not match the CVC2 held by Thredd.	Usually declined. Can be configured to accept for VISA if no CVC2 is provided.	Advise the cardholder to use embossed Expiry. If issue persists there could be an expiry misalignment, if so raise a Jira for Thredd Operations.
DR: Exceeds Max Per Transaction limit	The authorisation value (bill amount) is higher than the maximum per transaction limit in the Limit group assigned to the card.	Always Decline	Upgrade Card to a different Limit group, or wait until the limit group allows this to be completed (time dependent on the configuration.)
DR: Exceeds withdrawal amount limit	This authorisation would exceed the daily withdrawal limit as per the Limit group assigned to the card.	Always declined	Upgrade Card to a different Limit group or wait until the limit group allows this to be completed (time dependent on the configuration.)
DR: Exceeds withdrawal amount limit for the Accum period 1	This authorisation would exceed the accumulated period 1 withdrawal limit as per the Limit group assigned to the card.	Always declined	Upgrade Card to a different Limit group or wait until the limit group allows this to be completed (time dependent on the configuration.)
DR: Exceeds withdrawal amount limit for the Accum period 2	This authorisation would exceed the accumulated period 2 withdrawal limit as per the Limit group assigned to the card.	Always declined	Upgrade Card to a different Limit group or wait until the limit group allows this to be completed (time dependent on the configuration.)
DR: Exceeds withdrawal frequency limit	This authorisation would exceed the frequency limit as per the Limit group assigned to the card, , only 10 withdrawals are allowed per day.	Always declined	Upgrade Card to a different Limit group or wait until the limit group allows this to be completed (time dependent on the configuration.)
DR: Exceeds withdrawal frequency limit for the Accum period 1	This authorisation would exceed the accumulated period 1 frequency limit as per the Limit group assigned to the card, e.g. Only 10 withdrawals are allowed per week.	Always declined	Upgrade Card to a different Limit group or wait until the limit group allows this to be completed (time dependent on the configuration.)
DR: Incorrect Pin	PIN used by the cardholder does not match the PIN held by Thredd	Always declined	Send PIN reminder to the cardholder. If the PIN is blocked, send a PIN block script and advise to use EMV capable Chip and ATM.
DR: Invalid Merchant	This merchant is not allowed as per the settings of the card. e.g., hard-coded AFD block or calendar group.	Always declined	Request Thredd to remove hardcoded AFD block – Issuer approval required via a change request/Jira. Advise the cardholder to use within the allowed time/date (calendar group.)
DR: ICVV does not match	The ICVV value sent to Thredd is Incorrect. ICVV is a card verification value stored/composed on the chip in EMV scenarios.	Always declined	This can be due to issue with the Card manufacturer, network, Thredd, terminal etc. If this is a recurring issue, please raise to Thredd.
DR: Invalid Use of Chip card in POS terminal, with no chip data	POS entry mode is Chip, but the card is not chip-capable.	Always declined	Potential Fraud - Contact cardholder to ensure that they still have the card, block and re-order card. Confirm in the transaction details that Entry mode is incorrect.
DR: Online Pin try limit exceeded	Online PIN is blocked due to too many incorrect entries. (3)	Always declined	Send a PIN unblock script to card. The Product Manager may decide to carry out cardholder verification and send a PIN reminder to the cardholder. Advise cardholder to use EMV capable chip and PIN for ATMs.
DR: Offline PIN try limit exceeded	Offline PIN is blocked due to too many incorrect entries. (3)	Always declined	Send a PIN unblock to the card. PM may decide to carry out cardholder verification and send PIN reminder to the cardholder. Advise cardholder to use EMV capable chip and PIN POS, or advise them to go to an ATM and unblock the PIN.
DR: Declined due to Security Violation	Card Status is set to 63 because of security violation.	Always declined	Change card status to 00 - All good.
DR: Decline due to Whitelist	This merchant (card acceptor id) is not allowed as per the card acceptor whitelist assigned to the card.	Always declined	Add card acceptor id to the whitelist via Smart Client or web services.
DR: Magstripe txn but no Track1 or Track2 data	An authorisation was received with magnetic strip as the Pan Entry mode but no Track 1 or 2 data was provided.	Always declined	Potential fraud due to card skimming. Contact cardholder to confirm and block card ASAP.
DR: Transaction not permitted to cardholder	The transaction is not permitted to the cardholder for a reason, e.g. calendar group.	Always declined	Check the groups assigned for the exact decline reason.
EH remote server unavailable	The remote server for the EH (External Host) returned an error: (503) Server unavailable.	If stand in ticked, Thredd approves/declines based on product config. If not ticked, it is declined (almost always declined).	Check the External Host for any issues. Contact Thredd.
EH Timeout	EH (External Host) didn't responded in the agreed time (timeout happened).	If stand in ticked, Thredd approves/declines based on product config. If not ticked, it is declined (almost always declined).	Investigate why the External Host did not respond in time. Contact Thredd.
EHI DNS Error	The remote name could not be resolved.	If stand in ticked, Thredd approves/declines based on the product configuration. If not ticked, it is declined (almost always declined).	Investigate why the DNS name could not be resolved. Contact Thredd.
Empty/Invalid response code received from EH	The respond code received by Thredd from the External Host is invalid or absent.	If stand in ticked, Thredd approves/declines based on product config. If not ticked, it is declined (almost always declined).	Investigate why the response code was absent or invalid. Contact Thredd for assistance.
EMV ATC (0x0002) is not higher than last EMV transaction ATC (0x00C4) value	The application transaction counter is lower in this authorisation than it was in the previous.	Always declined	May indicate fraud. Confirm if the cardholder attempted the transaction. If not, block and reorder the card.
Fees	Fees applied to a card.	Shows as presentment line in Smart Client/sent to EHI.	Not applicable
FX Rate Applied : Client FX of [applied FX rate] dated, YY MMM YYYY HH:MM	An FX rate has been applied to this authorisation as provided to Thredd.	FX rate applied on amounts sent by MC. Usually accepted unless there is another reason for decline.	No action required.
GEN: Balance Transfer - Overnight Sweep of funds from Primary Card (123456789) to Secondary (987654321)	Funds transferred automatically overnight from secondary card to primary card.	Funds transferred to primary card.	No action required.
GEN: Multi Wallet Auto Transfer	Funds transferred to a multi-FX wallet automatically.	Transfer to fund wallet during authorisation.	No action required.
Gen: Pre-Authorization Request	A merchant has requested a ‘preauthorisation’. An authorisation for an estimated value.	Depends on other criteria, e.g. limits, EHI etc. Usually Accept.	No action required.
GEN: Secondary Card Balance Transfer	Funds transferred to a secondary card automatically.	Transfer to fund secondary card during authorisation.	No action required.
incorrect track 1 data (wrong cvv1)	The CVV1 in the track 1 data was incorrect.	Always declined	Potential fraud due to card skimming. Contact cardholder to confirm and block card ASAP.
incorrect track 1 data (wrong exp date)	The Expiry Date in the track 1 data was incorrect.	Always declined	Potential fraud due to card skimming. Contact cardholder to confirm and block card ASAP.
incorrect track 1 data (wrong service code)	The Service Code in the track 1 data was incorrect.	Always declined	Potential fraud due to card skimming. Contact cardholder to confirm and block card ASAP.
LSR: Balance transferred from TOKEN 1 To TOKEN 2	Automatic transfer when replacement card ordered. (Only if new card Is regenerated with new PAN etc).	Balance transferred to new card.	No action required.
Neg Reversal due to AFD Advice with different amount. (AFD Amount= )	Reversal received from merchant with negative amount Increasing the blocked amount.	Accepted, increases blocked amount.	No Action required.
No response from EH Authorised by Thredd-Accepted	No response received from the External Host in authorisation process. Thredd STIP (Stand In Processing) has accepted this transaction.	Accepted	Check if the External Host is available, if this issue is affecting a high volume of transactions, raise with Thredd operations with the appropriate priority.
No Response from EH	The External Host did not respond within the configured limit. (May be unavailable).	Always declined. (If stand in is enabled, a different note will appear. (As in row above) .	Check if the External Host is available, if this issue is affecting a high volume of transactions, raise with Thredd operations with the appropriate priority.
Recalculated-BillAmount=	Presentment received for authorisation where FX rate is applied. Billing amount is recalculated based on the FX rate.	Accepted(Presentment)	No action required.
Refund	Shows on a credit for refund financial message.	Accepted as it is a financial message.	No action required.
Reverse Authorisation for Auth on [Transaction date]	Reversal for an authorisation on a specified date.	Reverse authorisation, credit bill amount back to available balance.	No action required.
Reverse Authorisation for Auth on [Transaction date]Partial dispense by ATM (Misdispense) or POS partial reversal	Reversal for an authorisation on a specified date. This is due to an ATM error.	Reverse authorisation, credit bill amount back to available balance.	No action required.
Reverse Authorisation for Auth on [Transaction date] Issuer timeout Auth Reversed	Reversal for an authorisation on a specified date. This is due to an issue timeout.	Authorisation reversed	If volumes are high, contact Thredd.
Reverse Authorisation for Auth on 2017-07-28 13:22:35.703 No confirmation from point of service	Reversal for an authorisation on a specified date.	Authorisation reversed	No action required.
Reverse Authorisation for Auth on [Transaction date] Transaction not completed	Reversal for an authorisation on a specified date.	Authorisation reversed	No action required.
Reverse Authorisation for Auth on [Transaction date] No confirmation from point of service	Reversal for an authorisation on a specified date.	Authorisation reversed	No action required.
Reverse Authorisation for Auth on [Transaction date] Banknet advice: APS error; unable to deliver response	Reversal for an authorisation on a specified date. This is due to a Banknet error preventing the response from reaching the merchant/acquirer.	Authorisation reversed.	If volumes are high, contact Thredd.
Root element is missing.	Incorrect response from the External Host.	Decline unless stand -in is enabled.	Investigate the EHI response for incorrect/missing tags.
System error	An error occurred while processing. Generic error code.	Always decline	If persistent, contact Thredd via Jira.
Visa repeat Message	Thredd has received a Visa Repeat 0101 message.	Authorisation accepted, declined, reversed. (Similar to 0100 message).	If persistent, contact Thredd, however, note this is not a Thredd issue.
DR: cannot find matching Base1 0100 TAR X-REQUEST-ID	The received tokenisation-related message, like TEN (Token Event Notification), is not linked to any TAR (Token Authorisation Request) in our system/TAR, which might have got archived.	Advice message only	No action required.
DR:MDES Thredd Status check failed Gen: Pre-Authorization Request	The underlying DPAN (Device Primary Account Number) status in our system is blocked.	Authorisation is declined	Change the status to All Good to further approve the DPAN transactions.
DR: Decline existing tokens(24) Min_Tokens_To_Decline(15) DR: MDES/VDEP validation failed MDES check failed from Tokenisation Processing	The TAR (Token Authorisation Request) is declined whenever the permitted number of DPAN’s (Device Primary Account Numbers) on a card would exceed if the TAR is approved or the number of assigned DPAN’s on a card is already greater than the permitted values.	TAR is declined	Delete one or more DPAN’s to permit further tokenization on the card. Or increase the number of permitted DPAN’s in Payment token group via change request.
DR: Expiry Date missing	Blank expiry is not permitted in the authorisation as per the usage group config.	Auth is declined	Enable ‘Allow blank expiry date..” flag in the usage group.
DR: MDES Digitisation reference already exists Tokenization request associated with Orange Flow indicator is not permitted	When Thredd receive a TAR (Token Authorisation Request) with a Digitization reference (Correlation ID) which already exist in our database, our system will decline the TAR with reason stating "MDES Digitisation reference already exists MDES check failed from Tokenisation Processing". This is an expected behaviour.	TAR is declined	No action required.
Tokenization request associated with Orange Flow indicator is not permitted	TAR (Token Authorisation Request) was declined by Thredd because of the Orange flow indicator in the request based on the configuration.	TAR is declined	If the TAR needs to be challenged instead of decline, raise a change request to change this config in the Payment Token Usage Wallet.
DR: Decline due to missing CVV2DR: MDES/VDEP validation failed MDES check failed from Tokenisation Processing	TAR (Token Authorisation Request) was declined due to CVV missing in the request. The decline was as per the Card usage group.	TAR is declined	No action required.
DR: Wallet Provider Not Configured: ANDROID not in PAYMENT_TOKEN_USAGE_WALLET for payment_token_usage_id=119 MDES check failed from Tokenisation Processing	TAR (Token Authorisation Request) was declined because GooglePay/Android is not added to the Payment Token usage wallet group.	TAR is declined	Can add GooglePay/Android to the payment token usage group wallet via a change request. Similar declines could arise for Apple wallet as well if the respective wallet is not added to it.
DR: Decline as wallet recommended decline	In the TAR (Token Authorisation Request), the wallet recommendation was to decline the request. As per the Payment token config decision, Thredd declined TAR.	TAR is declined	No action required.
DR:MDES Decline - Wallet disabled for tokenisation MDES check failed from Tokenisation Processing	If the Default Decision when a TAR (Token Authorisation Request) is received from a particular wallet is set to “Decline”, this is when this error is returned.	TAR is declined	No action required.
DR: Invalid Wallet Provider: token_requestor_id=40010071298 not in Payment_token_requestor_map	if the Token RequestorID is not added to the Payment_token_requestor_map table at Thredd’s end, the TAR (Token Authorisation Request) will be declined.	TAR is declined	No action required.
DR:VDEP new DPAN received on unknown payment-token (no TAR)	This error is returned in the Notes field when we receive an Auth advice TEN (Token Event Notification) or Authorisation in which the DPAN (Device Primary Account Number) received is not found anywhere in the Thredd Database.		No action required.
DR: Decline as wallet_account_score (1) = wallet_account_max_score_decline(1) DR: MDES/VDEP validation failed MDES check failed from Tokenisation Processing	If the Device score or wallet score received in the TAR (Token Authorisation Request) is equal to or less than the value configured in that field, then TAR would be declined.	TAR is declined	No action required.
DR: IAV:V (checked by MC-PREVAL) Declined by Thredd	Authorisation was declined based on the On-behalf service result (DE48.71.05). An on-behalf service is one offered by the scheme where the issuer can optionally participate, e.g., Cryptogram validation service, Mastercard AAV Checks etc. For more details, refer to Mastercard's Customer Interface Specification.	Authorisation is declined	No action required.
DR: Requires SCA	Based on the Product’s SCA configuration, the authorisation was declined due to additional authentication required/No SCA exemption is applicable/ transaction performed against SCA guidelines like PAN manual entry where the cardholder is present etc.	Authorisation is declined	No action required.
PSD2 Counter Reset …	Either the transaction went was authenticated using PIN or 3DS which reset the SCA counters.	This is just an informational message and is not a reason of decline.	No action required.
Unable to locate bound device 0 …	The device ID in the transaction is not found anywhere in the DB.	This is just an informational message and is not a reason of decline.	No action required.
Refund matching credit auth	When a refund presentment is matched to its respective Refund Auth.	Informational message	No action required.
Declined by Fraud Advantage Gen: Pre-Authorization Request Declined by Thredd	When the Authorisation is declined by the Featurespace/Fraud Advantage service.	Authorisation is declined	No action required.
DR: MDES Invalid Card Number - payment_token not found Declined by Thredd	When we receive a payment token transaction from a DPAN (Device Primary Account Number) which is not assigned on that card, the above error is returned.	Authorisation is declined	No action required.
DR: Invalid Country Declined by Thredd	The country from which the authorisation originated is blocked by Thredd on that product/scheme.	Authorisation is declined	No action required.
DR: Japan-Restricted Payment mode	When F118 is received, Thredd will only approve transactions with F118.8 = 10 (one-time payment) and decline everything with note: 'DR: Japan-Restricted Payment mode' that has a value different to 10. The F118 field is used in Japan (as well as other specific countries) by acquirers to share payment modes.	Authorisation is declined	No action required.

Accepted by EHI

Authorisation accepted by the external host.

Accepted

No action required.

Accepted by EHI Gen: Pre-Authorization Request

Pre-authorisation request accepted by the external host.

Accepted

No action required.

Accepted by EHI ASI card

ASI (Account Status Enquiry) authorisation accepted by the external host.

Accepted

No action required.

Accepted with load via EHI

Authorisation accepted by the external host with load.

Accepted

No action required.

ASI.... AVS check ASI card

Account Status Enquiry – Address verification system.

Usually accepted

No action required.

ASI.... CVC check ASI card

Account Status Enquiry – CVC (Card verification Code) check.

Usually accepted

No action required.

Auth Reversed on [Transaction Date]

The authorisation was reversed on a particular date.

Nothing changes on this transaction line.

Find reversal on the mentioned date and see notes field.

AUTOMATIC AUTHORISATION REMOVAL BillAmt – [Billed amount] Location – [transaction Location]

Authorisation has been reversed. Usually this note refers to the hanging authorisation filter.

Credits bill amount to available balance.

No action required.

BLACKLIST

This merchant (card acceptor id) is not allowed as per the card acceptor blacklist assigned to the card.

Always declined

Remove Card acceptor id from the blacklist via Smart Client or web services.

C01 - Person-to-Person

Type of credit authorisation that is person to person. These values are received in DE48 subelement 77 known as Transaction Type Identifier. Note that the values are discontinued.

Accepted or declined based on usage group rules.

Check usage group Rules.

C04 - Gaming Re-pay

Type of credit authorisation for gaming and gambling. These values are received in DE48 subelement 77 known as Transaction Type Identifier. For more details, refer to Mastercard's Customer Interface Specification.

Accepted or declined based on usage group rules.

Check usage group Rules.

CardRequest.XML load by

Card Load performed by CRI file.

Accepted Load

No action required.

CB:Charged Back on CBC: Chargeback Credit confirmed on

This shows when a presentment is charged back.

Either an accepted Chargeback or rejection.

Check the Chargeback screen to show all Chargeback information.

Declined by Ext Auth

The authorisation was declined by the external host operating external authorisation.

Always declined

Check external host for decline reason.

Declined by EHI

The external host has declined the authorisation.

Always declined

Check decline reason on External Host.

DR: AF:Mag ATM attempt

Magnetic stripe used at an ATM. The hard-coded block is still applied to this product.

Always declined

To remove block, gain issuer sign off and raise a change request with Thredd via Jira.

DR: ARQC not matching

The ARQC (Authorization ReQuest Cryptogram) generated by the card does not equal the ARQC generated by Thredd.

Always declined

This can be due to issue with the Card manufacturer, network, Thredd, Terminal etc. If this is a recurring issue, please raise to Thredd.

DR: Auth Amount

The card does not have enough available funds for the authorisation.

Usually declined, unless the external Host overwrites and accepts the authorisation.

Load the card with the required amount. If enough Available funds please check the value of fees applied etc.

DR: Auth Amount

Total :

Available Amount : ==> Decline! Declined by Thredd Accepted with load by EHI

Authorisation declined by Thredd but accepted with load by EHI.

Accepted

No action required.

DR: AVS Failed because of: Address not Matching

Address verification system failure. The address sent to Thredd in the authorisation message does not match the address details held.

Usually declined. Thredd can configure to accept if AVS is wrong.

Ensure the cardholder is using the address registered in the ‘Cardholder details’ held under the card details on Smart Client.

DR: AVS Failed because of: House No not Matching

Address verification system failure. The house number of the address sent to Thredd in the authorisation message does not match the details held by Thredd.

Usually declined. Thredd can configure to accept if AVS is wrong.

Ensure the cardholder is using the address registered in the ‘Cardholder details’ held under the card details on Smart Client.

DR: Bad Retailer

This retailer has been blocked via the merchant blacklist.

Always declined

Merchant has been blocked for fraudulent behaviour. Contact Thredd for details.

DR: Card expiry check failed with Emboss Expiry date (DE014)

The expiry date sent to Thredd in the authorisation message does not match the expiry date held by Thredd (This is the embossed expiry of the card),

Always declined

Advise the cardholder to use embossed Expiry. If issue persists there could be an expiry misalignment, if so raise a Jira for Thredd Operations.

DR: Card Service Code check failed, Txn MSR Track 2 service code=xxx but Thredd service code=xxx Declined by Thredd

The service code in the track 2 data of the authorisation message does not match the service code held by Thredd.

Always declined

Validate transaction with cardholder as this can indicate a fraudulent card transaction attempt involving card skimming. If persists and is a valid transaction contact Thredd/merchant.

DR: Card usage group check…. Card Acceptance Method (A) - (Rule causing decline specified)

The POS (Point of Sale) entry mode used (DE22) is not allowed as per the card usage group assigned to the card.

Always declined

Change the usage group assigned to the card, gain issuer sign off and raise a change request to allow this Entry mode or tell the cardholder to use a different POS Entry mode.

DR: Card usage group check…. Transaction type (T)

The transaction type (processing code) is not allowed as per the card usage group assigned to the card.

Always declined

Change the usage group assigned to the card, gain issuer sign off and raise a change request to allow this transaction type.

DR: CAVV incorrect (checked by

The cardholder Authentication Verification Value was incorrect.

Always declined

Potential attempted Fraud as incorrect authentication value has been passed.

DR: CVC1 does not match

The CVC1 sent to Thredd Does not match what we hold.

Always declined

Potential fraud due to card skimming. Contact cardholder to confirm.

DR: Declined due to Expired card

The card is expired.

Always declined

Check if the card expired correctly as per the configuration detailed on the Product Set up Form.

DR: Declined due to Card Destroyed (Original status 83, changed to 05)

Card status is set to 83 -destroyed.

Always declined

Order new card Via WS_Regenerate.

DR: Declined due to Do not honour

Card Status is set to 05 - to do not honour.

Always declined

Change status to 00 – All good or order new card.

DR: Declined due to Do not honour Declined by Thredd (EHI sent decline notification)

Card Status is set to 05 - to do not honour.

Always declined

Change status to 00 – All good or order new card.

DR: Declined due to GroupMCCCheck

The MCC (Merchant Category Code) passed in this authorisation is not allowed as per the MCC group assigned to the card.

Always declined

Remove this MCC from the MCC group or advise the cardholder to use a merchant with a different MCC.

DR: Declined due to Invalid card number (no such number) card not found

The Card number (PAN) passed in DE 2 is not recognized by Thredd.

Always declined

Either an accidental entry by the cardholder or attempted Fraud. No action required.

DR: Declined due to Limited network Check

This merchant is not included in the limited network assigned to the card.

Always declined

Advise the the cardholder to use the card within the allowed limited network.

DR: Declined due to Lost Card (Capture)(Original auth resp status 41, changed to 05)

Card Status is set to 41 – Lost card.

Always declined

Order new card via Webservices. (WS_regenerate)

DR: Declined due to Restricted card (Card is not active)

This card has not been activated.

Always declined

Activate card via Smart Client, Webservices or phone/IVR line, (Activation methods available depend on the product set up).

DR: Declined due to technical fallback transactions

The transaction declines due to the phasing out of the magstripes.

Always declined

Advise the cardholder to use the chip/contactless.

DR: Declined due to voided card (Original auth resp status 99, changed to 05)

Card Status is set to 99 – Voided card.

Always declined

Change status to 00 – All good or order a new card.

DR: Emboss CVC2 not matching with CVC2 on PDS92

The CVC2 sent to Thredd in the authorisation message does not match the CVC2 held by Thredd.

Usually declined. Can be configured to accept for VISA if no CVC2 is provided.

Advise the cardholder to use embossed Expiry. If issue persists there could be an expiry misalignment, if so raise a Jira for Thredd Operations.

DR: Exceeds Max Per Transaction limit

The authorisation value (bill amount) is higher than the maximum per transaction limit in the Limit group assigned to the card.

Always Decline

Upgrade Card to a different Limit group, or wait until the limit group allows this to be completed (time dependent on the configuration.)

DR: Exceeds withdrawal amount limit

This authorisation would exceed the daily withdrawal limit as per the Limit group assigned to the card.

Always declined