What Mastercard SecureCode is
Mastercard SecureCode was an online authentication service for card-not-present purchases. A shopper entered a personal code during checkout, and the card issuer checked the shopper's identity before the transaction proceeded.
The service was part of the earlier 3-D Secure 1.0 experience. Mastercard SecureCode is not an interchange category or a named network fee, so it does not add a defined charge to your processing statement.
SecureCode authentication is evidence of an identity check, not a guarantee against fraud or chargebacks.
How the code-based flow worked
A cardholder enrolled through their bank and used the resulting code at participating online stores. The issuer handled the identity check, and the merchant did not see the shopper's code. For your checkout, that meant an extra step controlled by the issuer rather than a password your staff collected.
Merchants connected the authentication through a compliant software component on their server or a hosted service. This older flow is associated with 3-D Secure 1.0. The broader 3-D Secure term also covers later versions, so an integration guide that says SecureCode does not, by itself, tell you which version a live checkout supports.
What it means for fraud and disputes
Issuer authentication gives you evidence that the cardholder completed an identity check. Mastercard described SecureCode as a way to reduce online fraud and disputed purchases, but that description is not a guarantee that a transaction is legitimate or that every chargeback will be covered.
Do not treat the SecureCode name alone as proof of chargeback liability protection. Authentication outcomes and dispute protections depend on the transaction and applicable network rules. If an older integration or report uses the name, confirm which authentication version was used and retain the resulting transaction records.
What you can actually change
You cannot change the issuer's identity check or negotiate a SecureCode rate. You can make sure your current online checkout uses a supported authentication flow and that your team understands what the transaction records establish.
- Ask your technical team whether any checkout still uses the legacy SecureCode code-entry flow or a later 3-D Secure version.
- Review authentication results alongside the transaction record when responding to an online card dispute.
- Compare your processing statement for actual fee line items, rather than assuming SecureCode has its own charge.
- Keep customer-facing checkout instructions clear about when an issuer will request an additional identity check.
- Map your checkout. Document the authentication version used by each online checkout and note any older SecureCode references in technical materials.
- Check dispute records. Make sure your response process captures authentication results together with the order and transaction details.
- Audit fee lines. Review itemized statement charges before attributing any processing cost to an authentication product.
Frequently asked questions
Is Mastercard SecureCode the same as 3-D Secure?
SecureCode refers to Mastercard's legacy code-based 3-D Secure 1.0 experience. 3-D Secure is the broader authentication standard, which also includes later versions and different checkout flows.
Does Mastercard SecureCode add a processing fee?
SecureCode is an authentication service, not an interchange category or a named network fee. The available product information does not specify a fee amount, so look for an actual itemized charge before linking a statement cost to it.
Does SecureCode prevent chargebacks?
No authentication method guarantees that every purchase is legitimate or that every dispute will be covered. SecureCode was intended to help reduce online fraud and disputes, but the name alone does not establish liability protection for a specific transaction.