Hybrid Online and Offline Payments API

A hybrid online and offline payments API for teams that need hosted checkout, invoice-led collection, and manual settlement to update the same customer-specific balance.

Flint already separates payment links, checkout sessions, and invoices by collection shape, while allowing invoices to record manual payments on the same receivable later.

Hosted invoice payment and manual settlement both point back to the same customer-specific billing record, so online and offline collection do not need separate ledgers.

That makes hybrid billing easier for B2B or operator-assisted workflows where some money arrives through Flint and some arrives by wire, check, or external transfer.

Workflow Outline

The same customer balance may be settled by hosted checkout, later invoice payment, or money collected outside Flint.

Your team does not want online checkout and offline settlement living in separate systems with no shared audit trail.

B2B or operator-assisted workflows need one receivables model even when the final payment path changes.

What This Solves

Teams searching hybrid online and offline payment APIs usually need a workflow where the same balance might be paid by hosted card checkout, later invoice collection, or money collected outside the platform without losing the audit trail.

Step 1

Hosted payment first, offline fallback later

Start with a hosted invoice or checkout path, then record manual settlement later if the customer pays outside Flint.

Step 2

Customer-specific balances

Keep one identifiable receivable record even when the payment path changes from card collection to wire or check.

Step 3

B2B and operator-assisted workflows

Support AR-style follow-up where some buyers pay online and some settle through manual processes without splitting the ledger.

Step 4

Cleaner support history

Let support and finance read one collection timeline instead of stitching together payment pages, invoice records, and offline notes by hand.

Why Flint Fits

Flint already separates payment links, checkout sessions, and invoices by collection shape, while allowing invoices to record manual payments on the same receivable later.

Hosted invoice payment and manual settlement both point back to the same customer-specific billing record, so online and offline collection do not need separate ledgers.

That makes hybrid billing easier for B2B or operator-assisted workflows where some money arrives through Flint and some arrives by wire, check, or external transfer.

Choose Another Path When

Use hosted checkout alone when the workflow is immediate payment only and no offline settlement path should exist.

Use bank-transfer and manual settlement when the direct focus is offline recording and reversals, not hybrid collection broadly.

Use invoice APIs when the question is strictly receivables lifecycle and not the broader mix of online and offline payment paths.

Implementation References

Reference the exact flow surfaces

Payment Links vs Checkout Sessions vs Invoices

See how Flint separates immediate checkout, reusable links, and invoice-led receivables with offline payment support.

Invoices API

Record and reverse manual payments while keeping hosted invoice payment on the same receivable lifecycle.

Orders First Guide

Understand how an open balance can begin as pay-now and later move into invoice collection and offline settlement.

Explore invoices, manual settlement, and order-backed receivables

These pages narrow the next step once you know the collection flow needs both online and offline settlement paths.

Bank Transfer and Manual Settlement API

Use this when the direct focus is offline payment recording and reversal behavior.

Invoice API with Hosted Payments

Start here when the main question is invoice-owned hosted checkout rather than the hybrid collection pattern broadly.

B2B Commerce API

Go broader when hybrid collection is one part of a larger order, balance, and receivables workflow.

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.