AXIS Launch List your app

Verification standards

Four badges appear on AXIS Launch listings, and each one maps to exactly one checkable procedure below.

Metrics Verified

This badge is issued after the admin has either watched a live screen-share of the maker's Stripe, RevenueCat, PAID, or Google Analytics dashboard, or been given a read-only invite to one of those dashboards directly. Either method counts as equivalent evidence.

Verification is refreshed monthly. Every listing carrying this badge shows the line "Metrics last verified: {date}" so buyers can see exactly how current the number is.

If verification goes more than 45 days without a refresh, the badge is dropped automatically. There is no grace period and no manual override — a stale check simply results in no badge.

Identity Verified

This badge is issued after the admin has checked a government-issued ID against the LinkedIn profile of the person claiming to be the app's maker or seller. Both documents have to match the name and likeness of the person on the listing.

The ID check and the LinkedIn check happen once, at verification time. Neither document is stored afterward, and neither is ever shown to a buyer, a seller, or anyone else — only the pass or fail outcome, the badge itself, is visible.

PAID Verified

This badge is issued when an active PAID connection has been confirmed from the PAID side, not asserted by the maker. Confirmation means PAID's own systems report the connection as live.

The underlying evidence artifact behind this badge is the Trust Fabric Passport, the cryptographically auditable payment record PAID generates once connected. The badge is the summary; the Passport is the proof a buyer would actually review in diligence.

Buyer Funds Verified

This badge is issued to a prospective buyer, not a seller. The buyer emails a redacted bank or brokerage statement, and the admin reviews it and responds with a "Verified up to $X" note.

That number is what sellers see, on request — never the statement itself. Redaction and document handling are the buyer's responsibility before the email is sent; the admin does not un-redact or request the full document.

A note on diligence

Verification confirms a specific, narrow fact. It is not due diligence — buyers remain responsible for their own diligence before any deal closes.