Library · MIDs · How to run this
Put the DBA on the statement, not the LLC
The statement is the first time a cardholder sees you after checkout. If that line is a legal entity they never met, they call the bank. That call is an unrecognized chargeback. This page is what the line must say. It is not the alert-seat enrollment job, and it is not the Order Insight payload job.
Pair: Statement descriptor checklist on MIDs. Phone / URL on that line: descriptor phone / URL. Alert seats that no longer match the line are a different job: Map prevention holes on a MID. Returning the name on a Visa inquiry is a different job: Order Insight inquiries.
Soft line vs hard name
Soft line. The short string on the card statement. City or a phone often sit next to it. This is what they read in the banking app. It has to be the DBA they already know from the ad, the checkout, and the email.
Hard name. The settlement / DBA the acquirer boarded. Alerts and the bank file against this. If the hard name is last year’s brand and the soft line is this year’s, you will miss alerts and still look unknown on the statement.
Legal name. The LLC on the application. Underwriting needs it. The cardholder does not. Printing it on the statement is the classic miss.
We do not fill a character cap. Ask this acquirer how long the soft line can be. Type nothing.
What has to match
Ads, checkout, receipt, CS greeting, and the statement line are one DBA. If CS answers as a different brand than the statement, the cardholder still thinks it is fraud.
The phone or URL on the statement has to work. A dead number next to a correct DBA still files as unrecognized.
Change the line in writing with the acquirer. Then update checkout, emails, Order Insight, and the alert seat the same day. A live seat on the old DBA is a hole on this week’s volume — that tick lives on the prevention map.
Two offers may share a line only when shoppers already know that one name. Parking a continuity brand on a grocery DBA is a MATCH problem, not a shortening trick.
After you tick the list
If the statement still shows the LLC, change it before you buy more alerts. If the soft line and the hard name disagree, pick the DBA they know and fix both. If the phone on the statement dumps to voicemail, that is the dispute.
Related: Chargebacks (unrecognized is a family), Payments (the name on the agreement is not the statement line).
Procedure
- Print the DBA they already know. Keep the LLC on the application.
- Make the soft line and the hard name tell the same story.
- Confirm the phone or URL on the statement answers, and CS greets as that DBA.
- Change the line in writing with the acquirer. Update seats the same day.
Failure modes
- Printing the LLC on the statement.
- Soft line and hard name telling two different brands.
- A phone on the statement that does not answer.
- Two offers sharing a line neither shopper knows.
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 line
- The short string on the card statement. This is what they read in the banking app.
- Hard name
- The settlement / DBA the acquirer boarded. Alerts and the bank file against this.
Work with us — We run this job on your accounts. Services
FAQ
- Should the statement show the legal entity?
- No. Print the DBA they saw at checkout. The LLC stays on the application. Legal names are how unrecognized chargebacks start.
- What is the difference between a soft line and a hard name?
- Soft is the short line on the card statement. Hard is the settlement name the bank and alerts enrolled. They must tell the same story.
- Can two offers share one statement line?
- Only if shoppers already know that one name. A shared line that matches neither ad is how both offers file unrecognized disputes.