Uber Pro Card (Canada) API integration & Payfare data services

1. Instant cashout transaction feed

Each completed trip and Uber Eats delivery produces a credit on the card account. We expose this as a paginated stream with trip_uuid, gross fare, driver share, surge component and credit timestamp — perfect for nightly reconciliation against Uber's weekly Driver Dashboard statements.

2. Statement & export endpoint

Mirrors the Statements tab of the Driver Dashboard (the official PDF/CSV available at uber.com/earningsstatements). Returns JSON, CSV or Excel for any week or custom date range, including promotions, tips and adjustments separated from base fare.

3. Cashback rebate webhook

Pay-at-the-pump fuel and public EV charging trigger a rebate that settles a few days after the original purchase. We deliver a webhook payload pairing the original purchase, MCC, status tier and the eventual rebate credit so dashboards never double-count earnings.

4. Backup Balance & ATM event log

The $50 advance line, repayments and ATM withdrawals across Canada are surfaced as typed events (advance_drawn, advance_repaid, atm_withdrawal) — useful for liquidity scoring and the financial-wellness modules many gig platforms now ship.

5. Account & KYC state

Card status (active, frozen, replaced), Google Wallet enrollment, and the user's CDIC-eligible balance — all read through the authorized session the cardholder grants. No silent credential storage.

6. Mastercard Easy Savings rebate sync

The card includes Mastercard's Easy Savings small-business rebate program. We map merchant offers and posted rebates so they appear in the right tax category for a self-employed driver come T2125 season.

A. Tax-prep platform pulling weekly statements

Context: A Canadian tax-prep SaaS wants to auto-populate self-employment income for Uber drivers without asking them to upload PDFs.
Data & APIs: Statement endpoint (weekly), trip-level payout feed, Mastercard transaction list for deductible expenses (gas, EV charging, vehicle maintenance).
OpenData mapping: Aligns with the Consumer-Driven Banking Act's data-portability intent — the cardholder authorizes export of "specified personal information" to an accredited recipient.

B. Multi-platform earnings dashboard

Context: A gig-worker app aggregates earnings across Uber, DoorDash, Instacart and Amazon Flex into a single net-pay-per-hour view.
Data & APIs: Real-time payout webhook from the Uber Pro Card, paired with the user's tracked online time from the Driver app.
OpenFinance mapping: A read-only consent flow analogous to the UK FCA's account-information service provider model, adapted to Canada's CDBA framework.

C. Fleet manager & rental partner reporting

Context: A vehicle-rental partner who leases EVs to Uber drivers needs to verify weekly earnings to calculate revenue-share rent.
Data & APIs: Aggregated weekly fares, EV-charging cashback events, and Backup Balance utilization to flag at-risk drivers.
OpenData mapping: Cardholder grants scoped, time-bounded access; the fleet partner never receives full card credentials.

D. Cash-advance & underwriting product

Context: A regulated lender wants to pre-qualify a driver for a working-capital advance using verified Uber payout history rather than self-reported income.
Data & APIs: 12 weeks of statement history, Backup Balance utilization, ATM withdrawal density, status tier.
OpenFinance mapping: Mirrors the "income verification" use case heavily discussed in the Department of Finance's Budget 2025 open-banking consultation.

E. Driver-side personal finance coach

Context: A consumer fintech offers gig-specific budgeting and tax-set-aside automation.
Data & APIs: Daily transaction feed, cashback ledger, status-tier change events to recompute the user's effective net rate.
OpenData mapping: Uses PIPEDA's incoming data-mobility right to let the user freely move their card-derived data to a chosen advisor app.

Auth: authorized session bootstrap

POST /api/v1/uberpro-ca/session
Content-Type: application/json
Authorization: Bearer <PARTNER_TOKEN>

{
  "cardholder_consent_id": "ccnt_8f2…",
  "device_fingerprint": "android-aab-…",
  "scopes": ["transactions.read",
             "statements.read",
             "rewards.read"]
}

200 OK
{
  "session_id": "sess_01HF…",
  "expires_in": 3600,
  "refresh_token": "rt_…",
  "kyc_state": "verified"
}

