Skip to content
Wooligan Plugins

Fraud & Compliance

Coming soon

Descriptor Shield

Make every charge recognizable, and give shoppers a "what is this charge?" page that actually answers them.

  • Audit the statement descriptor on each connected gateway
  • Show "this will appear as X" on checkout and receipts
  • A public lookup for "what is this charge?" questions
  • Planned pricing from $15/month

Features

  • Descriptor audit

    Reads the statement descriptor on connected gateways and warns you when it does not match the store brand (for example, a legal entity name the shopper will not recognize).

  • Checkout and receipt preview

    Tells the shopper, in plain language, what the charge will usually look like on their statement.

  • Public lookup

    A page where someone can enter the last four digits, amount, and date to see whether it matches an order, plus how to reach support. Rate-limited so it cannot be used to fish for other people's orders.

  • Soft descriptors

    Uses product or brand text where the gateway allows it.

  • Evidence for Dispute Desk

    Stores what was shown to the shopper, for unrecognized-charge cases.

  • Support Snap hook

    The same explanation can be inserted into a support reply.

Who this plugin is for

Any store whose legal name, URL, or processor default does not obviously match the brand on the website — and any team that answers "what is this charge?" emails by hand.

The problem

A large share of "I didn't authorize this" disputes start with a line on a bank statement the shopper does not recognize. WooPayments says a clear statement descriptor "can help reduce refunds and disputes," requires 5–22 Latin characters that reflect the business name, and notes that the default is often the site URL (statement descriptor requirements). Its dispute-prevention guide leads with fixing the descriptor (Preventing disputes).

How it works

  1. Connect your gateways and run the audit.
  2. Fix anything that does not look like your store name.
  3. Checkout, receipts, and shipping emails state what the charge will typically appear as.
  4. Publish the lookup page and point support (and the receipt) at it.

Why it's different

Descriptor settings usually live in each processor's dashboard, not in WooCommerce, so they drift — especially if you use more than one gateway. Descriptor Shield is planned as a WooCommerce-first audit, a consistent shopper-facing explanation, and a lookup page you control. Issuing banks sometimes rewrite descriptors, so the preview must be labelled as what the charge typically appears as.

Get notified at launch.

Get notified at launch

Be the first to know when this plugin launches.

Or email support@wooliganplugins.com