AspireProof
Merchant monitoring and proof for payment processors

Know what your merchants are actually selling.

Underwriting is a snapshot. Aspire Proof watches every merchant from inside their store and from the open web, tells you the moment something changes, and keeps the evidence. Board the verticals you decline today, with the controls to back it up.

  • Inside and outside view
  • Processor controlled, not merchant controlled
  • Append-only evidence

Northwind Wellness

northwind-wellness.example

Connector live, 4 min agoWooCommerce
62
  • CORE-005Connector reporting from an unregistered domain
  • CORE-006Public site cannot be crawled
  • SUB-006Free trial or risk free language without billing disclosure
  • SUB-011Shipping and fulfilment policy required

last scan loading

Merchants change after you approve them.

Drift you cannot see

Products, claims, and billing terms change weeks after boarding. You usually learn about it from dispute ratios.

Disputes you cannot fight

The proof of what the customer saw lives on the merchant's site, if it exists at all.

Risk that lands on your whole book

Monitoring programs judge the portfolio, so one bad pocket of merchants becomes everyone's problem, and whole verticals get declined instead of priced.

How it works

Three steps, then it runs on its own.

01

Connect

The merchant installs one connector: a plugin, a snippet, or an API integration. It reports products, pages, policies, and subscription plans on every change, plus a heartbeat.

02

Compare

We crawl the public site independently, discover pages on our own, and compare what shoppers see with what the store reported.

03

Prove

Every finding carries hashed, append-only evidence with excerpts and capture times, tied to the merchant record.

04

Control

Request a sync, verify a connector, or change the schedule from your portal.

Inside vs outside

Two views of every merchant. The difference is the finding.

Periodic crawlers only see what a merchant lets them see, and a plugin alone only sees what the merchant reports. Proof holds both views and flags the gap between them.

Inside: reported by connector

Northwind Wellness, last full sync loading

  • /Home
  • /product/daily-greensProduct, $39.00
  • /policies/refundsPolicy
  • /product/sleep-blendProduct, $29.00

Outside: seen on the public site

Independent crawl, loading

  • /Home
  • /product/daily-greensProduct, $39.00
  • /policies/refundsPolicy
  • /product/sleep-blendProduct, $29.00
  • /lp/vip-trial

    Not reported. Selling signals: price near a buy call-to-action, subscription language.

Hidden landing pages that never reach the product feed.

Public price or billing terms that differ from the feed.

A connector that goes silent or is removed.

What it catches

How merchants get around monitoring, and what Proof does about each.

A clean page for the crawler

Available

Some sites show monitors a sanitized version.

Proof also reads the store from the inside, so the public page and the store's own records can be compared.

Hidden landing pages

Available

Offers live on pages that are never linked from the site.

The crawler discovers pages on its own and flags public selling pages the store never reported.

Changes after approval

Available

Products, claims, and billing terms change weeks after boarding.

Every save is reported within about a minute and kept on a drift timeline.

Turning monitoring off

Available

The merchant removes or disables the connector.

Deactivation and removal are reported on the way out, and silence raises a critical alert.

A decoy store

Available

The connector is installed on a clean site while selling happens elsewhere.

Keys are bound to the registered domain, and the processor can challenge the connector at any time.

Blocking the crawler

Available

A firewall or bot wall keeps monitors out.

A blocked or challenged crawl is itself a finding that escalates if it continues.

A modified connector

Available

The plugin is edited to report less.

Each install reports a fingerprint of its own files, checked against the published release.

Starving the feed

Available

The connector stays online but stops sending inventory.

A live connector with a stale feed is flagged and a fresh sync is requested automatically.

Tricks inside checkout

Roadmap

Pre-checked boxes, order bumps, and post-purchase upsells never appear in the catalog.

An automated checkout walk-through with screenshots.

Claims inside images

Roadmap

Restricted claims are placed in images where text scanners cannot read them.

Text recognition on product images.

Selling on an unknown domain

Private preview

The same merchant account is used by a site you have never seen.

Attestation enforced at authorization, plus reconciliation of orders against reported inventory.

No monitor can stop a merchant who controls their own server. Proof makes evasion visible quickly and leaves a record of it.

Control

You run the connector. The merchant does not.

Once installed there is nothing for the merchant to configure. Sync schedule, modules, minimum version, and updates are all set from your portal.

Available
  • Request a fresh sync on any merchant and get it in seconds.
  • Verify a connector on demand with a signed challenge.
  • Set how often each store reports.
  • Require a minimum connector version and let stores update themselves.
  • Every command is signed, expires in five minutes, and works once.

Connector

WooCommerce, version 0.2.0

Integrity: verified

sha256:cfba4350...cbd95b45

Last check-in
3 min ago
Delivery
Push

Command history

  • loadingfull syncacknowledged
  • loadingchallengeverified
Policy packs

Your rules, not ours.

Controls are configuration, not code. Each vertical gets a pack. Your risk team switches controls on or off, changes severity, and edits keyword lists. Every change is versioned and logged.

  • CORE-001Connector silent or removedcriticalenabled
  • CORE-002Inside versus outside content mismatchhighenabled

