All partner programs

Partner program · Vaults

You hold the credentials, so the platform never has to.

Be the vault behind every payment on Functional Finance. Card and bank details go into your hosted fields, stay in your PCI DSS–scoped storage and reach the payment rails through your proxy. The platform keeps only tokens and display details.

Why partner with us

  • Every capture, every client

    Wherever a payer enters card or bank details on the platform, for any client, they go into your hosted fields.

  • We build the connection

    Functional Finance builds the connection to your vault and uses your fields on every capture surface.

  • Works with every rail

    Your proxy forwards credentials to whichever payment rails a client uses, so one vault serves them all.

Who this is for

You run a PCI DSS–compliant vault that tokenizes card and bank credentials and manages them for as long as they are in use.

  • Hosted card and bank fields the host page cannot read

  • Tokens, fingerprints and card details on request

  • A proxy that swaps in the real credential on its way to a processor

How it works

A credential goes into your vault once and is only ever handled there.

  1. Step 1: Payer to Your vault.

    Enters card or bank

    Typed into your hosted field; the page never sees it.

  2. Step 2: Your vault to Functional Finance.

    One-time token

    Short-lived, and good for one exchange.

  3. Step 3: Functional Finance to Your vault.

    Server exchange

    Once, on the server. The one-time token is never stored.

  4. Step 4: Your vault to Functional Finance.

    Saved token

    Kept with display details and a fingerprint.

  5. Step 5: Functional Finance to Your vault.

    Register with a rail

    Once for each rail, through your proxy.

  6. Step 6: Your vault to Payment rail.

    Real credential

    Forwarded once; later charges use the rail's own id.

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

Credentials
YouStore raw card and bank credentials in PCI DSS–scoped storage.
Functional FinanceNever stores a full card or account number.
Capture
YouProvide hosted fields the host page cannot read.
Functional FinanceUses them wherever a payer enters payment details.
Tokens
YouIssue one-time and saved tokens, with fingerprints.
Functional FinanceExchanges each one-time token once; keeps the saved token, linked to its payer.
Show all 6 areasShow fewer
Access
YouLog every access to credentials.
Functional FinanceRole-based, audited access to tokens.
Display details
YouReturn brand, last four, expiry and bank details on request.
Functional FinanceReads them back from you, never from a caller.
Money
YouMoves no money.
Functional FinanceSends payments through the payment rails, via your proxy.

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: Introduction

      Your vault, attestations and hosting.

    2. Step 2: Due diligence

      Vendor assessment, proof of concept, PCI DSS Level 1 attestation, SOC 2 report.

    3. Step 3: Agreement

      Commercial terms for the partnership.

  2. Build

    1. Step 4: Sandbox integration

      Functional Finance builds the connection; every capture surface uses your fields.

    2. Step 5: End-to-end testing

      Card and bank capture, exchange, read-back, proxy to each rail.

  3. Run

    1. Step 6: Go live

      Your vault set up for each client profile.

    2. Step 7: Operate

      Key rotation and attestation renewals.

Security and compliance

  • Card and bank numbers are typed into your hosted fields and never pass through Functional Finance pages, requests or logs.

  • That keeps the platform's PCI DSS scope narrow. It does not remove it: the platform still protects tokens and the systems around them.

  • Access to tokens is role-based and audited.

Questions partners ask

No. Numbers go into your hosted fields and out through your proxy. The platform holds tokens, display details and a fingerprint.

Talk to us about becoming a vault partner

Tell us about your vault and your attestations, and we'll be in touch about fit and next steps.

Vault partners | Functional Finance Labs