Functional Finance

Functional Finance

Living BookBusiness ToolsDevelopersPartnersfunctionalfi.comopens in a new tab
Sign InRequest a tenant
All partner programs

Partner program · PAS and AMS plug-ins

Connect the policy system. We run the money behind it.

Build one connector and every Functional Finance client on that PAS or AMS can use it. Your plug-in sends policy events in; invoices, payments and status come back. Functional Finance works with the policy system a client already runs, never in place of it.

Talk to our partnerships teamExplore developer tools

Why partner with us

  • Build once, reuse

    Build one connector and every Functional Finance client on that PAS or AMS can use it.

  • Everything to build with

    Once your developer access is approved: a sandbox, API keys, guides, runnable flows, code samples and an MCP server.

  • Your PAS stays primary

    The policy system stays the system of record. Functional Finance runs billing and payments behind it and reports status back.

Who this is for

A systems integrator hired by an MGA or carrier, or the vendor of a policy administration system (PAS) or agency management system (AMS), that builds and maintains the connection to Functional Finance.

  • Systems integrators delivering client projects

  • PAS and AMS vendors building a reusable connector

  • Teams that want the architecture first and a clear statement of work

How it works

The PAS stays the system of record. One policy transaction, end to end.

  1. Step 1: PAS or AMS to Your plug-in.

    Policy transaction

    New business, endorsement, cancellation, renewal and more.

  2. Step 2: Your plug-in to Functional Finance.

    Policy event

    Each event carries the change (plus or minus), never a new total.

  3. Step 3: Functional Finance.

    Billed

    On execution, scheduled from the effective date.

  4. Step 4: Functional Finance to Insured.

    Invoice and payment

    Collected, applied and paid out on the platform.

  5. Step 5: Functional Finance to Your plug-in.

    Signed webhook

    Invoice, payment and policy status, retried.

  6. Step 6: Your plug-in to PAS or AMS.

    Status updated

    Matched by policy and invoice.

Build it with AI

Your engineers start from a ready-made prompt

Once your developer access is approved, each program's interface page gives you a ready-made AI prompt: the contract, every key flow and the events, grounded in our API reference, OpenAPI spec and llms.txt.

Paste it into Claude, Cursor, GitHub Copilot, Codex, Windsurf, Replit or Lovable.

See the full interface

Who does what

Event mapping
YouMap each PAS transaction to an event type.
Functional FinanceBills each event against the policy.
Amounts
YouSend each change (plus or minus), and return premium explicitly.
Functional FinanceBills what it is sent; never works out return premium.
Retries
YouMake money-moving requests safe to retry; slow down when asked.
Functional FinanceNever applies a repeated request twice; says when to try again.
Show all 6 areasShow fewer
Dates
YouEvents in effective-date order, true effective dates.
Functional FinanceBills each event on execution, scheduled from its effective date.
Products
YouBind to a product version the client authored.
Functional FinanceKeeps product versions frozen, so results replay.
Status back
YouConsume webhooks and exports by policy and invoice.
Functional FinanceSigns and retries webhooks; shows every attempt.

The full interface, for approved developers

Contracts, events, error handling and testing flows are in the developer portal, open to anyone whose developer access is approved.

Open the interface detail

How to become a partner

  1. Agree

    1. Step 1: Request access

      Ask for developer access to the platform.

    2. Step 2: Scope the work

      Agree scope with Functional Finance and the client.

  2. Build

    1. Step 3: Sandbox and keys

      A sandbox tenant and API keys, filled through the API.

    2. Step 4: Build

      Guides, flows, code samples and the MCP server.

    3. Step 5: Readiness review

      The plug-in reviewed against its use cases.

  3. Run

    1. Step 6: Go live

      The client's connection switched to live traffic.

    2. Step 7: Operate

      Delivery history, spec and changelog followed.

Building a good plug-in

  • Make every money-moving call safe to retry; the developer portal shows how.

  • Where a client cannot receive webhooks, poll the read routes and exports instead.

  • Follow the published OpenAPI spec and changelog with each release.

Questions partners ask

No. The PAS stays the system of record for the policy. Functional Finance runs the billing and payments behind it.

Yes. Once your access is approved you get a sandbox tenant and API keys, and you fill it through the API.

cURL, Python and Node.

Talk to us about building a plug-in

Tell us about the systems you connect and the clients you build for, and we'll be in touch about fit and next steps.