Mastercard Payment Decline Code
Mastercard Decline Code 76: Invalid or Nonexistent To Account
Category Invalid Payment DataRetry Guidance Conditional Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026
What Mastercard Decline Code 76 Means
Mastercard decline code 76 (Invalid or Nonexistent To Account) indicates that the destination account specified for the transaction is invalid or does not exist. It is returned during authorization to tell the merchant the payment could not be approved as submitted.
Where the Response May Come From
Mastercard code 76 (Invalid or Nonexistent To Account) is returned by the card issuer during authorization and signals that the destination account referenced by the transfer is invalid or does not exist. Issuers rarely disclose the precise internal cause, so treat it as a directional signal rather than a full explanation.
Common Reasons for This Response
Common causes include an incorrect account reference, or a transfer target the issuer cannot locate. The exact trigger depends on the issuer, the account, and how the transaction was submitted, so the same code can appear in several different situations.
Should the Merchant Retry the Payment?
Whether a retry helps depends entirely on the fact that the destination account referenced by the transfer is invalid or does not exist; retry only once that condition is genuinely resolved, and avoid immediate repeat attempts that conflict with network retry expectations.
Recommended Merchant Action
Confirm the cause first, since the destination account referenced by the transfer is invalid or does not exist, then verify the destination account details entered, and ask the customer to contact their issuing bank if the response points to their account.
What to Tell the Customer
Let the customer know the payment did not go through because the destination account referenced by the transfer is invalid or does not exist, and suggest confirming the destination account or trying another method. Keep the wording neutral and avoid asserting issuer details you cannot confirm.
How to Reduce Similar Payment Failures
Segmenting how often the destination account referenced by the transfer is invalid or does not exist appears by issuer and BIN, validating destination account references before submission, and submitting clean, correctly formatted authorization data can reduce avoidable occurrences of this decline over time.
Important Limitations
Decline-code meanings vary by processor, gateway, and payment environment, and issuers do not always disclose the specific reason behind a response. The retry classification on this page is Payment Defender editorial guidance, not an official Mastercard rule. Merchants should confirm handling with their processor or gateway.
Related Decline Codes
Sources and Review Information
- PayPal (Braintree): Braintree Processor Response Codes
- Mastercard: Mastercard Rules and Merchant Support
Last reviewed July 17, 2026
Raw network-response codes are supplemental to the complete processor or gateway response. Meanings and recommended actions can vary by issuer, processor, gateway, card network, payment method, region, and merchant configuration.