Get paid by link, reconciled on arrival.

Create a payment request, share the link, and the payer settles into your Infinite Account. The payer is screened before funds move and the payment reconciles to the request automatically.

Draft — pending review

Who it’s for

Links on Infinite (infinite.net) are the receive side of the network: a business creates a payment request for an amount and currency, shares the link, and the payer settles into the business’s Infinite Account. The payer is screened before funds move, and the incoming payment is matched to the request and reconciled automatically.

  • Finance and AR teams collecting from customers abroad without chasing wire references
  • Platforms collecting from business customers into per-customer accounts — third-party funds flow
  • Businesses replacing “wire us and email the confirmation” with a link that reconciles itself
Capabilities

The receive side, on the same network.

Payouts, Links, Invoicing, and Checkout are capabilities of the same Infinite Account — one compliance review, one integration, one ledger.

A request, not a bank letter

Create a payment request with the amount, currency, and reference. The link carries the instructions, so no one retypes an account number.

Payer screened before funds move

The party paying you is screened the same way a payout recipient is — before settlement, with a hold for review rather than a silent landing.

Paid on the rail the payer has

The payer settles over a supported rail into your account; the request does not dictate their bank.

Matched and reconciled to the request

The incoming payment posts against the request that created it — cash applied on arrival, on the same ledger as everything you send.

Into a real account

Funds land in your Infinite Account — or, for platforms, in the customer’s own account on the network — not in a pooled float.

Example

From request to cash applied.

A logistics company in Singapore bills a US customer. On Infinite (infinite.net), the request and the reconciliation are one object.

01

Create the request

Amount, currency, and your reference — one API call or one action in the console.

02

Share the link

The customer opens a page that carries the payment instructions. Nothing to retype, nothing to email back.

03

Payer pays, screened before funds move

The customer settles over a supported rail. The payer is screened before the payment lands; a flag holds it for a named analyst.

04

Lands and reconciles

The payment posts against the request in your Infinite Account, and a webhook tells your systems the receivable is closed.

Developers

Integrate once.

A payment request is an object with an amount, a destination account, and a reference. Creating it returns the link; settlement arrives as a webhook against the same object.

create-payment-link.tsILLUSTRATIVE EXAMPLE
import { Infinite } from "@infinite/sdk";
 
const infinite = new Infinite({ apiKey });
 
const request = await infinite.paymentLinks.create({
  amount: "12400.00",
  currency: "USD",
  destination: "acct_ops_usd",
  reference: "SO-88213",
});
 
send(request.url); // to the customer
 
// payment_link.settled arrives with the same id
FAQ

Answers before you ask

Is the payer screened?

Yes — before funds move, the same way a payout recipient is: sanctions and watchlists, the network’s own counterparty record, and a hold for a named analyst when something trips. A payment link never lets an unscreened party settle into your account. The checks are the ones described on Stablecoin Compliance.

How does a payment link differ from an invoice?

A payment link is the request-and-pay mechanism — an amount, a reference, and a page the payer settles through. Invoicing wraps that mechanism in a document: line items, terms, and an invoice record the payment reconciles to. Every invoice carries a payment link; not every payment link needs an invoice.

Can a link land in a customer’s own account?

Yes. Platforms operating third-party funds flow can create payment requests whose destination is the customer’s own account on the network, so collections reconcile per customer rather than into a pooled balance you have to allocate later.

What happens if the payer sends something unexpected?

A payment that does not match its request — or that trips screening — does not reconcile silently. It holds with the case assembled for your team, on the same ledger, so the exception is worked once rather than discovered at month-end. How stablecoin refunds and returns reconcile is covered in this essay.

Send the link. Watch it reconcile.

Book a 30-minute demo and see a payment request go from link to settled, screened funds in your account.