PayMe - Claim Your Money API integration & class action settlement OpenData services

Eligibility matching service

A REST endpoint that mirrors PayMe's short-questionnaire flow: intake fields include state of residence, bank/card issuer, affected product SKUs, employment window and data-breach exposure. The service returns a ranked list of eligible settlements with estimated payout bands. In 2024 PayMe expanded this logic to include mass tort and personal injury matching — our implementation mirrors that addition.

Claim filing automation

Programmatic claim submission per settlement: our source code handles form schema discovery, field mapping (claimant name, address, proof uploads), CAPTCHA handoff and idempotent retries so a partner app can file hundreds of claims per user without triggering duplicate submissions.

Payout tracking & ledger

Structured tracking of filed, approved, rejected and paid status per claim, mapped to ISO 8601 timestamps and payout method (check, ACH, Zelle, PayPal, gift card). Deliverable includes a Postgres schema and webhook dispatcher for downstream CRMs.

Unclaimed property scanner

Aggregates 50-state unclaimed-funds databases behind one query. Returns account holder, originating entity, dollar range (states publish bands, not exact amounts) and the official state claim URL — matching PayMe's built-in unclaimed property tool without re-scraping each state treasury site.

Subscription & bill intelligence

Wraps PayMe's Gmail bill-scan output and 2025 subscription-cancellation module into a GET /subscriptions feed: merchant, renewal cadence, average charge, last charged date. Used for Rocket Money-style dashboards and bill negotiation flows with documented 30–60% savings profiles.

Tax credit & refund discovery

Surfaces tax credit eligibility (EITC, child tax credit, state-specific credits) and recoverable gift-card balances. Returns a simple recoverable_total estimate per user — a concrete hook for neobanks running "found money" notifications at statement close.

1. Neobank "found money" module

A challenger bank wants a "You may be owed $X" card on its dashboard. Business context: activation and retention. Data / API involved: POST /eligibility/match with the user's ZIP, past 24-month merchants and breach exposure; the response drives a UI card. OpenFinance mapping: this is a consumer-side OpenData read — the app is the primary source, the bank is a consent-based consumer.

2. Legal tech lead generation

A mass tort firm ingests /settlements/search?category=mass_tort to identify active cases and correlates payouts with ZIP codes. Flow: settlement metadata → firm's CRM → outreach. This avoids using personally identifiable information — only aggregated settlement metadata flows, aligning with the SettlementRadar API model we benchmark against.

3. Tax / accounting reconciliation

A TurboTax-style app pulls /payouts?tax_year=2025 so settlement receipts (often reportable as miscellaneous income above $600) land directly in the user's return. Fields: payout_amount, payer_name, payment_method, issued_at. Maps to OpenFinance "transaction categorisation" primitive.

4. Subscription audit for SMBs

A small-business SaaS tool imports the subscription feed to flag duplicate or dormant tools (e.g. two overlapping CRMs). Data: subscriptions[] with cadence, last_charge and cancellation_url. The feed avoids PSD2-style bank aggregation — it ships at the email/app layer, which is cheaper and covers non-card charges.

5. Unclaimed property enrichment for wealth advisors

RIAs enrich their client onboarding with a 50-state sweep: POST /unclaimed/search with first/last name, past addresses and DOB. Returns state-by-state hits. Business context: advisors turn "found money" into AUM conversations. Compliance: requests are logged and require written client consent, aligning with state treasury claim processes.

Deliverables checklist

• OpenAPI / Swagger spec covering every PayMe module we expose
• Protocol and auth flow report (login → OAuth / session → questionnaire → claim file → payout webhook)
• Runnable source code in Python (FastAPI) and Node.js (NestJS) with Docker images
• Postman collection, Pytest / Jest test harness and recorded HAR fixtures
• Compliance pack: consent templates, CCPA/GDPR data-subject flows, retention matrix
• 30-day warranty plus optional pay-per-call hosted tier (no infra for the client)

API example — settlement eligibility

POST /api/v1/payme/eligibility/match
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "user_ref": "u_8fa31c",
  "residence_state": "CA",
  "issuers": ["chase", "apple_card"],
  "breach_exposure": ["tmobile_2023", "att_2024"],
  "lookback_months": 36
}

