What connecting PAID actually does (and what it costs)
Asked by makers — answered by AXIS. This question comes up repeatedly in listing intake and onboarding conversations; we have reworded it so no individual maker is identifiable.
The question: "Everyone on this platform points me to 'connect PAID.' What does it concretely do for my listing, what does it cost, and what's the catch?"
The answer.
PAID is the payments product in our ecosystem. Connecting it to your app does three concrete things:
- Your listing gets the PAID Verified badge — active connection confirmed on the PAID side, the strongest verification we offer.
- Every payment from the moment you connect becomes auditable history. This is the Trust Fabric Passport: a verifiable record of real transactions that an acquirer can trust without taking your word or your screenshots.
- It unlocks the exit path. Auctions on AXIS Launch require PAID-verified revenue. Connecting now, even years before you sell, is what makes selling later fast.
Costs: connecting is free and takes minutes. PAID charges standard payment processing on transactions it handles — the pricing is on PAID's site, and if you already accept payments elsewhere, nothing forces you to move existing flows. Many makers run PAID alongside their current processor and route new payments through it so history starts accruing.
The honest catch, stated plainly: the value is prospective, not retroactive. PAID cannot verify revenue from before you connected — that is precisely what makes its verification worth something. So the badge on day one says "this app's revenue is verifiable from August 2026 forward," and it compounds from there. A maker who connects today and sells in 2028 walks into diligence with two years of proof-of-life. That asymmetry — free now, decisive later — is the whole pitch, and it is also why we push it early rather than at exit time.
What we do not do: touch your revenue claims outside PAID, or gate basic listings on it. Free listings never require it.
For those who have connected: what was unclear or annoying in the setup? Specific friction reports go straight to the PAID team.
Replies (5)
Follow-up from maker intake: "I sell through app-store billing / a platform that controls payments. Can I still get verified history?"
Partially. App-store revenue can be covered by Metrics Verified (point-in-time, dated, checked against your store payouts) but not PAID Verified, since the payment rail isn't ours to confirm continuously. If you have any direct-sale surface — web checkout, team plans, API access — routing that through PAID gives you a verifiable core even if store revenue stays as documented-but-not-continuous evidence.
The question behind this question is usually "is this platform just funneling me to its own payment product?" — so let me answer that one directly. Yes, PAID conversion is the business model; listing is free because verified payment history is what makes the marketplace side work. We would rather state that than pretend otherwise. The test I'd apply: does the thing being sold benefit you independently? Two years of third-party-verifiable revenue history is worth real money in any exit, whether or not you ever auction here.
Follow-up from maker intake: "What exactly does an acquirer see from my Passport during diligence?"
With your authorization (never without it): transaction-level payment history from the connection date — volume, refunds, churn events — as verified data rather than exported spreadsheets. You control when a buyer gets access, typically at the bidder-room stage under NDA. There is a full walkthrough in the M&A category: "How Trust Fabric Passport proof-of-life works in diligence."
Follow-up from maker intake: "If I disconnect PAID later, what happens to my history?"
The history that accrued stays verifiable — those transactions happened and remain attested. What changes: the active PAID Verified badge comes off the listing, replaced by the dated historical period ("PAID-verified May 2026 – January 2027"). No retroactive erasure in either direction: we don't delete your history, and we don't pretend a dead connection is alive.
Practical note from watching makers do this: the single most common setup mistake is connecting PAID, testing it, and then routing no real traffic through it — the badge is active but the history stays near-empty, which reads worse in diligence than no badge at all (a buyer sees a verified rail with three transactions and wonders where the rest is). If you connect, route something real and recurring through it, even if it is one pricing tier.
Threads are permanent — locked, not deleted, once resolved. New posts go through a submission form and are published by moderators, usually within 1 business day.