HomeSolutionsBank Transfer and Manual Settlement API

Bank Transfer and Manual Settlement API

Bank Transfer and Manual Settlement API

A bank transfer and manual settlement API for teams that need invoice-led receivables, hosted card fallback, and offline payment recording on one balance record.

Flint invoices support manual payments and reversals directly on the public invoice surface instead of forcing teams to track offline settlement in a separate ledger.
Hosted invoice checkout and manual settlement both point back to the same collectible balance, so card fallback and offline collection can coexist.
Invoice state, delivery history, and payment status remain visible on one receivables record after external settlement happens.

Workflow Outline

01

Money may arrive outside Flint through bank transfer, check, or another offline process, but the invoice still needs to update on one receivables record.

02

The same customer-specific balance may need hosted card fallback and offline settlement depending on how the buyer pays.

03

Your product needs manual payment reversals and clear invoice balance transitions instead of tracking external settlement in a separate ledger.

What This Solves

Teams searching bank-transfer or manual-settlement APIs usually need a receivables workflow where money may arrive outside the hosted payment page but still needs to update invoice state, customer balance, and support-visible history correctly.

Step 1

Offline payment recorded against an open invoice

Record a check or bank transfer directly on the invoice so collectible balance and support-visible state update together.

Step 2

Hosted fallback after send

Offer hosted invoice card collection first, then record external settlement later without leaving the same invoice workflow.

Step 3

Partial external settlement

Move the invoice to partially paid when an offline payment covers only part of the collectible balance and keep the remaining amount visible.

Step 4

Reverse a mistaken manual payment

Undo an offline payment entry on the same invoice record instead of repairing separate receivables state by hand.

Why Flint Fits

Flint invoices support manual payments and reversals directly on the public invoice surface instead of forcing teams to track offline settlement in a separate ledger.
Hosted invoice checkout and manual settlement both point back to the same collectible balance, so card fallback and offline collection can coexist.
Invoice state, delivery history, and payment status remain visible on one receivables record after external settlement happens.

Choose Another Path When

Use hosted invoice payment pages when the workflow is mostly online card collection and offline settlement is rare.
Use the B2B commerce page when manual settlement is only one part of a larger order-and-receivables workflow.
Use generic payment-link pages when the collection does not need invoice lifecycle, reminders, or customer-specific balances.

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.