Billing & Payment integrations that just work.
Build on the Functional Finance platform for multi-party contracts and policies billing & payment. Provision a sandbox in seconds, choose your API surface, and capture your first payment without a sales call.
Billing & payment for contracts and policies is a different problem than simple transactions.
Insurance premiums. Installment schedules. Multi-party splits. Commission disbursements. Most platforms excel at simple checkouts but miss the structural logic of contracts and policies. Functional Finance is built for that complexity.
Multi-party billing & payment is a structural requirement, not a feature gap.
Insurance premiums, installment schedules, and commission splits between agents and carriers are core data requirements. Bolt-on payment integrations break under real contracts and policies logic.
Migration debt compounds faster than you expect.
Stripe or ePay integrations that made sense for v1 become architectural constraints at scale. Switching providers means rebuilding your payment foundation, not just swapping credentials.
Legacy systems deserve modern payment rails.
SQL-first teams should not have to become REST experts to capture payments. Strongly typed SDKs and AI-generated integration code remove the protocol translation burden entirely.
Your payment data should belong to your systems.
Every transaction, installment, and audit event should be a first-class object your systems own, not a record you are renting from a payment provider.
Choose the surface that fits where you are.
Start with your current integration pattern. Move toward the native FF API as your needs grow. All four surfaces share the same sandbox and the same production platform.
Coming from Stripe?
100% compatible with Stripe API endpoints. Change the base URL, swap your API keys, and your existing Stripe integration runs on Functional Finance.
Coming from ePay?
Migration-friendly endpoints mapped to your current ePay integration. The Claude Code skill can analyze your existing code and produce a line-by-line migration assessment.
Building from scratch?
Native API with Stripe-like semantics, purpose-built for multi-party contracts and policies billing & payment. Invoices, payment links, installment schedules, and disbursements as first-class primitives.
Existing Functional Finance customer?
Continuity surface for organizations already on the Functional Finance platform. Your existing integration keeps working. Migrate to the native API at your own pace.
REST API
Built for developers. Familiar by design.
The FF API follows Stripe-compatible patterns: predictable, well-documented, and consistent. If you know Stripe, you are productive on day one.
The difference: processor-agnostic routing, structured payment intent, and full audit trails are first-class API objects, not bolt-on features.
create-contract.sh
import FuncFi from '@funcfi/sdk';
const client = new FuncFi({
apiKey: process.env.FUNCFI_API_KEY,
});
// Create a payment intent for an insurance premium installment
const paymentIntent = await client.paymentIntents.create({
amount: 42500, // $425.00 installment
currency: 'usd',
contractId: 'ctr_agt_7f3k2m',
parties: [
{ role: 'insured', partyId: 'pty_8a1b', amount: 42500 },
{ role: 'carrier', partyId: 'pty_2c9f', amount: 38000 },
{ role: 'agent', partyId: 'pty_4d7e', amount: 4500 },
],
metadata: { installment: 3, totalInstallments: 10 },
});
console.log(paymentIntent.id); // pi_funcfi_...Everything you need to ship.
Sandbox, SDKs, AI-assisted tooling, documentation, and a developer community. No gatekeeping. No sales call required.
Hosted Sandbox
Sign up and your sandbox is provisioned in seconds. Pre-loaded with realistic multi-party scenario data for contracts and policies billing & payment. API keys available immediately in your developer portal.
Strongly Typed SDKs
Java and .NET SDKs enforce correct field types and valid values at compile time. Data quality issues that affect raw API integrations are caught before your code runs.
Claude Code Skill
Generate integration code from plain language. Analyze existing Stripe or ePay code for migration assessment. Generate proof-of-concept scaffolding in scoping sessions.
AI Knowledge Base
Self-service answers to integration questions: field semantics, valid values, error handling, and integration patterns, without opening a support ticket.
Community and Office Hours
A developer community for integration discussions, pattern sharing, and migration help. Plus weekly office hours for live troubleshooting with the Functional Finance team.
Describe what you need. Get production-ready integration code.
The FF Claude Code skill generates SDK-based integration code from plain language descriptions of your scenario. Works for new builds, Stripe migrations, legacy system integrations, and SI scoping sessions.
Generate from plain language
Describe your integration scenario in plain language. The skill generates SDK-based code with correct field types, valid values, and error handling built in.
Assess your migration
Point the skill at your existing Stripe or ePay integration. It produces a migration assessment: what passes through the compatibility layer and what needs rework.
Scope integrations faster
Systems integrators use the skill live in client scoping sessions to generate proof-of-concept code and architecture scaffolding. The output becomes the technical appendix of the statement of work.
What's inside
Production-ready from day one. Full documentation at launch. No feature flags, no gated access.
Processor-agnostic: Stripe, Finix, Payrix, and more
Deploy on AWS, GCP, or Azure Marketplace
REST API and webhook events, Stripe-compatible patterns
OpenAPI / Swagger spec with idempotency keys
Sandbox environment for integration testing
SOC 2 compliant data handling and full audit trails
Your sandbox is ready in seconds.
Sign up with your business email. Your FF sandbox is provisioned instantly, pre-loaded with realistic scenario data for contracts and policies billing & payment. Sandbox API keys available immediately. No sales call required.
Business email required. One sandbox per organization.