Skip to article
ecomservices.io
Chargebacks · How to run this
MatchingNot on this page yetPricingCalculatorIntakeCalculatorReason codesCalculatorRepresentmentCalculatorThresholdsCalculatorAllocationCalculatorOptimisationCalculatorPrevention stackCalculatorProviders

Library · Chargebacks · How to run this

Soft descriptor change still remaps alerts

How to run thisChargebacks4 steps
GuideSoft vs hard descriptor — claim map · Calculator lives in the articleOpen

Soft and hard descriptor changes are different mechanics, not different cardholder outcomes. Soft is often a dynamic string on the gateway. Hard is the boarded / clearing identity on the MID. Either can make Ethoca, CDRN, RDR, and Order Insight stale. The same-day remap list sits on descriptor re-enroll. This page filters myths about which change “counts.”

Pair: Soft vs hard descriptor — claim map on Chargebacks. How the statement should read: billing descriptor.

How to tell them apart

Soft. Gateway or platform field — product name, phone, URL fragment. Often editable without a full reboard. Still remaps alerts.

Hard. Legal / boarded DBA on the MID file. Processor approval common. Same-day remap still required after it clears.

What not to do

Do not call soft “cosmetic.” Do not skip remap because only the soft string moved. Do not invent a hard DBA without the processor. Do not confuse this with the re-enroll checklist itself.

Related: Chargebacks, descriptor re-enroll, billing descriptor, prevention stack.

Procedure

  1. Name whether the change is soft or hard.
  2. Get hard-change approval path in writing if needed.
  3. Same-day remap on the re-enroll sheet either way.
  4. Confirm a test auth matches the new string.

Failure modes

  • Calling soft cosmetic and skipping remap.
  • Renaming hard DBA without processor approval.
  • OI-only updates after a string change.
  • Waiting for unrecognized CBs to prove the hole.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

Soft vs hard descriptor
Soft is often a gateway/dynamic statement string. Hard is boarded / clearing identity. Both can change what the cardholder sees.

Work with us — We run this job on your accounts. Services

FAQ

What’s the difference between soft and hard descriptor?
Soft is often a gateway/dynamic string on the auth. Hard is the boarded / clearing identity. Both can change what the statement shows.
Does soft change skip alert re-enroll?
No. Remap the same day — [descriptor re-enroll](/manuals/descriptor-reenroll).
Can I invent a new hard DBA without asking the processor?
Usually no. Hard changes often need underwriting / board update. Get it in writing.