Payments
Checkout, billing and subscription management.
Nothing launched in this category yet.
Be the firstAbout Payments
Payment tooling covers accepting money, and the launches here range from full processors to the layer of tools around them: checkout components, subscription management, invoicing links, tax handling, fraud screening and payout tooling for marketplaces.
The first practical decision is processor versus merchant of record. A processor moves the money and leaves you responsible for tax determination, collection, filing and — importantly — being the party of record for every transaction. A merchant of record sells to the customer on your behalf and takes on the tax obligations, at a higher percentage. For a small software business selling internationally, the higher fee frequently costs less than the alternative once the compliance work is priced honestly. For a business with an existing finance function, the processor is usually correct.
Checkout design is where conversion is won and lost, and the pattern is consistent: abandonment clusters at surprises. An unexpected fee, a forced account creation, a required field nobody anticipated, or a currency the buyer did not expect all cost completions. Showing the full price early, supporting the payment methods local to your buyers, and asking for the minimum are the levers that work.
Failed payments deserve dedicated attention for any recurring business. A large share of subscription cancellation is involuntary, and intelligent retry logic combined with a good update-your-card flow recovers a real portion of it. This is the highest-return work in the subcategory and the least discussed.
Fraud and chargebacks are a cost of doing business and manageable rather than mysterious. Clear billing descriptors so customers recognise the charge, prompt refunds when asked, and accessible support prevent a meaningful share of disputes, which are expensive regardless of who wins.
There are things you should not build. Storing card numbers yourself is a serious undertaking with serious obligations, and there is no good reason for a small product to do it when tokenised alternatives exist. Let the processor hold the sensitive data.
Payouts, if you run a marketplace, are the hard part nobody warns you about — identity verification, cross-border transfers, and the tax reporting obligations that come with paying people. Choose a platform that handles it rather than assembling one.
From the blog
Reading on launching, ranking and payments.







