Every number on a TrustExits listing carries its provenance: verified (read from the platform API), reviewed (accounting exports checked by hand), or declared (seller-stated). Emerald is reserved for API-verified. This page lists exactly what we read and what a listing must survive.
Keys and tokens are used once and never stored. Only aggregate summaries are kept, and the seller sees them before anything goes public.
read_orders, read_shopify_payments_accounts, read_shopify_payments_payouts, read_shopify_payments_disputes
Reads: Bank settlements (payouts) by month, order revenue, AOV, repeat-customer rate, refund rate, manual-payment share, disputes.
Proves: Real revenue at bank level, customer quality, refund and chargeback risk.
restricted key, read-only: charges, payouts, balance
Reads: Net payouts by month, charge sample, disputes.
Proves: Revenue for stores off Shopify Payments.
webmasters.readonly
Reads: Clicks, impressions, CTR, position, 16 months monthly.
Proves: Organic traffic is real and durable, not a screenshot.
analytics.readonly
Reads: Sessions, engagement, conversions, purchase revenue, channel mix.
Proves: Audience quality and the organic vs paid split.
adwords (read) / ads_read
Reads: Monthly spend, clicks, conversions, conversion value.
Proves: The ad bill the declared profit must survive.
One source can be dressed up. Independent sources that agree cannot. Every listing with live connections renders these verdicts publicly:
Marketplaces verify at listing time and disappear at transfer time; that is where the fraud lives. Here, during handover the buyer reconnects the same read-only APIs and we match the accounts against the listing-time snapshot before escrow closes. A mismatch is logged in the deal room and blocks a clean close.
Accounting, tax and social liabilities, supplier contracts, or the future of the business. The score certifies API-read revenue and traffic only. The buyer runs their own diligence, and our failure playbook says what happens when something goes wrong.
