Invoice API with Hosted Payments

An invoice API for platforms that need formal billing, hosted payment, reminders, delivery tracking, and manual settlement on one receivables record.

Invoices keep stable billing content, a public invoice link, and hosted payment without leaving the invoice lifecycle.

The same invoice model supports reminders, delivery history, manual payments, reversals, and hosted-payment fallback.

Order-backed invoices and quick-pay invoices fit the same platform model, so teams do not need a separate billing subsystem.

Workflow Outline

The buyer expects a formal invoice with itemization, reminders, and a bill-like record.

You need hosted online payment plus the ability to record checks, wires, or other offline settlement on the same invoice.

The integration should support receivables operations and delivery history, not just fast checkout collection.

What This Solves

Teams searching invoice APIs usually need more than a bill object. They need online payment, reminders, delivery status, and offline settlement tracked on the same invoice.

Step 1

Post-service billing

Create and send itemized invoices after the work is done, then let buyers pay through a hosted invoice payment page.

Step 2

B2B collection with reminders

Track issuance, reminder sends, delivery attempts, and outstanding balance on the same invoice record.

Step 3

Mixed online and offline settlement

Accept card payments through hosted invoice checkout while still recording checks, wires, or other manual payments on the same invoice.

Step 4

Order-backed invoice conversion

Start from an order, turn it into an invoice, and keep later payment and reminder history on the invoice lifecycle.

Why Flint Fits

Invoices keep stable billing content, a public invoice link, and hosted payment without leaving the invoice lifecycle.

The same invoice model supports reminders, delivery history, manual payments, reversals, and hosted-payment fallback.

Order-backed invoices and quick-pay invoices fit the same platform model, so teams do not need a separate billing subsystem.

Choose Another Path When

Use payment links when the workflow is a fast hosted request and formal billing would add friction.

Use hosted checkout when the payment page should start from a specific order or quote, not an invoice record.

Use subscription billing when recurring plan lifecycle matters more than invoice-based collection.

Implementation References

Reference the exact flow surfaces

Invoices API

Reference for drafting, sending, collecting, and tracking Flint invoices.

Invoicing Guide

Guide for invoice-led collection, reminders, and hosted invoice payment.

Webhooks API

Inspect the invoice event surface for paid, sent, delivery, and manual-payment events.

Explore invoice-led collection and nearby alternatives

These pages help distinguish invoice workflows from other hosted collection primitives.

Hosted Checkout API for Developers

Use checkout sessions when the payment page should begin from an order rather than a receivables record.

Payment Links API for Platforms

Use payment links when speed and reuse matter more than formal invoice lifecycle tracking.

Sandbox Environments for Payment APIs

Useful when you want to test invoice reminders, hosted payment, and manual settlement in isolated environments.

Next Step

Ship the workflow before polishing the edge cases

Start with the underlying Flint flow, then layer your product-specific UX and recovery paths on top.