Library · Chargebacks · Guide
Soft vs hard descriptor — claim map
GuideSoft vs hard descriptor — claim mapBack to article
Soft ≠ cosmetic. Hard often needs processor approval. Both remap alerts. Distinct from the re-enroll checklist.
| Claim | Reality | Get in writing | Do not |
|---|---|---|---|
| Soft descriptor is cosmetic — no remap | No. Soft still changes what the cardholder may see | Whether soft edits hit clearing / statement here | Skip Ethoca / CDRN / OI after a soft edit |
| Hard DBA can be renamed in the gateway alone | Usually no. Hard is boarded identity — processor path common | Who approves a hard descriptor change on this MID | Invent a hard DBA without asking |
| Only hard changes force same-day re-enroll | No. Soft and hard both stale alert maps | N/A — open re-enroll checklist either way | Wait for unrecognized CBs to prove the hole |
| Updating Order Insight covers soft changes | No. Alerts and RDR that key the old string are still holes | Ethoca, CDRN, RDR, and OI after any string change | OI-only updates |
| This map is the re-enroll checklist | No. Re-enroll ticks the seats. This map is soft vs hard myths | N/A — open descriptor-reenroll to tick seats | Skip the sheet because you named soft vs hard |
| Billing-descriptor page already covers this fork | No. Billing-descriptor is what the line should say. This map is change mechanics | N/A — open billing-descriptor for the statement line | Confuse “what to print” with “soft vs hard change” |
Filter the claim. Soft and hard are how the string is set. Both can change the statement. Remap alerts either way. Hard often needs processor approval.
Pairing procedure: Soft descriptor change still remaps alerts. Topic: Chargebacks.
Work with us — We run this job on your accounts. Services