New verticals are added as packs. No rebuild.

Evidence

Evidence that holds up.

Findings are only as good as the record behind them. Evidence is append-only, content hashed, and timestamped, and it records which view produced it.

CapturedSourceHashExcerpt
loadingoutsidesha256:4b91ae0cfree trial, then $89.00 billed every 30 days
loadinginsidesha256:d0177f52plan: VIP monthly, interval month, price 89.00 USD
loadingsnippetsha256:9ac3e114rush my order, just pay $4.95 shipping
loadingoutsidesha256:1e6b8f70cancel any time by contacting support
Alerts and workflow

The right person hears about it.

Critical and high findings notify your team in the portal, by email, or through a webhook into the tools you already use, with repeat alerts held back so nobody gets flooded.

AvailableIn-app, email and webhook
  • criticalCORE-001Connector silent or removedloading
  • criticalCORE-005Connector reporting from an unregistered domainloading
  • highCORE-006Public site cannot be crawledloading
  • highSUB-006Free trial or risk free language without billing disclosureloading

Built for precision

Findings fire on restricted content and real differences, not on menus, footers, or shipping banners. Generated pages like cart and checkout are marked not comparable instead of raising noise.

Case managementRoadmapMerchant cure workflowRoadmapAudit exportRoadmap
Two ways to run it

Protect the portfolio you have, and approve verticals you currently decline.

Monitor

Available
  • Works alongside any gateway.
  • Nothing changes in the merchant's checkout.
  • Built for the book you already have.

Enforced

Private preview
  • The merchant processes through the Aspire payments API into your platform.
  • A customer attestation tailored to what is being sold is required before authorization. Private preview
  • The evidence record is keyed to your MID and transaction ID.
Attestation

Proof of what the customer agreed to.

For verticals where disputes turn on what the customer saw, Proof records a customer attestation tailored to what is in the cart before the card is authorized.

Private preview
  • Rendered from our domain, so the merchant's page cannot alter it or auto-accept it.
  • Tied to the exact cart, amount, and merchant account, single use and short lived.
  • The terms shown are hashed and stored with the transaction.
  • The customer receives their own copy, which is independent evidence in a dispute.

Before you are charged

Daily Greens, VIP monthly

$39.00 every 30 days

Cancel in your account or by email to support.

  • I understand this is a subscription that renews until I cancel.
  • I understand I will be charged $39.00 every 30 days.
  • I understand I can cancel in my account or by email at any time.

token expires in 09:58

Sample panel. This is a preview of a feature in development, not a live checkout.

Coverage

One ingest schema, many connectors.

WooCommerceFirst release
Public crawl for any siteAvailable
JavaScript snippet for custom sitesRoadmap
ShopifyRoadmap
BigCommerceRoadmap
MagentoRoadmap
Subscription CRMs by APIRoadmap

Built to sit inside a processor.

AvailableProcessor portal

Multi-tenant by design

Strict tenant isolation between processors, or a dedicated instance on request.

Role-based access

Separate roles for administrators and analysts, scoped to your tenant.

Full audit log

Every analyst action is recorded, including control changes and finding decisions.

One ingest API

A single normalized schema, so new platforms are connectors, not projects.

Two audiences, one record.

For the head of risk

  • Open verticals you decline today, with controls you can document.
  • See exposure across the portfolio in one place.
  • Every action is logged for your sponsor bank and examiners.
  • Tenant isolation, or a dedicated instance on request.

For the analyst

  • One place to see what changed and why it matters.
  • Alerts that are worth opening.
  • Evidence attached to every finding.
  • Pull fresh data whenever you need it.

What is live and what is next.

Available now

AvailableFirst release
  • Continuous monitoring
  • Inside vs outside comparison
  • Policy packs
  • Evidence trail
  • Processor portal
  • Processor control of the connector
  • Connector integrity fingerprint
  • Domain binding
  • Blocked crawl detection
  • Stale feed detection
  • Connector removal and deactivation alerts
  • In-app alerts
  • Email and webhook alerts
  • Self-updating connector
  • Invite-only access with tenant isolation
  • Audit log
  • WooCommerce connector

In preview

Private preview
  • Transaction-level customer attestation
  • Enforced mode

On the roadmap

Roadmap
  • JavaScript snippet for custom sites
  • Shopify
  • BigCommerce
  • Magento
  • Subscription CRM integrations
  • Real-browser crawl with screenshots
  • Checkout walk-through
  • Case management and merchant cure workflow
  • Audit export
  • Image text recognition
  • Unknown-domain discovery
  • Pre-boarding scan
  • Order reconciliation
  • Single sign-on

Questions we get asked.

No. It reads published catalog and content only.

Request a demo

See it on a sample portfolio in 20 minutes.

We walk through a sample book of merchants, show the inside and outside views side by side, and open the evidence behind a live finding. Bring one vertical you find hard to monitor.