Regulatory Radar.

Every change from the OCC, FDIC, Federal Reserve, CFPB, FINRA, SEC, FinCEN, state regulators, and DORA in the EU — tracked, classified by impact, annotated with AI-generated analysis of partnership consequences, and linked to concrete action deadlines. Your compliance team's desk, in the same app where the partnership actually happens. Built so a non-compliance-specialist partnership lead can tell at a glance whether a given change requires action this week, this month, or this year.

What gets tracked

Regulators publish bulletins, final rules, enforcement actions, proposed rules with comment periods, FAQs, and guidance in a dozen different formats across a dozen different destinations. The Radar normalises all of them into a single schema the compliance desk can actually use:

Regulators covered

Fields per update

Every entry in the Radar carries seven structured fields you can actually filter and act on:

• Regulator — one of the above, with subregulator context where relevant.
• Impact level — Critical (immediate action required), High (action within 30 days), Medium (monitor and plan), Low (awareness only).
• Category — third-party risk, data privacy, consumer protection, cybersecurity, operational resilience, AI governance, capital requirements, fair lending, licensing.
• AI analysis — Claude-generated commentary on how this specifically affects bank-FinTech partnerships.
• Recommended actions — concrete, deadline-bearing steps (not "review for applicability" — "update your vendor due diligence template to reflect the new OCC Tier III criteria by 2026-06-30").
• Affected partnership types — BaaS, co-brand, API integration, data sharing, white-label, referral.
• Source — URL, bulletin number, and publication date. Every item has a verifiable link back to the regulator's primary publication.

Impact levels explained

Relevance to your organization

Not every item applies to every org. An item is surfaced to your org if any of:

• affects_banks matches your org type (for bank members) or affects_fintechs matches (for fintech members).
• The item's affected_partnership_types overlaps with the partnership types in your active Pipeline.
• You've subscribed to the relevant regulator via Settings → Regulatory subscriptions.
• A partner on your active Pipeline is regulated by the issuing regulator (cross-relevance).

Critical items always surface regardless of filter; Medium and Low respect the above filters.

AI analysis section

Every Radar entry includes an AI-generated commentary on partnership implications. This is not legal advice — it is editorial analysis the way a trade press columnist might summarise what a rule means for practitioners. The prompt explicitly instructs Claude to:

• Describe who is most affected (by partnership type, stage, geography).
• Identify the first operational action a reasonable team would take.
• Flag second-order implications (e.g., "this rule increases cost of BaaS partnerships, which may accelerate consolidation among smaller BaaS fintechs").
• Avoid definitive claims about litigation risk or specific enforcement outcomes.

Per-org read and action tracking

Each Radar item has a per-org state: unread → read → actioned → dismissed. Admins can mark items actioned with a short note describing the action taken (e.g., "updated vendor DD template 2026-05-15, new template rolled out to partnerships team 2026-05-20"). Actioned items drop out of the active list but remain in history and are included in the compliance export — so an examiner can see exactly when your team reviewed each change and what they did about it.

Notification channels

• In-app banner — Critical items surface as a top-of-screen banner for all admins.
• Email digest — weekly Monday digest of new Medium+ items. Configurable to daily for High+ or critical-only.
• SHIELD Alert — Critical items automatically emit a High-severity SHIELD Alert with full context.
• Webhook (Enterprise) — POST per new item to a configured URL for integration with GRC platforms.

API surface