4 ms·

Allowing longer description lengths would be a huge improvement! Most chargebacks we see are "didn't recognize transaction", then we explain what the charge was

Allowing longer description lengths would be a huge improvement! Most chargebacks we see are "didn't recognize transaction", then we explain what the charge was for, and have to go through the chargeback cancellation process (which is a whole ordeal in itself). On that note... Why can't customers cancel a chargeback as easily as they can create one? The whole system is a UX nightmare for all parties involved.

protomyth 4y ago
I wonder how much changing the field size of the description would cost and what most banks would estimate the timeline would be?
- Someone1234 4y ago
  It would be quite expensive to be honest. The best way to do it would be to leave the short description and add an additional large description, therefore those on legacy mainframes can just continue to work until they've able to conduct a spec update and those on modern systems can add it immediately. Still will cost money though, particularly those paying EDI/VAN data-rates.
KennyBlanken 4y ago
Longer description lengths wouldn't change the fact that a lot of merchants use names that are unrecognizable because they're a corporate name, not the common name of the business. Instead of Bob's Bagel Company, it's 1132 Fifth LLC, and only after a bunch of googling do you happen to hit upon a corporate database and discover the LLC is for a restaurant. Merchants shouldn't even be allowed to set this field. It should be set by their merchant bank, and the bank should require that the name on a reader at a business location match the common name of the business, followed by their address or store number if it's a chain, and zipcode. Ideally the business phone number as well. Or there should be a merchant ID, cross-referenceable against a publicly database maintained by credit card companies.
- dazbradbury 4y ago
  A merchant ID in a separate "more info" field makes sense. But not to replace the description. The description should not only convey where the purchase was made, but also what product was purchased (ideally in enough detail). Only the merchant knows that information and so it's right that it's set by the merchant.

protomyth 4y ago

I wonder how much changing the field size of the description would cost and what most banks would estimate the timeline would be?

Someone1234 4y ago
It would be quite expensive to be honest. The best way to do it would be to leave the short description and add an additional large description, therefore those on legacy mainframes can just continue to work until they've able to conduct a spec update and those on modern systems can add it immediately. Still will cost money though, particularly those paying EDI/VAN data-rates.

KennyBlanken 4y ago

Longer description lengths wouldn't change the fact that a lot of merchants use names that are unrecognizable because they're a corporate name, not the common name of the business. Instead of Bob's Bagel Company, it's 1132 Fifth LLC, and only after a bunch of googling do you happen to hit upon a corporate database and discover the LLC is for a restaurant. Merchants shouldn't even be allowed to set this field. It should be set by their merchant bank, and the bank should require that the name on a reader at a business location match the common name of the business, followed by their address or store number if it's a chain, and zipcode. Ideally the business phone number as well. Or there should be a merchant ID, cross-referenceable against a publicly database maintained by credit card companies.

dazbradbury 4y ago
A merchant ID in a separate "more info" field makes sense. But not to replace the description. The description should not only convey where the purchase was made, but also what product was purchased (ideally in enough detail). Only the merchant knows that information and so it's right that it's set by the merchant.