Send a payment link
The simplest possible flow. A one-time payment you email to a customer. Useful for invoices, consulting fees, custom enterprise deals.
You owe a customer a payment link. They open the email, they click, they pay. That's the whole flow.
For most one-shot payment cases, you don't need a backend integration. You just need a session URL. This recipe is the shortest path from "I want money from someone" to "they paid me."
The script
Run it. You get a checkoutUrl like https://strimz-finance.vercel.app/pay/cs_…. Email that URL to the customer with whatever copy fits your business.
Sending the email yourself
The straightforward case:
The customer clicks Pay, gets to the hosted checkout, signs once, the payment confirms.
When the payment lands
Set up a webhook for payment.completed (see Webhooks → Overview). When the customer pays, your handler runs.
That's the integration.
Using Strimz's Invoices instead
If you want Strimz to host the invoice page (line items, customer name, due date), use the Invoices API:
The hosted invoice page renders the line items, the total, your branding. Customer clicks "Pay invoice," redirects to the backing PaymentSession, signs, pays.
strimz.invoices.send triggers the email. If you want to email it yourself with custom copy, skip the send call and use invoice.id's hosted URL: https://strimz-finance.vercel.app/invoice/<invoiceId>.
When the customer pays, you get an invoice.paid webhook (in addition to the payment.completed for the backing session). Use whichever is most convenient.
Why this is short
Most B2B payment flows are short. You wanted to send a link, you sent a link, the customer paid. You don't need a complicated integration; you need a session URL.
The pieces above scale up to handle more. Line items, multiple invoices per customer, automatic dunning emails. But the floor is one API call.
