Skip to main content

Mastercard 4812 - Account Number Not on File

Overview​

Used when a transaction was processed on an account number that was never valid, was closed, or does not exist in the issuer's system.

When This Code Applies​

  • Account number was never valid
  • Account was closed before transaction
  • Card number does not exist in issuer records
  • Keyed number with digit errors
  • Test card number used in production

Conditions for Valid Chargeback​

Issuer Must Verify​

  1. Account number is not on file
  2. Account was not valid at transaction time
  3. Transaction was processed to invalid account

Common Scenarios​

ScenarioDescription
Closed accountCard cancelled, account terminated
Never issuedNumber never assigned to cardholder
Digit transpositionKeyed entry error
Test cardSandbox card used in production

Time Frames​

RegionChargeback Window
Standard90 calendar days from settlement
ATM/Maestro Europe120 calendar days

Representment Options​

Limited options for invalid account:

1. Account Was Valid at Transaction Time​

Evidence required:

  • Authorization approval code
  • Auth was obtained successfully
  • Account active at auth time

2. Cardholder Used This Account​

Evidence required:

  • Cardholder correspondence
  • Prior transactions on same account
  • Account matched cardholder identity

3. Processing Error (Acquirer Side)​

Evidence required:

  • Account number was correct
  • Error occurred in transmission
  • Processor confirmation

Why This Happens​

Common Causes​

  1. Manual entry error - Wrong digits keyed
  2. Account closure - Card cancelled between auth and clearing
  3. System glitch - Data corruption
  4. Test in production - Test card accidentally used
  5. Fraud - Fabricated or stolen number

Prevention Strategies​

Terminal/System Configuration​

  1. Luhn validation - Check digit algorithm
  2. BIN validation - Verify valid issuer range
  3. Real-time auth - Always authorize online
  4. Production vs test - Separate environments

Manual Entry Controls​

  1. Double-entry - Verify card number
  2. Read-back - Confirm with customer
  3. Chip/swipe first - Avoid keying when possible
  4. Limit manual entry - Reduce keyed transactions

Processing Controls​

  1. Auth-capture matching - Same number both times
  2. Data validation - Check format before submit
  3. Error handling - Flag malformed numbers
  4. Test card blocking - Reject test BINs

Win Rate Expectations​

ScenarioExpected Win Rate
Account was valid (auth obtained)70-85%
Processing error proven50-70%
Account never validUnder 10%

Common Mistakes​

  1. Manual keying errors - Transposed digits
  2. No Luhn check - Invalid check digit accepted
  3. Test cards in production - Environment confusion
  4. Delayed clearing - Account closed after auth
  • 4807 - Warning Bulletin
  • 4808 - Authorization-Related
  • 4837 - No Cardholder Authorization

See Also​