Uber Pro Card - Canada API integration & OpenFinance services

Compliant protocol analysis and production-ready APIs for the Payfare-powered Uber Pro Card (com.payfare.uberpro): earnings, statements, cashback, Backup Balance and EV charging data.

From $300 · Pay-per-call available

OpenData · OpenFinance · Gig Economy · Mastercard prepaid · Canada

Connect Uber Pro Card data — earnings, statements, rewards — to your accounting, fleet, or fintech stack

The Uber Pro Card, launched in Canada in March 2024 through Uber, Mastercard and Payfare, holds a richer financial dataset than a typical prepaid card: per-trip cashouts, gas and EV-charging cashback, Backup Balance draws and ATM withdrawals. Our team specializes in turning that mobile-only data into authorized OpenFinance APIs.

Driver earnings & cashout API — Mirror the "automatic cashouts" flow: every Uber trip and Uber Eats delivery payout, with timestamps, gross/net, fees, and wallet posting status — useful for bookkeeping and tax preparation in Canada.

Transaction statement export — UPC card transactions (gas, EV charging, groceries, ATM, contactless purchases via Google Wallet) with paging, date filters, MCC codes, and JSON / CSV / PDF exports.

Cashback & Uber Pro status sync — Programmatic access to tier (Blue → Gold → Platinum → Diamond), monthly cashback accrual on gas (1–4%) and public EV charging (2–8%), and the $100 refueling cap.

Backup Balance & CDIC posture — Track $50 Backup Balance eligibility, drawdowns and repayments; pull the issuing-bank metadata (Peoples Trust Company) and CDIC coverage flags for regulatory dashboards.

Feature modules we deliver

1. Authentication & session

Authorized session emulation for the Uber Pro Card app: login binding, token refresh, device fingerprinting, OTP/MFA handling. Built on the same OAuth 2.0 patterns Payfare publicly references when consuming Uber's /partners/me endpoint, adapted to authorized end-user flows.

2. Earnings & payout ingestion

Pull every per-trip cashout that hits the card. Each event carries trip ID, payout amount, currency (CAD), settlement timestamp and Uber Pro tier at the moment of settlement — the canonical input for driver bookkeeping or aggregator dashboards.

3. Statement & transaction API

Card-side ledger: purchase amount, merchant name, MCC, gas-pump or EV-charge classification, decline reasons. Used for monthly reconciliation, tax categorization and small-business expense tracking under Mastercard Easy Savings.

4. Cashback & rewards engine

Expose the rule engine that converts gas / EV-charging spend into accrued rewards based on Diamond, Platinum, Gold or Blue status. Supports the $100 monthly refueling cap and partial-month proration when tier changes mid-cycle.

5. Backup Balance liquidity

Detect eligibility, available headroom (up to $50), drawdown events and automatic repayment from the next payout. Returned as a structured object so risk teams can replay the liquidity ladder.

6. ATM & Google Wallet events

Withdrawal events at participating Canadian ATMs and tokenized contactless purchases via Google Wallet, with provisioning state, terminal ID and acquirer hint — useful for fraud-detection rule sets.

Data available for integration (OpenFinance inventory)

Data type	Source screen / feature	Granularity	Typical use
Per-trip cashout	Earnings / Activity tab	Per event, near-real-time	Bookkeeping, tax prep, gross-vs-net audits
Card transactions	Card > Transactions list	Per swipe / contactless tap	Expense reconciliation, MCC analytics
Gas cashback ledger	Rewards summary	Per qualifying pay-at-pump event	Driver cost-of-fuel reporting
EV charging cashback	Rewards summary	Per public charge session (up to 8%)	Fleet electrification / sustainability KPIs
Uber Pro tier	Profile > Status	Daily refresh	Reward rate computation, segmentation
Backup Balance	Card > Balance widget	Per draw + repay	Short-term-credit risk modeling
ATM withdrawals	Card transactions	Per withdrawal	Cash-out behavior analytics
Account / KYC metadata	Profile & onboarding	One-time + change events	Compliance, onboarding analytics

Typical integration scenarios

