For anyone who builds software a business runs on. By the end, your software asks Flow for a payment, gets a link back, and hears when it is paid.
On the Developers page in your account. It is shown once and stored hashed.
POST /api/payments with the amount, a title and your own reference. You get a pay link back. Show it, email it, or embed the button.
Set a notice address. Flow posts a signed JSON notice for every event, with your reference on it, and retries for about three days if you are down.
With the customer's consent, save a card or bank account once and charge it when a bill is due. Idempotency keys mean a retry can never charge twice.
If businesses run on your software, one button opens a Flow account for each of them. Their customers pay them, under their name.
Yes. Accounts start in test mode with test cards and bank numbers. Switch to live when verification completes.
Yes, one, with dependencies on nothing. Any language that can speak HTTPS and JSON can do the same four calls.
Nothing to connect, nothing per account, no monthly fee. Flow earns one fee per payment from the business taking the payment.
Create your account, connect your bank, send your first payment link. One price per payment, one deposit, your name on everything. No monthly fee.
by Dark Water