Five steps from "the customer paid for a service" to "an immutable verified review with a resolution badge on the public record." The verification stack collects multiple non-GPS signals; the 30-day window does the rest.
Each step produces a verifiable event in the operator dashboard. Each event is logged with a cryptographic timestamp. Nothing about the customer's device location at the moment of review submission is used — that's the Chen US 9,842,340 prior art, deliberately avoided.
While the customer is being served — paying, scheduling, receipting — Authyr quietly collects whatever signals the vertical supports. Payment-rail webhooks, receipt printouts, NFC taps, photographed receipts, booking confirmations. The customer doesn't do anything special; the business doesn't change its workflow.
After the service is complete, Authyr cross-references the captured signals against the business's expected pattern. Two or more independent signals trigger a verified attestation. Three or more produce Tier A. The verified-customer record is signed cryptographically — it can be independently verified by any third party without trusting Authyr.
Branded SMS or email referencing the specific service ("Your appointment yesterday with Smith Law"). The invitation links to a branded Authyr review form. Multi-platform amplification is offered after — but the verified record is the source of truth, not the third-party post.
For positive reviews (4-5 stars), the customer can immediately also share to Google / Yelp / Facebook on their own device if they choose. For 1-3 star reviews, the review enters the 30-day window automatically. Only the reviewer and the business owner can see it during the window. The owner can engage, refund, redo, comp, or escalate — but cannot modify or delete the review.
Whatever the review reads at the close of the window becomes the public record. Cryptographically sealed. Owner cannot delete. Reviewer cannot revise. A resolution badge — "Resolved within window," "Issue unresolved per reviewer," or "Owner did not respond" — is permanently attached.
Each signal type collects a different kind of evidence. Two or more independent signals trigger verified attestation; three or more produce Tier A. The combination is the patent-clean novelty — none of these signals operate on real-time device-location services at moment of review submission, which is what Chen US 9,842,340 already covers.
Stripe / Square / Toast / Clover webhook confirms the card swipe at the business's POS at a known timestamp. Pulled from the processor, not the customer's phone.
Customer photographs the receipt. EXIF GPS, capture timestamp, and OCR'd business name + transaction ID triangulate. Post-hoc, never real-time location-services.
Counter-mounted or table-side cryptographic token. RF/visual proximity at a known moment — different signal domain from device location services.
Receipt prints a single-use signed code. Customer redeems it once to begin a verified review. Pure cryptographic chain, no device telemetry.
Calendar-system record (Calendly, Acuity, Clio, Dentrix, etc.). Confirms the appointment was scheduled and attended. Standard operations byproduct.
Multiple photos with coherent EXIF timestamps + locations. Reverse-image-searchable provenance hardens further. Customer-initiated, optional.
Another verified Authyr customer present at the same time corroborates the reviewer. Pure network effect — gameable only if the network itself is compromised.
Patent-protected (PPA #7). The owner gets 30 days to resolve. Cannot delete. Cannot modify. After 30 days, immutability. A resolution badge tells the public what happened.
Multi-signal verification passes. Review enters the private window. Owner receives an immediate notification with full review content and the customer's contact information. The public record shows nothing yet.
Owner can engage directly with the customer through an in-platform thread (preserved forever as part of the audit trail) or through any external channel they prefer. Refund, redo, comp, escalation, sincere apology — whatever the situation requires. The customer can voluntarily withdraw or update the review at any time. The owner cannot.
Whatever the review reads at this moment becomes the public record. Cryptographically sealed. No owner-delete. No reviewer revisions. The signed record is portable to any platform that wants to verify it.
One of the badges below appears with the review wherever it's displayed — on authyr.com, on the business's own website, and on any partner platform that has integrated. Strong signal both ways: resolved looks excellent, unresolved looks damning.
Authyr signs each review cryptographically at issuance. The receipt can be independently verified by any third party. The tier rating tells the viewer how strong the underlying evidence is.
| Tier | Signals required | Used by | Strength |
|---|---|---|---|
| A | 3 or more independent signals | Legal, medical, financial · highest-stakes verticals | Cryptographically anchored, three independent witnesses to the same event |
| B | 2 independent signals | Home services, auto, beauty, vet · default for most operators | Two independent witnesses; still meaningfully harder to spoof than asserted-trust |
| C | 1 verification signal | Lightweight / high-volume / low-ticket businesses | One witness; weaker but still better than the unverified default |
| D | None — self-attested | What every existing review platform produces | None — shown only for contrast |
Three specific prior-art references shaped the Authyr architecture. The design-around is not a workaround — it's a structurally better primitive.
Granted Dec 2017. Covers using device location services to verify reviewer presence at moment of review submission. Authyr's stack uses post-hoc non-location-service signals exclusively. None of our seven signal types operate on real-time device telemetry at submission.
The Adobe-led capture-time provenance standard. Authyr's customer-attestation primitive sits above C2PA, not parallel to it. Our Capture SDK is C2PA-interoperable rather than redundant, signing customer-attestation receipts that can carry C2PA manifests as a sub-record.
Various prior patents and platform features allow some form of owner suppression. Authyr's 30-day window is structurally different — the owner's only power is to resolve the underlying complaint. The review record itself is immutable from the moment of submission onward. PPA #7 (Frequentor patent series) covers our specific architecture.
Bad review tools claim things they can't deliver. Authyr will get torn apart in a sales call if our marketing isn't technically defensible. So here it is in writing.
Founding cohort slots open across legal, medical, and home services.
Apply for the Founding cohort → Read the whitepaper