Statement query (mirrors Driver Dashboard)

POST /api/v1/uberpro-ca/statements
Authorization: Bearer <SESSION_TOKEN>

{
  "from_date": "2026-04-07",
  "to_date":   "2026-04-13",
  "format":    "json",
  "include":   ["fares","tips","promos",
                "adjustments","cashback"]
}

200 OK
{
  "period_iso_week": "2026-W15",
  "currency": "CAD",
  "gross_earnings": 1284.55,
  "trip_count": 87,
  "cashback_total": 12.40,
  "items": [ … ]
}

Transaction & cashback webhook

POST https://your-app.example/hooks/uberpro
X-Signature: sha256=…
Content-Type: application/json

{
  "event": "card.transaction.posted",
  "id": "txn_01HF…",
  "card_last4": "4421",
  "merchant": "PETRO-CANADA #4128",
  "mcc": "5541",
  "amount":  -64.20,
  "currency": "CAD",
  "posted_at": "2026-04-22T18:11:04Z",
  "rebate_pending": {
    "rate_pct": 4.0,
    "tier": "Diamond",
    "estimated_credit": 2.57
  }
}

Deliverables checklist

• OpenAPI 3.1 spec covering session, statements, transactions, cashback and Backup Balance
• Reference Python and Node.js SDKs (async, retry, signed-webhook verification)
• Protocol analysis report: OAuth-style consent, refresh chain, certificate pinning observations
• Postman / Bruno collection plus a recorded happy-path test set
• Compliance brief: PIPEDA data-mobility alignment, CDBA readiness notes, retention schedule template
• Two engagement models: source-code delivery from $300, or pay-per-call on our hosted endpoint

Compliance & privacy

Canadian context matters: the Personal Information Protection and Electronic Documents Act (PIPEDA) governs cardholder data, and the new Consumer-Driven Banking Act (CDBA) — given Royal Assent in March 2026 — sets the scaffolding for accredited data-mobility recipients. We design every integration to fit that framework: explicit per-scope consent, a revocation endpoint, structured audit logs, data minimization (we never request fields a downstream use case cannot justify), and CDIC disclosure language preserved end-to-end so cardholders still understand that funds sit at Peoples Trust Company. For Mastercard Easy Savings rebates we honour Mastercard scheme rules on merchant categorization. Where a partner operates outside Canada, we add a regional addendum (e.g. EU GDPR Art. 28 processor terms) rather than forcing a one-size-fits-all DPA.

About our studio

We are an independent technical studio focused on App interface integration and authorized API delivery. Our engineers come from card-issuing platforms, gig-economy back ends, and Canadian fintech compliance teams. We have shipped integrations against issuer processors, OpenFinance aggregators, and direct mobile-app protocols, with a strong bias toward consent-driven, audit-friendly designs.

• Financial / banking apps — transaction records, statements, payment rails
• E-commerce, food-delivery and retail — orders, payments, sync
• Hotel, travel and mobility — bookings, itinerary, payment verification
• Social, OTT and dating — auth/login, messaging, profile
• Two engagement models: source code from $300 (pay after delivery), or pay-per-call hosted API

Contact

Tell us the target app (Uber Pro Card - Canada in this case) and the specific data surfaces you need — statements, transactions, cashback, Backup Balance — and we will scope a delivery within one business day.

Open contact page

NDA available on request. Sandbox / staging credentials accepted.

Engagement workflow

1. Scope confirmation — which Uber Pro Card data surfaces (payouts, statements, cashback, Backup Balance, ATM events).
2. Protocol analysis & API design — 2–5 business days, including consent & refresh-token flow.
3. Build & internal validation — 3–8 business days, with happy-path and error-path coverage.
4. Documentation, sample SDK, signed webhooks and recorded test cases — 1–2 business days.
5. Typical first delivery in 5–15 business days; CDIC / PIPEDA reviews on the partner side may extend the timeline.

FAQ

What do you need from me?

How long does delivery take?

How is Canadian compliance handled?

Do you do detection bypass?