Scenario A: Driver bookkeeping & CRA tax filing

A Canadian rideshare bookkeeping SaaS pulls per-trip cashouts and matched card spend, classifies fuel and EV charging through the cashback ledger, then exports T2125-ready summaries. The integration consumes the Earnings API and the Transactions API and joins on settlement date so net earnings reconcile against deposits to the Uber Pro Card.

Scenario B: Fleet sustainability dashboard

A delivery aggregator wants to measure EV adoption across its courier fleet. We project the EV-charging cashback events (the 8% tier flag is a strong proxy) into a daily kWh-equivalent metric and surface it alongside total trips. This maps cleanly onto OpenFinance principles: a single permissioned consumer-driven feed answers a sustainability KPI without scraping individual chargers.

Scenario C: Earned-wage-access risk control

A licensed EWA provider underwrites a cash advance against future Uber Pro Card payouts. They consume the Earnings stream, the Backup Balance object and the Uber Pro tier in real time, then size the advance against 7-day rolling cashouts. The architecture aligns with Canada's Consumer-Driven Banking Framework finalized in Budget 2025 — explicit consent, scoped scopes and revocable tokens.

Scenario D: Insurtech mileage & fuel proxy

An insurer that prices commercial-auto coverage for gig drivers wants a usage-based premium signal. Pay-at-pump and public EV-charge events from the card act as a fuel-consumption proxy, while ATM patterns refine cash exposure. Field mapping happens through our statement API; payloads return MCC, terminal location hints and Mastercard Easy Savings tags.

Scenario E: Multi-platform earnings unification

Many Canadian gig workers run Uber and Uber Eats alongside DoorDash, Instacart or Lyft. A unified earner-finance app stitches the Uber Pro Card feed with DasherDirect, Lyft Direct and Branch outputs, producing a consolidated view of weekly take-home, fuel rebates and instant-pay velocity across platforms.

Technical implementation

Login & token refresh (pseudocode)

// Authorized session bootstrap for com.payfare.uberpro
POST /api/v1/uberpro/auth/login
Content-Type: application/json

{
  "username": "driver@example.ca",
  "password": "<encrypted>",
  "device_id": "android-04a9c1...",
  "mfa_otp": "428193"
}

// 200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_...",
  "expires_in": 1800,
  "scope": "earnings statement rewards backup_balance",
  "issuer": "Peoples Trust Company"
}

Statement query — gas & EV filter

POST /api/v1/uberpro/statement
Authorization: Bearer <ACCESS_TOKEN>

{
  "from_date": "2026-03-01",
  "to_date":   "2026-03-31",
  "channels":  ["pump_gas","ev_charging","atm","pos"],
  "currency":  "CAD",
  "page":      1,
  "page_size": 100
}

// 200 OK
{
  "items": [
    {
      "txn_id": "t_8842a1",
      "ts": "2026-03-04T18:21:00-05:00",
      "type": "pump_gas",
      "merchant": "Petro-Canada #1124",
      "mcc": "5541",
      "amount": -64.20,
      "cashback_pct": 4.0,
      "uber_pro_tier": "Diamond"
    }
  ],
  "next_page": 2,
  "monthly_refuel_cashback_cap_remaining": 71.40
}

Webhook — Backup Balance event

POST <your_webhook_url>
X-Signature: sha256=...

{
  "event": "backup_balance.drawn",
  "occurred_at": "2026-04-12T03:55:11Z",
  "card_last4": "8810",
  "amount": 25.00,
  "remaining_headroom": 25.00,
  "auto_repayment": {
    "trigger": "next_payout",
    "expected_at": "2026-04-12T11:00:00Z"
  },
  "issuer": {
    "name": "Peoples Trust Company",
    "cdic_member": true
  }
}

Compliance & privacy (Canada-aware)

Every integration we ship for Uber Pro Card data is engineered around the live Canadian regulatory frame, not a generic checklist. Three pieces matter most for this app:

