Mastercard Test Data

Sandbox-only Mastercard cases for AVS/CVV checks and EMS risk testing.

Use these Mastercard test values in PCE to simulate approvals, declines, AVS/CVV outcomes, and Enhanced Merchant Screening (EMS) risk responses. This page helps QA and developers validate user messaging, fraud rules, and retry flows without touching real cards.

Prerequisites

  • Sandbox account, a test gateway enabled, and logging of payment responses (risk fields).

Limitations

  • Test PANs work only in sandbox; AVS/CVV/EMS behavior can vary by gateway. Amount caps below are maximums for a scenario. Do not store PANs outside approved tools.

AVS & CVV/CSC

Use this data effectively. For more information on AVS and CVV/CSC, visit our dedicated documentation.

  1. Map each scenario to your flow: AVS fail, CVV fail, delays, partials, timeouts.
  2. Verify EMS risk handling (scores, reason codes, approval overrides).
  3. Test fallback behavior when EMV is missing or a timeout occurs.
  4. Confirm decline copy and retry paths are precise and actionable in your UI.

The AVS & CVV response signals appear in the risk object of payment responses:

"risk": {
  "cvvResponseCode": "Y",
  "cvvResponse": "Match",
  "cvvMatch": true,
  "avsResponseCode": "Y",
  "avsAddressMatch": true,
  "avsZipMatch": true,
  "avsAccountNameMatchPerformed": false
}

Mastercard AVS & CVV + EMS Scenarios (Sandbox)

EMS simulates risk scoring or fraud evaluation so you can validate fraud rules, alerting, and review queues. Legend: AVS/CVV — M = Match, N = No match. Approved % is the expected approval rate within the amount range. EMS status shows whether EMS is active and, when provided, the (score / reason) tuple.

Card numberAVSCVVMax amountApproved %EMS status
5100 0000 0000 0123MM$30100%True (40 / 2)
5100 0000 0000 0131MN$110100%True (120 / 2)
5100 0000 0000 0149NM$290100%True (300 / 2)
5100 0000 0000 0156NN$360100%True (370 / 2)
5211 1111 1113 1438MM$29050%None

Notes

  • Submit amounts ≤ Max amount to trigger the listed outcome. Higher amounts may produce different responses.
  • When EMS is shown as True, your integration should record the score and reason for audit/testing.
  • Always assert on both transport-level success and business-level approval/risk fields.

Issuer Response Codes for Mastercard

This is a brief list of Issuer Response Codes for Mastercard. For the full list, please download this file.

Card numberIssuer response codeAuth messageStatus
51000000000500030Approved or completed successfullyApproved
51000000000500111Refer to card issuerDeclined
51000000000500292Do not honorDeclined
51000000000500373Invalid merchantDeclined
51000000000500454Capture cardDeclined
51000000000500525Do not honorDeclined
51000000000500606Response TimedoutDeclined
51000000000500787Do not honorDeclined
51000000000500868Honor with IDApproved
51000000000500949Do not honorDeclined
510000000005010210Partial ApprovalApproved
510000000005012812Invalid transactionDeclined
510000000005013613Invalid amountDeclined
510000000005014414Invalid card numberDeclined
510000000005015115Invalid issuerDeclined
510000000005019319Do not honorDeclined
510000000005028428Do not honorDeclined
510000000005030030Format errorDeclined
510000000005041741Lost cardDeclined
510000000005043343Stolen cardDeclined
510000000005051651Insufficient funds/over credit limitDeclined
510000000005054054Expired cardDeclined
510000000005057357Transaction not permitted to issuer/cardholderDeclined
510000000005058158Transaction not permitted to acquirer/terminalDeclined
510000000005061561Exceeds withdrawal amount limitDeclined
510000000005062362Restricted cardDeclined
510000000005063163Security violationDeclined
510000000005065665Exceeds withdrawal count limitDeclined
510000000005075575Allowable number of PIN tries exceededDeclined
510000000005091291Authorization Platform or issuer system inoperativeDeclined
510000000005092092Unable to route transactionDeclined
510000000005093893Do not honorDeclined
510000000005096196System errorDeclined


© 2025 Priority Technology Holdings LLC. All rights reserved.