Platform walkthrough
How Evidencee works
From first connection to a sealed audit bundle — in four steps.
No Shopify, Stripe or GoCardless? You can still add an own-website brand and record compliance by attestation — with checks you confirm using your own dated proof.
Step 01 / 04
Connect Shopify, Stripe, or GoCardless
Add your Shopify store domain and admin API token, your Stripe API key, or your GoCardless access token. Evidencee seeds default DMCC rulesets and templates for the brand, and a short guided step records your subscription model.
- Shopify — catalogue scans for drip pricing and order events; Shopify hides your subscriptions from Evidencee, so no reminders, hosted cancellation or cooling-off cases
- Stripe — API key verification, subscriptions and invoices
- GoCardless — direct debit mandates, payments and subscriptions
- Webhooks registered for you on Stripe and Shopify, pasted in on GoCardless; every delivery signature-checked
- Test mode available — connect a test environment before going live
Add a Brand
Choose the platform that powers this brand's recurring payments.
Shopify
Catalogue & order events
Stripe
Subscriptions & invoices
GoCardless
Direct debit & mandates
Step 02 / 04
Set up your DMCC compliance controls
Work through the guided setup to configure your pre-contract information block, notice templates, hosted cancellation page, cooling-off policy, drip-pricing scan targets, and connected review sources. Before you go live, Evidencee checks your settings against the DMCC minimums it enforces.
- Pre-contract template editor — a block cannot be published without its title, price, renewal and cancellation summaries
- Notice timing: at least 3 days before a trial ends, 7 days before a monthly renewal and 28 days before an annual renewal, or earlier if you choose
- Hosted cancellation page with magic-link subscriber verification
- Cooling-off policy — Approve a refund and Evidencee sends it through your connected Stripe or GoCardless account — built and tested against a stand-in, not yet run on a live account — or record one you paid yourself; Evidencee logs the reference, date, and proof
- Drip-pricing scans — your Shopify catalogue and your Stripe prices and payment links
- Review sources — Judge.me is verified end to end; Trustpilot, Yotpo, Loox, Okendo, Stamped and Google are connected but not yet verified against a live account.
Configure your DMCC compliance controls
Step 03 / 04
Evidencee operates continuously in the background
Once live, Evidencee records your subscription events as they arrive, sends reminders on schedule for Stripe and GoCardless brands, scans for drip pricing and suspicious reviews, writes each record to the Evidence Vault with a SHA-256 hash, and puts findings that need attention in your notifications.
- Webhook events recorded as they arrive
- Scheduled reminders for Stripe and GoCardless brands, each send logged as evidence
- For Stripe and GoCardless brands, cases open automatically when a trial converts to paid, a fixed-term plan renews, or a customer cancels on your hosted cancellation page — none opens for a Shopify shop
- Daily drip-pricing scans — every finding names the product or payment link and the missing price component
- Daily fake-review scans — bursts of reviews, near-duplicate text, repeat reviewers and ratings that contradict their own text surfaced for triage
- Readiness audit score recomputed from your live data each time you open it
DMCC Readiness
HealthyHealthy
Notices Due (7d)
0
Scheduled to send
Notice Failures (24h)
All clear0
Parity Issues
Pass0
Cooling-Off Cases
Clear0
Exports (30d)
0
Evidence bundles
Active Alerts
No active alerts
All compliance controls are reporting healthy.
Step 04 / 04
Export a sealed audit bundle
When a regulator or legal team asks for evidence, choose a subscriber, a subscription, a case or a date range in the Evidence Vault and export its records as one self-contained HTML bundle, sealed with a SHA-256 Merkle-root manifest. Every record in it is checked against its seal — covering its contents, when it was recorded, its event type and the subscriber — when the bundle is made, so the bundle flags any record that no longer matches its seal. A record rewritten and resealed together with every record after it and the chain’s head, which are kept in the same database, would pass.
- Search by subscriber hash, subscription ID, or date range
- Bundle includes every record in the scope you choose: notices, cancellations, refund decisions, template publishes and more
- Every record is sealed with a SHA-256 hash of what it says and when, and linked to the record before it, so a later edit to a record breaks the chain at that record and the Evidence Vault names it. The chain’s head is kept in the same database as the records, so rewriting a record, every record after it and the head together would not show
- Self-contained HTML bundle with an integrity summary and evidence count
Export Evidence Bundle
Compile an integrity-verifiable bundle for the selected scope.
Included in every bundle
HTML evidence bundle
Each record checked against its seal, plus a Merkle root over those seals.