You’re the analytics lead for Stripe Treasury’s B2B payments and settlement product. The platform processes $25B/month in cross-border payouts for marketplaces, payroll providers, and SaaS platforms. To expand into higher-volume corridors, the business wants to onboard new payout counterparties (e.g., regional banks, liquidity providers, and payment processors). Each counterparty introduces credit and settlement risk: if they fail to settle, Stripe may need to cover obligations to customers, creating direct losses and regulatory scrutiny.
Over the last two quarters, the Risk team observed that while onboarding volume increased 30%, losses from counterparty settlement failures rose from $1.2M to $2.1M per quarter. The Head of Risk believes the current onboarding checklist is inconsistent across regions and wants a single, metrics-driven creditworthiness framework that can be monitored weekly and used to set: (1) approval/decline decisions, (2) initial exposure limits, and (3) ongoing monitoring triggers.
You are asked to propose a primary KPI that summarizes the creditworthiness of a new counterparty at onboarding time, and a set of supporting leading indicators that can be monitored post-onboarding. Stakeholders include:
You have historical data for ~1,800 counterparties onboarded over 4 years, including outcomes (defaults, late settlements, limit reductions) and financial/operational attributes at onboarding.
| Source | What it contains | Grain |
|---|---|---|
counterparty_master | counterparty_id, entity_type, country, regulator, onboarding_date, status | Counterparty |
financials_onboarding | counterparty_id, as_of_date, cash, current_assets, current_liabilities, total_debt, equity, revenue_ttm, ebitda_ttm | Counterparty-date |
settlement_ledger | counterparty_id, settlement_date, expected_amount, actual_amount, days_late, shortfall_amount | Counterparty-settlement |
exposure_snapshots | counterparty_id, date, gross_exposure, net_exposure, collateral_posted, limit | Counterparty-day |
risk_events | counterparty_id, event_ts, event_type (default, limit_cut, fraud_alert, regulatory_action) | Event |
kyc_aml_flags | counterparty_id, flag_type, severity, created_ts | Flag |
You have one week to deliver a written proposal and a dashboard spec for the quarterly risk committee.