Home / Fraud Library / Identity Tools / Mastercard Identity Check (SecureCode)
Identity Tools

Mastercard Identity Check (formerly SecureCode)

Payment Verification ~6 min read The Fraud Practice Library

Mastercard Identity Check, formerly Mastercard SecureCode, is Mastercard's version of 3-D Secure. It checks that the person paying online is the authorized cardholder and, in exchange, gives merchants liability protection on the fraud chargebacks it covers. It applies to Mastercard credit and debit (Maestro) transactions.

What changed: from SecureCode to Identity Check

SecureCode was the Mastercard-branded version of the original 3-D Secure 1.0, with its password pop-up. Mastercard has since renamed it Identity Check and moved it to EMV 3-D Secure (3DS 2.0), which lets the issuer assess each payment on far more data and approve most low-risk ones without any prompt. Riskier payments are challenged with a one-time passcode, a banking-app approval or a biometric such as a selfie. Visa and Mastercard both retired support for 3DS 1.0 in October 2022, and the SecureCode name now survives mostly in search and in older documentation.

The liability rules, reason codes and decision logic below still apply. Details differ by region and acquirer, so confirm current rules with yours.

How it works

  • The consumer goes through checkout normally and enters the same fields as always.
  • The merchant's authentication software sends an enrollment check to Mastercard and the card issuer.
  • The issuer decides whether to approve silently or challenge. In the classic flow, an enrolled consumer saw a pop-up that appeared to come from their issuing bank.
  • If challenged, the consumer enters a password, PIN, one-time passcode or approves in the banking app.
  • The issuer validates the response and returns the result to the merchant.

Depending on the issuer and country mandates, two-factor authentication or a one-time password may be required instead of a static password.

What implementation requires

  • E-commerce only. Mail and telephone orders (MOTO) need separate fraud processes.
  • Everyone has to participate. The merchant, consumer, issuer and acquiring bank all take part. Make sure your acquirer supports the e-commerce indicator and ask about its certification requirements.
  • Send the right data. Mark the order as e-commerce with the ECI, check AVS and enrollment, and capture the authentication value (CAVV/AAV) and the XID transaction identifier.
  • Certification. In the classic setup you obtained a digital certificate from Mastercard, which took about two weeks through your acquirer. Today most merchants get this through their gateway or processor.
  • Keep your other checks. It does not replace them. Many card types are not covered, and some legitimate customers cannot complete authentication.
  • Low-volume merchants should consider an outsourced service bureau.

What's actually covered

Transactions authenticated through Mastercard's program shift fraud chargeback liability from the merchant to the issuer. In the United States, coverage was expanded in October 2011 to include attempted authentications where the cardholder is not enrolled, but only for U.S. domestic transactions (a U.S. merchant and a U.S.-issued card). Outside the U.S., only successfully authenticated transactions get the shift.

Only specific chargeback reason codes are covered: 4837 (No Cardholder Authorization) and 4863 (Cardholder Does Not Recognize / Potential Fraud). Nothing else shifts.

The exclusions match the other 3-D Secure programs under the original rules: procurement cards, recurring billing, split shipments or back-ordered goods, and "one-click" sales, plus higher-risk verticals such as adult content and gaming. There are significant differences between what is covered in the U.S. and in Europe, so check the current rules with your acquirer.

Country mandates also apply. In Europe, merchants that want to accept Maestro debit online have to support the program, and in Singapore 3-D Secure implementations must use a dynamic one-time password.

How to use the results

  • Enrolled and authenticated, covered order type: accept the order.
  • Not enrolled, covered order type, enrollment was checked, and the order looks normal for you: accept the order.
  • Not enrolled, enrollment was checked, but the order does not look normal: review it or run further fraud checks, favoring sales conversion.
  • Enrolled but could not authenticate, and the order looks normal: run other fraud screening or manually review it, favoring risk aversion.
  • Not a covered order type: use your traditional checks.

Limits and edge cases

  • Legitimate customers fail authentication. Pop-up blockers, timeouts and forgotten passwords all cause good customers to fail. A failed authentication is not proof of fraud.
  • The shift is not a guarantee. Treat it as one control among several, not your only one.
  • It simplifies disputes. When the cardholder authenticated, the dispute plays out between the issuer and the cardholder rather than between you and your customer.

Key notes

  • Alternatives: Visa Secure (formerly Verified by Visa), American Express SafeKey and J/Secure by JCB, which work in similar ways. Most gateways offer them together.
  • Building in-house: not practical. Use a gateway, processor or authentication provider.
  • Cost: available as an outsourced service or software. Expect per-transaction or annual fees plus changes to your checkout engine.

Related reading: Consumer Authentication, Identity Check app with selfie authentication, and Identity Check app rollout.

Not sure where 3-D Secure fits in your fraud strategy? Talk to a senior consultant: no junior hand-offs and no vendor pitch, just a vendor-neutral read on where you actually stand. See our consulting services.