Consumer-Driven Banking Framework (Budget 2025): the federal government finalized amendments to the Consumer-Driven Banking Act, with the Bank of Canada now designated to administer Canada's open-banking framework. Any production integration is staged so it can later move to the official accreditation regime without re-architecting consent flows.
PIPEDA data mobility: proposed amendments give individuals the right to request that prescribed organizations transfer specified personal information — including financial data — in a structured format to another authorized recipient. Our consent UI, scope definitions and audit log are designed against that emerging standard.
PCMLTFA: March 2025 amendments strengthened Canada's anti-money-laundering framework and gave the Office of the Privacy Commissioner an oversight role over reporting-entity codes of practice. We log access events and minimize KYC fields accordingly.

On the card-issuer side, the Uber Pro Card is issued by Peoples Trust Company, a CDIC member institution. Funds on the card are eligible for CDIC coverage up to $100,000 per insured category. We expose these issuer attributes as fields on the account object so downstream systems can render the correct disclosures.

Data flow / architecture

A typical deployment uses a four-stage pipeline:

Client / Driver app boundary — authorized session against the com.payfare.uberpro backend, using OAuth-style tokens with explicit per-feature scopes.
Ingestion gateway — our hosted API (or your self-hosted source code) normalizes earnings, statement, rewards and Backup Balance objects, and signs every webhook.
Storage & lineage — append-only event store keyed by txn_id with retention policy aligned to PCMLTFA record-keeping. Optional encryption at rest with customer-managed keys.
Analytics / API output — JSON, CSV, Parquet or REST endpoints feed your accounting, fleet, EWA, or compliance system. Webhooks push deltas; pull endpoints support historical backfill.

Market positioning & user profile

The Uber Pro Card targets Canadian rideshare drivers and Uber Eats couriers — overwhelmingly mobile-first earners using Android and iOS Driver apps. Primary users are independent contractors who care about same-day liquidity, fuel cost and (increasingly) EV charging economics. Geographically, the program is Canada-only at launch; cardholder concentration follows Uber's Canadian metros — Toronto, Montreal, Vancouver, Calgary, Ottawa — but cashback eligibility extends to any Mastercard pay-at-pump or public-EV-charging merchant nationwide. This is a B2C front-end on a B2B financial stack: Payfare provides the digital banking platform, Mastercard runs the rails, and Peoples Trust Company issues. Our integration work usually serves bookkeeping SaaS, fleet operators, EWA providers and insurtech vendors selling into that population.

Screenshots

Click any thumbnail to view the full-size screenshot.

Similar apps & integration landscape

The Uber Pro Card sits inside a wider gig-worker financial stack. Canadian and North-American drivers and couriers frequently hold accounts with several adjacent apps, and unified data exports across these platforms is one of the most-requested integration jobs we see.

DasherDirect (DoorDash) — DoorDash's prepaid business Visa with no-fee instant deposits and gas cashback. Drivers running both Uber Eats and DoorDash often need a unified weekly earnings view.
Lyft Direct — Lyft's debit card and banking account for drivers, with cashback on gas. Ride-share earners moving between Uber and Lyft want statement parity across both feeds.
Branch — A workforce payments platform that powers driver pay accounts and earned-wage access; Uber Eats has historically used Branch in some markets, and cross-aggregation against the Canadian Uber Pro Card is a frequent request.
ADP Wisely Pay — A Pathward-issued prepaid paycard widely used for hourly workers; integrators often blend Wisely transaction feeds with gig-pay feeds to give consumers a single budget view.
Grubhub Instant Cash Out — Grubhub's instant-payout flow for delivery couriers; data shape is similar to the Uber Pro Card cashout stream and pairs naturally for couriers who multi-app.
Instacart Pay — Instacart shopper payment account; useful when courier-aggregator dashboards need to ingest grocery-delivery earnings alongside ride-share earnings.
Stride — A free mileage and tax tracker for gig workers; bookkeeping integrators often want to pair Stride mileage logs with Uber Pro Card fuel-cashback events for fully reconciled T2125 reports.
Gridwise — Earnings analytics and mileage tracking for rideshare and delivery; commonly co-installed with the Uber Pro Card for drivers who want hour-by-hour profitability views.
Earnin — Earned-wage-access app; appears in the same searches as Uber Pro Card cash-advance alternatives and shares the same risk-modeling needs.
Gerald — Fee-free cash-advance app frequently compared with the Uber Pro Card's Backup Balance feature in Canadian gig-worker reviews.

