Connect Debbie Rewards goals, points and Plaid-linked accounts to your stack
Debbie Rewards is a US fintech that pays cash for paying off debt and growing savings. Behind the friendly UI sits a rich data model — Streaks, Quick Wins, Pathway courses, a points ledger and Plaid-linked balances — that is genuinely useful for partner credit unions, treasury reporting and financial-wellness analytics. We deliver authorized OpenFinance-style APIs, runnable source code and clear documentation around that data.
- Why this app's data is valuable: it normalizes debt-payoff progress, savings deposits, monthly streaks and educational completions per user.
- Plaid-linked accounts surface credit card balances, checking/savings transactions and loan payoff events already mapped to a goal.
- The points ledger and $50 cash-out events are exactly what partner CUs and reward-platform vendors want for engagement reporting.
What we deliver
Deliverables checklist
- OpenAPI 3.1 specification covering login, goals, points, Pathway, cash-out
- Protocol and auth-flow report (mobile token, refresh, Plaid Link handshake)
- Runnable Python (FastAPI) and Node.js (NestJS) reference servers
- Pytest / Jest integration tests with replayable HTTP fixtures
- Compliance brief: CFPB §1033, GLBA, Plaid data-use, state UDAP
- Runbook for sponsor credit-union onboarding and rotation of secrets
Engagement models
- Source code delivery from $300 — receive runnable API source and full docs; pay after delivery upon satisfaction.
- Pay-per-call hosted API — call our managed Debbie Rewards endpoints and pay per request; no upfront cost.
- Optional retainer for partner CU onboarding and Pathway content tracking.
Data available for integration
The table below maps the data Debbie Rewards exposes inside its app to the integration surface we build. Each row is what a partner credit union, accounting tool or analytics warehouse typically asks us to expose first.
| Data type | Source (screen / feature) | Granularity | Typical use |
|---|---|---|---|
| User profile & onboarding-quiz answers | Onboarding flow | Per user, immutable + revisions | Segmentation, personalised Pathway, partner CU matching |
| Sponsor partner binding | Accept-sponsor screen | One active partner per user, history of changes | Attribution, partner-CU revenue share, eligibility gating |
| Linked account metadata (via Plaid) | Connect-accounts flow | Per institution / item, scrubbed of credentials | Account-aggregation health, debt vs savings classification |
| Credit-card & loan balances | Plaid liabilities + manual entries | Daily snapshot, plus delta events | Risk dashboards, payoff progress, refinance Rate Crusher leads |
| Savings & checking transactions | Plaid transactions | Per-transaction, deduped, categorised | Goal verification, anomaly detection, budgeting tools |
| Streaks & monthly goal status | Streaks tab | Per goal per month, current vs target | Engagement metrics, partner reporting, A/B testing |
| Quick Wins completions | Quick Wins tab | Per challenge per user, timestamped | Behavioural-finance research, content ROI |
| Pathway module progress | Pathway tab | Per lesson, with quiz score | Financial-education compliance reporting (CRA, NCUA) |
| Points ledger | Rewards tab | Append-only, per-event | Loyalty analytics, reconciliation, fraud review |
| Cash-out events ($50 thresholds) | Redeem flow | Per redemption, idempotent id | Treasury reconciliation, 1099-MISC reporting, webhooks |
Typical integration scenarios
1. Partner credit-union engagement reporting
A sponsor credit union (for example MSU FCU or Lafayette FCU) wants weekly evidence that Debbie Rewards is moving deposit and payoff behaviour for their members. We expose GET /v1/partners/<cu_id>/engagement returning streak completion rate, average payoff per member and Pathway completion rate. This maps directly to OpenFinance partner-reporting patterns and feeds the CU's CRA / NCUA member-impact narrative.
2. Treasury & 1099 reconciliation
The finance team needs to tie every $50 cash-out to a user, a points-balance snapshot and the funding partner. A signed webhook POST /webhooks/cash_out with idempotency keys plus a daily statement.csv export ends manual spreadsheet work, and the schema mirrors what accounting tools already accept for vendor-paid rewards.
3. Rate Crusher refinance handoff
When a user levels up enough in the Debbie program to access Rate Crusher, our integration emits a structured "refi-eligible" event with masked debt summary, current APR ranges and consented contact channel. A partner lender consumes the event over OAuth-protected webhooks and returns a pre-qualified rate, closing the loop end-to-end.
4. Personal financial wellness dashboard
Employer benefits providers and HR-tech platforms increasingly want to ingest gamified-finance signals. We aggregate Streaks, Quick Wins and Pathway module status into a per-employee score (with explicit user consent), keeping raw transaction data off the wellness vendor's stack — a clean OpenData minimisation pattern.
5. Behavioural-finance research export
Researchers studying debt-payoff psychology need anonymised, longitudinal data. We provide a periodic export of de-identified onboarding-quiz answers joined to Streaks and savings-goal outcomes, hashed with a per-study salt. This unlocks academic partnerships without exposing PII and follows GLBA's "non-public personal information" handling rules.
Technical implementation
Three sample endpoints below illustrate the shape of a Debbie Rewards integration: an OAuth-style login, a goals/streaks read, and a cash-out webhook. Real keys, signing secrets and partner identifiers are issued during onboarding.
Auth: device login & refresh
POST /api/v1/debbie/auth/login
Content-Type: application/json
{
"email": "user@example.com",
"device_id": "ios-9F3C-...-21A",
"client_app": "debbie-rewards/1.x",
"consent_scopes": ["goals.read", "points.read", "plaid.link"]
}
200 OK
{
"access_token": "eyJhbGciOi...",
"refresh_token": "rt_8b7...",
"expires_in": 3600,
"user_id": "usr_01HE...",
"sponsor_partner": "msufcu"
}
Read: monthly streaks & goal progress
GET /api/v1/debbie/goals?month=2026-05
Authorization: Bearer <ACCESS_TOKEN>
200 OK
{
"month": "2026-05",
"streak_payoff": {
"target_usd": 350.00,
"achieved_usd": 215.40,
"progress": 0.615,
"status": "in_progress"
},
"streak_savings": {
"target_usd": 150.00,
"achieved_usd": 150.00,
"progress": 1.0,
"status": "completed",
"points_awarded": 300
},
"quick_wins": [
{"id": "qw_check_score", "completed_at": "2026-05-04T13:22:11Z"},
{"id": "qw_balance_review", "completed_at": null}
]
}
Webhook: $50 cash-out event
POST https://your-app.example.com/hooks/debbie
X-Debbie-Signature: t=1715251200,v1=...
Idempotency-Key: cash_01HEZ...
{
"event": "cash_out.created",
"user_id": "usr_01HE...",
"amount_usd": 50.00,
"points_burned": 5000,
"destination": {
"type": "partner_cu_savings",
"partner": "lafayettefcu",
"account_mask": "****4421"
},
"occurred_at": "2026-05-09T14:08:32Z"
}
// Recommended: verify HMAC, ack 2xx, then enqueue downstream work.
// Errors should return 5xx so retries (with the same Idempotency-Key) are safe.
Compliance & privacy
Debbie Rewards is a US-domiciled fintech, so our integrations align with the regulatory baseline US consumer-finance teams expect: the CFPB's Personal Financial Data Rights rule under Section 1033 of the Dodd-Frank Act, GLBA confidentiality for non-public personal information, and the data-use commitments published by Plaid. We never store raw bank credentials; consent is captured per scope and revocable, and every read is logged with user id, scope, and partner identifier so audit trails hold up under examination.
For partner credit unions we additionally surface NCUA-friendly logging (member impact, education completions) and follow state UDAP rules around how rewards are described to users.
Data minimisation defaults
- Mask account numbers to last four digits in every payload.
- Hash user ids with a per-partner salt before sharing with downstream vendors.
- Strip raw transaction descriptors from research exports; keep only category and amount bands.
- Default scopes are read-only; write scopes (e.g. cash-out trigger) require a separate consent flow.
- 30-day retention on raw webhook bodies, 13-month retention on aggregated metrics.
Data flow / architecture
The pipeline is intentionally short and inspectable: Debbie Rewards mobile client → our authorized API gateway → event store & points ledger → partner-facing OpenAPI / webhooks. The gateway terminates TLS, validates OAuth tokens and Plaid Link webhooks, normalises events into a canonical schema, and writes them to an append-only ledger. Downstream consumers (a credit union, a wellness vendor, a research warehouse) read either via the OpenAPI surface or via signed webhooks; they never reach the mobile-side protocol directly. This keeps the blast radius small if a partner key is rotated and makes it easy to add a new partner without touching the upstream integration.
Market positioning & user profile
Debbie Rewards launched in 2021 and grew to 200,000+ users across the United States, distributed primarily through partnerships with not-for-profit credit unions such as MSU Federal Credit Union, Lafayette Federal Credit Union and Royal Credit Union. The user base skews toward US millennials and Gen Z carrying credit-card or student-loan balances — Debbie reports that its community has paid off $73M+ of debt and saved $149M+ toward goals, with $2.3M+ in cash rewards distributed. In 2024 the company announced a $5.3M seed round led by TruStage Ventures and Raseda Group and rolled out Rewards 2.0, a points engine that pays 1x per dollar saved or applied to credit-card balances and 1.5–2x at sponsor-partner accounts. The platform ships on both Android (com.joindebbie.debbie) and iOS, which is exactly the surface our protocol-analysis and OpenFinance integrations target.
Screenshots
Click any thumbnail to view a larger version. Images are sourced from the public Google Play listing.
Similar apps & integration landscape
Customers who care about Debbie Rewards data usually also work with one or more of the apps below. We frame them here as part of the broader OpenFinance ecosystem — each app holds adjacent data and the same integration patterns apply.
Bright Money
Holds linked credit-card balances, APRs and AI-driven payoff schedules. Teams that integrate both apps usually want unified payoff-progress reports across providers.
Qapital
Surfaces rule-based micro-savings (round-ups, payday transfers) tied to user-defined goals — a natural counterpart to Debbie's streaks for a combined savings dashboard.
YNAB (You Need a Budget)
Keeps detailed budget categories and assigned-money snapshots. Users running both YNAB and Debbie Rewards often want to import streak completions as YNAB inflows.
Undebt.it
Web-based debt planner with snowball / avalanche strategies. Pulling Debbie's payoff events into Undebt.it gives a single canonical projection of the debt-free date.
Tally
Automates credit-card payments and consolidates balances. A combined export with Debbie clarifies which payoff was incentive-driven versus auto-managed.
Rocket Money (formerly Truebill)
Tracks subscriptions, recurring bills and cash flow. Mapping its bill events alongside Debbie streaks helps explain why a goal slipped in a given month.
Long Game
Truist's gamified savings experience with mini-games tied to deposits. Conceptually the closest cousin to Debbie's points engine on the savings side.
Yotta
Prize-linked savings model. Even after recent platform changes, its data shape (deposits, draws, prize ledger) matches the points-and-redemption pattern we ship for Debbie.
Debt Payoff Planner
Mobile-first debt tracker with visual countdowns. A two-way sync exposes both the projected debt-free date and the actual rewarded payoff events.
Mint / Credit Karma
Aggregated balances, credit scores and bills. Treat them as a baseline aggregator and Debbie Rewards as the gamified-engagement layer on top.
About us
OpenFinance Lab is an independent technical studio specialising in mobile-app protocol analysis and authorized OpenData / OpenFinance / OpenBanking API integration. Our team has shipped fintech back-ends at banks, payment networks and digital lenders, so we read mobile traffic, write a clean OpenAPI surface and deliver runnable code in the same week.
- Consumer fintech, credit unions, debt-payoff and savings-rewards platforms.
- Authorization, OAuth, mobile-token rotation and webhook security reviews.
- Custom Python / Node.js / Go SDKs with replayable HTTP test fixtures.
- Full pipeline: protocol analysis → API design → build → validation → compliance brief.
- Source code delivery from $300 — runnable API source plus full docs; pay after delivery upon satisfaction.
- Pay-per-call hosted API — call our managed endpoints, pay only per call, no upfront cost.
Contact
Send us the target app name and the data scopes you care about. For Debbie Rewards a typical first scope is goals + points + cash-out; we follow up with a scoped proposal in one business day.
Engagement workflow
- Scope confirmation: which Debbie Rewards data (goals, points, Pathway, cash-out) and which partner CU(s) are in play.
- Protocol analysis and API design (2–5 business days).
- Build, internal validation and signed-webhook end-to-end test (3–8 business days).
- Docs, OpenAPI, compliance brief and Pytest/Jest fixtures (1–2 business days).
- Typical first delivery: 5–15 business days. Multi-partner or refinance-handoff scope can extend timelines.
FAQ
What do you need from me to start a Debbie Rewards integration?
How long does delivery take for a Debbie Rewards API drop?
How do you handle compliance with US consumer-finance rules?
Can you support Debbie Rewards points and cash-out events?
📱 Original app overview (appendix)
Debbie Rewards (package id com.joindebbie.debbie) is a US fintech app that pays cash for paying off credit-card balances, building savings, paying down debt and learning about money psychology. It positions itself as the first app whose rewards programme is built on a psychology-based money-goals framework rather than spend-based loyalty.
Core in-app features:
- Streaks — personalised monthly credit-card payment and savings goals.
- Quick Wins — weekly short financial challenges, e.g. checking your balance or credit score.
- Pathway — weekly courses that uncover the truth of your money psychology.
- Cash rewards — points awarded for completing the above, redeemable in $50 increments with unlimited cash-outs.
- Rate Crusher — at higher program tiers, the app helps users find lower-rate refinance offers via banking partners.
Onboarding flow:
- Download the app and complete the onboarding quiz (used to personalise content and challenges).
- Accept the matched sponsor partner — typically a not-for-profit, community-based credit union — and optionally open a free checking or savings account to redeem rewards.
- Connect debt and savings accounts via Plaid (encrypted, never sold to third parties).
- Start the Debbie course covering money mindset.
- Hit monthly goals and weekly Pathway lessons to earn points; cash out at $50.
- Level up to access lower refinance rates through Rate Crusher.
Business model: Debbie is 100% free to the user. Sponsor financial institutions pay for the experience to lift engagement on their loan and savings products, and pay Debbie when matched to a suitable user product. Reported outcomes: users have paid off roughly 3x more debt than the average debtor and saved around $100 per month on average. A $5 referral programme is also available, subject to terms.
Disclosures (paraphrased from the app listing): not a guarantee of approval; Debbie does not extend credit directly; soft credit checks do not impact credit score; terms and conditions apply.