How are invoices different from payment links?

Invoices are better for formal billing, reminders, and balance tracking. Payment links are better for fast collection when you want less ceremony and more speed.

Can buyers still pay online from a Flint invoice?

Yes. Flint invoices can route buyers into a hosted payment experience so the invoice doubles as the bill and the payment destination.

Invoices | Flint Pay

Home FeaturesInvoices

Invoices

Flint invoices give you itemized billing, hosted payment, reminders, and invoice state without forcing buyers into a separate accounting portal.

Handle formal billing without splitting the invoice, the payment flow, and the follow-up process across separate tools.

Use invoices for receivables-style workflows while still letting buyers pay online through a hosted path.

Track reminders, delivery attempts, manual payments, and outstanding balance on the same record.

Why Developers Reach for This

Searchers looking for invoices usually need more than a bill template. They need formal billing, online payment, reminders, delivery visibility, and a cleaner way to track what is still collectible.

Implement This When

The buyer expects a real invoice with itemization, due dates, and follow-up rather than a lightweight payment request.

The team needs hosted online payment plus the ability to record checks, wires, or other offline settlement on the invoice.

Receivables operations matter more than pure checkout speed.

Implementation Path

Start with the docs for this flow

Use the quickstart, API reference, orders model, and benchmark to move from evaluation into implementation.

Quickstart

Ship the first payment flow before you wire the whole stack.

API Reference

Open the REST surface for orders, checkout, subscriptions, and refunds.

Orders First

See the model behind Flint's order-backed payment approach.

Benchmark

Compare Flint against other developer payment workflows.

Common Implementation Patterns

One-off service billing

Create a standalone invoice directly from invoice input when the bill itself is the first-class workflow.

Scheduled receivables ops

Prepare invoice drafts early and let Flint issue them automatically when the planned billing window arrives.

Online invoice settlement

Let buyers pay the open invoice through an invoice-owned hosted payment path instead of separate payment instructions.

Mixed online and offline collection

Track both card payments and manual settlement like checks or wires against the same invoice lifecycle.

Choose a Different Primitive When

Use payment links when the real need is a fast shareable payment page, not formal billing.

Use hosted checkout when the flow should start from a specific order, cart, or quote rather than an invoice-led receivables record.

Use subscription billing when the requirement is recurring plan logic like trials, contracts, or setup fees.

Implementation Docs

Invoices API

Reference for creating, sending, updating, and collecting Flint invoices.

Invoicing Guide

Guide for invoice creation, sending, reminders, and hosted payment flows.

Invoice Sub-Features

Explore the specific invoice workflows behind the broader category

These pages target the more specific invoice jobs buyers search once they know they need invoicing.

Quick Pay Invoices

Create standalone invoices without building the order first, while still using Flint's invoice lifecycle and hosted payment flow.

Scheduled Invoices

Set invoice drafts to send automatically at a future time instead of relying on manual follow-up.

Hosted Invoice Payments

Let buyers pay an open invoice online through an invoice-owned hosted checkout session.

Manual Invoice Payments

Record checks, cash, wires, and offline payments directly against the invoice with balance tracking and reversals.

Invoice Reminders

Resend invoice emails, track delivery attempts, and keep follow-up tied to the invoice instead of scattered email threads.

Payment Links

Shareable hosted checkout pages for deposits, donations, event payments, and fast remote collection.

Next Step

Turn this feature into a working integration

Start with the quickstart, pick the Flint primitive that matches the workflow, then wire in the API surface and sandbox behind it.