Skip to content

Dispute w/ Core Processor Over Transaction

Answered by: 

Question: 
We received notice from our core processor that we will be charged for a debit card transaction that is not our customer, the card is not on us and the merchant is not a customer. We are disputing this with our core processor but they say we will be charged for the transaction. Why can this transaction not be returned when it wasn't on us? I have no idea how it reached our core processor and was processed for our bank.
Answer: 

Debit card transactions are routed based on BIN which is usually the first six digits of a card number. If a merchant either miskeyed an account number or intentionally forced a transaction through on an invalid card number that has your BIN, then the transaction will be routed to you.

If the merchant failed to obtain a valid authorization as required by VISA/MC rules, then you should have chargeback rights to send the transaction back to the merchant. Exceptions to this would be if the communication network was down at the time of the transaction and the merchant used a "stand in" authorization or the dollar amount is below the minimum chargeback threshold.

First published on 04/12/2020

Filed under: 
Filed under compliance as: 

Banker Store View All

From training, policies, forms, and publications, to office products and occasional gifts, it’s available here:

Banker Store

hot right now

image description

Looking for effective, convenient training on a particular subject?

BOL Learning Connect offers more than 200 courses ON-DEMAND or on CD ROM from AML to Reg Z and every topic in between.

Search Topics