Beetle scans a merchant's public policies into a signed, timestamped record — graded, hashed, and stored. So when a regulator, an auditor, or your risk team asks what you checked and when, you have the receipt.
This sandbox calls the production Beetle endpoint. Enter a domain and switch between the machine view — the JSON your systems receive — and the document view — the artifact your auditor files.
Every scan produces an immutable artifact: canonical policy grades, source URLs, extracted text hash, an ISO 8601 timestamp, and a snapshot ID. It hasn't changed since we wrote it, and neither has the underlying record.
Stable key order, ISO 8601 timestamps with timezone, no floating-point in money fields. Ready for the audit file, not just a developer's console.
Every record carries a sha256 over its canonical form. File it, and any future change is detectable to the byte.
Every grade points to the URL it came from and, where included, the exact extracted text. Nothing is graded in a black box.
Snapshots are stored, not regenerated. A record from March 2026 still reads as March 2026 when your auditor asks in 2028.
Beetle diffs every scan against the last one for the same domain. When a policy disappears, weakens, or a category shifts, you hear about it before the merchant's next transaction — not in next year's audit.
governing law or indemnify. Reads as marketing copy since the change.refund_policy_removed emitted.Beetle is a single POST. Bearer token, JSON in, signed JSON out. No SDK to install, no client library to keep in sync. Copy the snippet, set an environment variable, ship.
Policy templates, category codes, and register vocabularies are drawn from the frameworks your compliance team already files under. Beetle doesn't invent a new standard; it maps to the ones on your desk.
Payment Aggregator and Payment Gateway guidelines, including the 2020 directive and the 2021 clarifications. Merchant category codes and restricted-category flags align to Attachment A.
Payment Services Directive 2 and its strong customer authentication requirements. Terms, privacy, and refund policy expectations for EU-facing merchants.
Consumer Financial Protection Bureau guidance on disclosure, plus the state-level privacy regimes (CCPA, CPA, and successors).
Master Direction – KYC 2016, PMLA 2002, and related guidance. Signalled through document presence and merchant category mapping.
Compliance is a subscription, not a transaction. You pay for the merchants you monitor, not the times we check them. Daily assessments, signed filings, and drift alerts are all included.
For teams moving off manual onboarding review to continuous, per-merchant policy assessment.
For risk and compliance teams running continuous monitoring across a portfolio.
For acquirers and PSPs with their own policies, review queues, and audit cadence.
We work with payment gateways, acquirers, and PSPs to map scan output into their own risk policies and review queues. Tell us about your onboarding flow and we'll set up access.