200 OK
{
  "matches": [
    {
      "settlement_id": "stl_9c21e",
      "title": "T-Mobile 2023 data breach",
      "category": "data_breach",
      "deadline": "2026-06-30",
      "payout_band_usd": [25, 350],
      "required_proof": ["account_number", "id_photo"],
      "claim_url": "https://..."
    }
  ],
  "next_cursor": "eyJwYWdlIjoy..."
}

API example — payout webhook

POST https://partner.example.com/hooks/payme
X-PayMe-Signature: t=1735689600,v1=9ab8...
Content-Type: application/json

{
  "event": "payout.paid",
  "claim_id": "clm_4f21a",
  "settlement_id": "stl_9c21e",
  "amount_usd": 147.25,
  "method": "ach",
  "paid_at": "2026-04-18T14:02:11Z",
  "idempotency_key": "clm_4f21a:paid"
}

// Recommended handling: verify HMAC, upsert on idempotency_key,
// fan out to ledger + notification service, return 2xx < 3s.

API example — subscription discovery

GET /api/v1/payme/subscriptions?user_ref=u_8fa31c
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "subscriptions": [
    {"merchant":"Netflix","cadence":"monthly","last_charge_usd":15.49,
     "last_charged_at":"2026-04-02","cancel_url":"https://www.netflix.com/cancelplan"},
    {"merchant":"Adobe CC","cadence":"annual","last_charge_usd":659.88,
     "last_charged_at":"2025-11-14","cancel_url":"https://account.adobe.com/plans"}
  ],
  "detected_at":"2026-04-20T09:00:00Z"
}

Regulatory alignment

Every integration ships against U.S. consumer-protection baselines: the FTC Act §5 (unfair or deceptive acts and practices), California Consumer Privacy Act (CCPA/CPRA), and state unclaimed property statutes administered by each state treasurer. Where users reside in the EU or UK, deliverables extend to GDPR and UK DPA 2018, including Article 6 lawful-basis documentation and Article 15 data-subject access flows.

Authorized-access posture

We do not build scraping tools that bypass authentication. Every PayMe integration uses the end-user's own consent — either via the app's documented OAuth-style session, a signed data export, or a server-to-server key issued under a written agreement. Logs retain consent events for a configurable window (default: 18 months, aligned with CCPA record-keeping).

Data minimisation

Only fields required for the stated use case are transferred. For example, settlement matching ships ZIP-level residency, not full address; payout webhooks ship banded amounts when downstream use does not need the exact sum. All payloads are TLS 1.2+; at-rest data is AES-256 encrypted with per-tenant KMS keys.

About our studio

We are an independent technical studio focused on App interface integration, authorized API integration and OpenData / OpenFinance delivery. The team combines former engineers from payment processors, challenger banks, protocol-analysis labs and cloud security firms, and has shipped integrations covering finance, e-commerce, travel, OTT and now consumer-refund categories such as PayMe - Claim Your Money.

• Financial & banking apps (transactions, statements, transfers)
• E-commerce, food delivery and retail (orders, payments, sync)
• Hotel, travel, mobility (bookings, itineraries, refunds)
• Social, OTT media and dating (auth, messaging, profiles)
• Consumer refund & unclaimed property aggregation (PayMe, Payout, Compensate, Settlemate)
• Source code delivery from $300 — runnable API source + docs, paid on satisfaction
• Pay-per-call hosted API — no upfront cost, pay only for successful calls

Contact

Send us the target app name and your data requirements (endpoints, expected volume, region). We reply within one business day with a fixed quote or a pay-per-call rate card.

Open contact page

NDAs available on request. We never share client scope, source code or reverse-engineering notes between projects.

Engagement workflow

1. Scope confirmation — we lock target app, modules (eligibility, claim filing, payouts, unclaimed property, subscriptions) and deployment mode.
2. Protocol analysis & API design — 2–5 business days: static + dynamic analysis of PayMe clients, OpenAPI draft, compliance checklist.
3. Build & validation — 3–8 business days: runnable source in Python + Node, fixture-backed tests, sample deployment.
4. Documentation & handover — 1–2 business days: quickstart, Postman collection, compliance pack, optional live walk-through.
5. Total first delivery — typically 5–15 business days. Third-party reviews (e.g. Play Store listing changes) can extend timelines.

FAQ

What do you need from me to start?

How do you handle PayMe ToS and consumer consent?

What if PayMe changes its protocol?

Do you bill per call or per project?