myFlexPay (powered by Stream) API & Open Data Integration

Payroll and employer reconciliation

An employer or payroll provider needs to reconcile wage advances taken via myFlexPay against payroll. Our API can expose transfer history and earned-to-date amounts (with appropriate authorization). Data maps to OpenData: transaction records with amount, date, type (instant vs standard), and fee. Flow: Employer system → auth → our API → reconciliation report.

Accounting and statement export

Finance teams need exportable salary statements and transfer logs for month-end close or audits. We deliver endpoints that return net wages, stream totals, fees, and bank payments over a date range—aligned with OpenFinance statement export. Fields: net_wages, streams, fees, build_pot, paid_to_bank, period_start, period_end.

Financial wellness and aggregation

A wellness platform aggregates earned wage balance and savings from myFlexPay alongside other accounts. Our consent-based API returns available_balance, savings_balance, and optional spending summaries. This fits OpenFinance: multiple sources in one view for budgeting and coaching.

Compliance and EWA reporting

Regulators or internal compliance need visibility into EWA usage (e.g. advance volume, fee revenue). Our implementation can expose aggregated or per-user transaction counts and amounts (where legally permitted), with clear consent and retention policies—aligned with state EWA licenses (e.g. CA, NV, MO) and CFPB guidance.

HR and benefits dashboards

HR wants to see adoption and usage of myFlexPay (e.g. number of advances, average amount) without accessing individual financial data. We can design an API or reporting layer that returns anonymized or employer-scoped metrics, with data flow: app/employer → ingestion → storage → dashboard; consent and minimal identification enforced.

Deliverables

• API specification (OpenAPI / Swagger)
• Protocol and auth flow analysis (login, token, employer linkage)
• Runnable API source code (Python / Node.js) for earnings, transfers, statements
• Test scripts and interface documentation
• Compliance notes (CFPB/EWA, state licenses, GDPR/CCPA, retention)

Example: earnings balance (pseudo)

// Example: earned wage balance (pseudo)
GET /api/v1/myflexpay/balance
Authorization: Bearer <ACCESS_TOKEN>
x-api-key: <API_KEY>

Response: {
  "available_balance": 450.00,
  "earned_to_date": 1200.00,
  "savings_balance": 200.00,
  "currency": "USD"
}

Example: statement / transfers (pseudo)

// Example: transfer history / statement (pseudo)
GET /api/v1/myflexpay/statement?from=2025-03-01&to=2025-03-31
Authorization: Bearer <ACCESS_TOKEN>

Response: {
  "transfers": [
    { "date": "2025-03-15", "amount": 200, "type": "instant", "fee": 2.99 }
  ],
  "net_wages": 2400, "fees": 5.98, "paid_to_bank": 2394.02
}

Example: auth and webhook (pseudo)

// Login / token refresh (pseudo)
POST /api/v1/auth/refresh
Content-Type: application/json
{ "refresh_token": "<REFRESH_TOKEN>" }

// Webhook: transfer completed (pseudo)
POST <YOUR_URL>/webhook/transfer
x-api-key: <API_KEY>
Body: { "event": "transfer.completed", "id": "...", "amount": 200 }

Compliance & privacy

We work from client authorization or public/authorized APIs and follow privacy and local regulations. myFlexPay (Stream) operates in the US and Canada; banking is provided by Piermont Bank (Member FDIC), with deposits insured up to $250,000. In December 2025 the CFPB stated that covered EWA products are not considered credit under TILA Regulation Z. Stream holds state EWA licenses (e.g. California CCFPL, Kansas, Missouri, Nevada, South Carolina, Utah, Wisconsin). We align implementations with GDPR and CCPA where applicable (consent, minimization, retention) and recommend audit trails for advances and fees.

Data flow / architecture

A typical pipeline we design: (1) Client app (myFlexPay or your front-end) — user or employer consents and triggers requests. (2) Ingestion / API layer — our delivered service authenticates (e.g. OAuth 2.0 or x-api-key), validates scope, and queries the data source or employer integration. (3) Storage or cache (optional) — for reconciliation or reporting. (4) Output — JSON/API to your payroll, accounting, or analytics. Logs and consent are retained for audit.

Market positioning & user profile

myFlexPay targets B2B2C users: employees whose employers partner with Stream (Wagestream). Primary regions are the United States and Canada; transfer rules vary by state (e.g. Connecticut next-day only). The app is on Android (com.wagestream.myflexpay) and iOS. In the EWA space, Payactiv (Access-as-a-Service API, Fortune 100 employers), DailyPay, and Clair (embedded in payroll/HR platforms) operate in the same ecosystem; integration work for myFlexPay can complement payroll and HR system workflows.

About us

We are a technical studio focused on app interface and authorized API integration. We deliver protocol analysis, Open Data integration, third-party integration, and automated scripting plus API documentation. Services start at $300; we can deliver first and you pay when satisfied.

• Experience in fintech and mobile apps
• Android and iOS; ready-to-use API source and docs
• Transparent pricing; result-first option

Contact

For inquiries, quotes, or to send your target app and requirements:

Contact us

Process

1. Confirm needs: app name (myFlexPay) and integration scope (balance, transfers, statements, employer linkage).
2. Protocol analysis and API design (2–5 days, depending on scope).
3. Development and validation (3–8 days).
4. Delivery of docs, samples, and tests (1–2 days).
5. Typical first delivery: 5–15 business days.

FAQ

What do I need to provide?

How long until delivery?

Compliance and privacy?