Verify a Postboard Track Record
Someone gave you a Postboard verification link. This page is for you: lenders, landlords, accountants, and partner platforms. It explains how to inspect the source of each supplied field and check that a snapshot came from Postboard and was not altered. Stripe-cleared earnings are identified separately from signed agreements, reviews, and other activity. Each recipient decides whether the record meets its requirements; institutional acceptance has not been established.
Why this is different
A Track Record is a provenance-labeled record, not one blanket verification badge. Payment totals labeled as verified earnings come from Stripe-cleared payments; agreement and review signals come from their respective Postboard workflows. A recipient asks Postboard to authenticate a shared snapshot online and compare it with current data. That does not certify every member-provided detail or require a recipient to accept it.
Three ways to verify
Pick the one that matches your workflow. The fields can differ by consent and surface; each method preserves the evidence labels available to it.
1. Click the link
The fastest path. Open the URL the applicant gave you. You'll see a verification page with the snapshot date, total verified income, project count, and a QR code that points to this same data. No login required.
Useful for: a person reviewing a provider-authorized record alongside its own required documentation.
2. API call
One authenticated GET returns consent-scoped JSON directly from Postboard. Access is controlled by a time-bounded bearer grant and recorded in the audit trail. See the code samples below.
Useful for: integrating a provider-authorized integrity check into an existing review workflow.
3. PDF letter
The applicant can also send you a downloadable PDF income verification letter. The letter includes the verification URL, a reference digest, and a QR code for your records.
Useful for: workflows that need a dated document plus a verification link.
API integration guide
Postboard exposes a consent-scoped read path for authorized recipients. The Authorization header carries the bearer token issued through the provider consent flow; the response returns only the fields the provider authorized for the recorded permissible purpose. The API verifies provenance and integrity, not the recipient's acceptance policy. The live bearer-authorized response is served directly by Postboard; it does not contain a separate HMAC signature today.
GET /api/verifier/v1/passport
Returns the Track Record snapshot the applicant authorized for the granted permissible purpose. Bearer auth required.
curl https://www.postboard.io/api/verifier/v1/passport \
-H "Authorization: Bearer $POSTBOARD_GRANT_TOKEN"
{
"subject": { "providerId": "..." },
"purpose": "income_verification",
"verifier": {
"slug": "acme-lending",
"display_name": "Acme Lending",
"organization_type": "lender"
},
"granted_fields": ["verifiedEarnings", "rating", "reliability"],
"granted_at": "2026-04-30T...",
"expires_at": "2026-07-29T...",
"passport": {
"verifiedEarnings": { "cents": 8420000, "display": "$84,200" },
"rating": { "average": 4.9, "reviewCount": 28 },
"reliability": { "onTimeRate": 0.96 }
}
}Bearer token is issued through the provider consent flow and scoped to a specific permissible purpose (lender / landlord / accountant / partner). Grants expire after the agreed window and the applicant can revoke from their dashboard at any time. Missing or invalid Bearer returns 401. Scope denied returns 403 with the needed-scope hint.
What Postboard can confirm
- Total verified earningsSum of payments cleared by Stripe in the current UTC calendar month through issue time plus the preceding 11 calendar months, net of refunds and chargebacks. Anchored to Stripe webhooks; cannot be self-attested.
- Payment-derived supporting figuresUnique paying clients, average verified income across all 12 reporting months, adjacent-month change, and payment gaps are derived from the same Stripe-cleared transactions.
- Accepted proposalsCounts accepted Postboard proposal records separately. Acceptance does not prove completion or payment.
- Snapshot authenticityPostboard validates a server-held HMAC bound to the stored snapshot, owner, token, and signed expiration. The printed SHA-256 value is only a reference digest.
- Member-since dateWhen the provider opened their Postboard account. The record compounds with tenure; the longer they have worked through Postboard, the deeper it goes.
- Adjacent-month income changeAverage symmetric absolute percentage change between adjacent reporting months, using the two-month average as the comparison base. Zero-income months are included.
- Longest revenue gapMaximum days between paid invoices in the window.
Privacy + security
- Provider-controlled. Snapshots are issued by the provider on demand. They choose the verifier and the expiry. Postboard cannot disclose Track Record data without provider consent.
- No SSN, no bank routing. Track Record verification doesn't expose tax IDs, account numbers, or any sensitive identifiers. Just the income picture.
- Time-bounded access. Verifier grants expire and can be revoked. Separately, member-generated Income Passport snapshots expire after 90 days.
- Audit trail. When you fetch a snapshot, the provider sees the access in their verifier-grants list.
Become an early verification partner
We want Postboard Track Records to become a useful form of income verification for independent workers, and we're looking for the first lenders, landlords, and platforms to help shape how that works. Early partners get integration support, joint comms, and a featured listing on this page.
Institutions accepting Postboard verification
No accepting institution has been established yet. This list will grow only after a named organization confirms a bounded use case. If your institution wants to test Postboard Track Records, email us and we'll document the outcome here.
We're building this list now.
Help run the first documented institutional pilot. Reach out.
Are you the independent worker who got referred here?