When should I use a payment link instead of an invoice?

Use a payment link when speed matters more than formal billing. Use an invoice when the workflow needs a bill-like document, status tracking, reminders, or accounts-receivable style follow-up.

Can Flint payment links work for text-to-pay?

Yes. Text-to-pay in Flint is usually a delivery pattern built on top of hosted payment links, so the buyer opens the same checkout page from SMS or email.

Payment Links | Flint Pay

Home FeaturesPayment Links

Payment Links

Flint payment links give you hosted, shareable checkout pages for deposits, donations, event registrations, and one-off collections.

Share one hosted payment page across text, email, and QR collection flows.

Use payment links for deposits, one-off balances, donations, and event-style collections.

Start simple now without getting trapped in a dead-end payment button workflow later.

Why Developers Reach for This

Most teams searching payment links want the fastest route to a hosted payment page they can share by text, email, QR code, or social without building checkout first.

Implement This When

You need a reusable hosted payment page instead of a one-time order-specific checkout session.

The operator wants to send the same payment path by text, email, or QR without rebuilding the flow each time.

Speed matters more than formal billing, but you still need cleaner structure than cash, checks, or Venmo.

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

Text-to-pay collection

Send the hosted link by SMS or email after a quote approval, service visit, or reminder-driven follow-up.

Deposit requests

Collect commitment money before reserving inventory, appointments, or field-service capacity.

Donation and event flows

Keep one hosted page live for campaigns, registrations, or recurring public collection moments.

Remote balance collection

Close out one-off balances without sending a full invoice when the workflow should stay fast and lightweight.

Choose a Different Primitive When

Use invoices when the buyer expects a formal bill, reminders, due dates, or receivables-style follow-up.

Use hosted checkout when each buyer should enter a payment page tied to a specific order with fixed items, tax, and totals.

Use subscription billing when the real requirement is recurring plan logic rather than a shareable one-off payment page.

Implementation Docs

Payment Links API

Reference for creating and managing Flint payment links.

Payment Links Guide

Implementation guide for hosted links and common link-based workflows.

Explore payment-link workflows and adjacent product decisions

These pages help buyers move from the broad payment-links category into more specific workflows and comparisons.

Text to Pay

Turn a payment link into a textable payment flow for service teams, mobile operators, and follow-up collection.

Hosted Checkout

Order-backed checkout sessions for payments that need line items, tax, discounts, redirects, and lifecycle state.

Invoices

Send itemized invoices with hosted payment, reminders, status tracking, and cleaner follow-up than manual chasing.

Payment API

Order-first payments for developers who need line items, tax, discounts, refunds, and a full audit trail in one flow.

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.