Skip to content

Security

Built to ask for less and protect what it keeps.

DisputeGuard sits between your payment processor and your customers' order history. Here's exactly how we approach that responsibility.

Processor access

  • Stripe Connect OAuth is the recommended way to connect Stripe. It asks Stripe for read and write access, because submitting evidence needs write.
  • You can instead paste a restricted or secret Stripe API key. Keys are stored encrypted, and a restricted key limits what DisputeGuard can do. PayPal, in beta, needs a REST app client ID and secret.
  • The access is used to read disputes and the charge data needed to answer them, and to submit evidence you approve or that your auto-submit rules allow.
  • You can disconnect from DisputeGuard at any time, and revoke OAuth access from your Stripe dashboard.

Credentials and secrets

  • Processor credentials (OAuth tokens, keys and PayPal secrets) and signing secrets are encrypted at the application level before they are stored.
  • Source tokens are stored as SHA-256 hashes, with only the last four characters kept as a hint.
  • Each source gets its own token and signing secret, scoped to one account. Revoke one source without touching the others.
  • Signing secrets are shown once when created. Rotating a source replaces its token and secret together, and the old ones stop working immediately.

Signed, verified webhooks

  • Incoming processor webhooks are verified against the processor’s signature before anything is processed, and stored idempotently.
  • Every callback and webhook DisputeGuard sends is signed with HMAC-SHA256 over the timestamp and raw body.
  • Receivers reject stale timestamps (older than 5 minutes) to prevent replays; our SDKs and the WooCommerce plugin do this for you.

Nothing sent without your say-so

  • Every evidence packet (fields, files and the PDF summary) can be reviewed and edited before it is submitted.
  • Auto-submit is off by default and available on Growth and Scale. When you turn it on, a packet is submitted once it reaches the strength score you set, and in any case a number of days before the deadline that you also set.

What we collect

  • We collect what helps answer a dispute (orders, fulfilment, activity and communications) and nothing for advertising or resale.
  • Full card numbers are never collected. From Stripe we read the card brand and the AVS, CVC and 3D Secure results Stripe recorded.
  • The WooCommerce plugin also sends billing phone number, coupon codes, IP address, user agent, the Accept-Language header, a device ID from its dg_device_id cookie, login history and customer-facing order notes. Device data, login history and order notes can be switched off in the plugin.
  • The Connect API only receives what your app pushes.

Data requests

  • The WooCommerce plugin registers with WordPress’s personal data exporter and eraser. They cover data the plugin keeps in WordPress, not data held by DisputeGuard.
  • To export or erase data DisputeGuard holds, email [email protected] and we will handle the request.
  • Evidence submitted to a processor becomes part of that processor’s dispute record and is governed by their policies as well as ours.

Found a vulnerability?

Please email [email protected] with details and steps to reproduce. We'll acknowledge your report, keep you updated, and credit you if you'd like. Please don't access other merchants' data or disrupt the service while testing.

Compliance & questionnaires

We don't advertise third-party certifications on this page. If your procurement process needs a security questionnaire or details about our data processing, contact us and we'll answer as specifically as we can.

Contact us

Stop answering chargebacks from scratch.

Connect Stripe and your store in a few minutes. The next dispute arrives with its evidence already gathered.