Mastercard Payment Decline Code

Mastercard Decline Code 77: Invalid or Nonexistent From 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 77 Means

Mastercard decline code 77 (Invalid or Nonexistent From Account) indicates that the source 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 77 (Invalid or Nonexistent From Account) is returned by the card issuer during authorization and signals that the source 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 funding account 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 source 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 source account referenced by the transfer is invalid or does not exist, then verify the source 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 source account referenced by the transfer is invalid or does not exist, and suggest confirming the funding 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 source account referenced by the transfer is invalid or does not exist appears by issuer and BIN, validating source 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

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.

Turn the Code Into Action

Know What to Do Next

Payment Defender helps merchants connect reason codes to transaction history, dispute alerts, refunds, evidence, fraud activity, VAMP exposure, and payment-performance decisions.