This list is not a ranking. It maps the integration landscape: each of these apps holds a partial picture of a gig worker's finances, and unified, consent-based access is what OpenFinance is supposed to enable.

What we deliver

Deliverables checklist

OpenAPI / Swagger specification for every endpoint
Protocol & auth flow report (token chain, MFA, device binding)
Runnable source for login, statement, rewards, Backup Balance APIs (Python or Node.js)
Webhook signer and reference consumer
Automated test suite plus replay fixtures
Compliance notes mapped to PIPEDA, PCMLTFA and CDIC disclosures

Engagement workflow

Scope confirmation: target endpoints (earnings, statement, rewards, Backup Balance) and required fields.
Protocol analysis & API design (2–5 business days).
Build & internal validation against fixtures (3–8 business days).
Documentation, sample client and test cases (1–2 business days).
Typical first delivery: 5–15 business days; third-party approvals may extend timelines.

FAQ

What do you need from me?

The target app (provided: com.payfare.uberpro), the data scope (e.g. earnings + statement only), and an authorized test account or sandbox if available.

How long does delivery take?

Usually 5–12 business days for a first API drop and docs covering login plus one data domain; multi-domain or multi-region rollouts take longer.

Do you handle pay-per-call?

Yes — you can either receive runnable source code (from $300, pay after delivery upon satisfaction) or call our hosted endpoints and pay per call with no upfront fee.

About our studio

We are a technical service studio specializing in App interface integration and authorized API integration. Our team has many years of hands-on experience with mobile applications and fintech, including payment networks, prepaid programs, and gig-economy payout platforms. We focus on protocol analysis, interface refactoring, OpenData integration, third-party interface integration, automated data scripting and full delivery of interface documentation. Customers provide a target app and a list of requirements; we deliver runnable API or protocol implementation source code.

Marketed to overseas clients, fluent in cross-region authorization and data laws
Compliant, lawful interface implementations aligned with local privacy frameworks
Android and iOS coverage, with Python / Node.js / Go reference SDKs
Two engagement models: source-code delivery from $300, or pay-per-call hosted APIs

Contact

For quotes, NDAs, or to submit your target app and requirements, open our contact page:

Contact page

📱 Original app overview (appendix)

The Uber Pro Card is a business prepaid Mastercard powered by Payfare, designed exclusively for drivers and couriers who use the Uber Driver app. It can be used for purchases anywhere Mastercard is accepted.

How it works: Earnings go directly to the Uber Pro Card after every trip via automatic cashouts. Drivers earn up to 4% cash back on gas at the pump and up to 8% cash back on EV charging when they reach Diamond status; the higher the Uber Pro tier, the higher the cashback rate, with no trip fee. A Backup Balance of up to $50 is available when cash is low, subject to terms and eligibility.

Card management: The card can be added to Google Wallet for contactless payments, and cash withdrawals are supported at select ATMs across Canada. Drivers apply for the Uber Pro Card directly through the Driver app.

Issuer & insurance: The Uber Pro Card is issued by Peoples Trust Company under licence from Mastercard International Incorporated. Mastercard is a registered trademark, and the circles design is a trademark of Mastercard International Incorporated. Funds loaded onto the card are held by the issuer Peoples Trust Company, a member institution of CDIC, and are eligible for CDIC coverage. Uber and Payfare are not CDIC member institutions. Funds are combined with eligible deposits held under Peoples Trust Company for up to $100,000 of deposit protection, per insured category, per depositor. Further details are available on CDIC's website.

Terms note: Rewards are subject to change without notice. Gas and public EV-charging merchant classification is subject to Mastercard rules. Cash back on gas only applies to pay-at-the-pump purchases. Cash back rewards are earned for select purchases using the Uber Pro Card and become available for redemption as those purchases settle.