CrexiPay
A payment-request and invoicing platform we built, launched in September 2026 and now run ourselves, on the principle that the safest way to handle other people’s money is never to hold it.
Visit CrexiPayTaking a payment is easy. Being trusted with one is not.
Every service business wants the same thing: send a customer a request, get paid by card, and see the money arrive in the bank. The pay button is the easy part. The hard part is everything that makes a business comfortable letting software stand between them and their money.
That means plain answers to uncomfortable questions. Whose account does the money land in? Who carries the risk when a customer disputes a charge? What happens to a payment if a notification never arrives? A platform that cannot answer those clearly should not be taking payments at all.
And because it is money, “mostly right” is not a state that exists. A request is paid or it is not, a refund happened or it did not, and the numbers on the screen have to match the ones the bank shows.
Where the engineering actually went
Never holding the money
Merchants connect their own Stripe account and payments settle straight into it. We never hold funds and never see card numbers, so we can never become the thing standing between a business and its payouts.
Risk that sits where it belongs
Each payment is taken on the merchant’s own account, so a dispute goes to the business that made the sale, through its own processor, rather than pooling on a platform that has to police every customer at once.
Paid means paid
A request is only marked paid once the payment provider confirms it, and anything that arrives late or not at all is caught and settled anyway, so nobody chases an invoice that was already paid.
A history that matches the bank
Refunds and chargebacks are recorded against the original request, so the story the dashboard tells is the same one on the bank statement.
The merchant’s name on everything
Customers pay a business they know. Requests and emails carry the merchant’s own name rather than ours, because a payment request from an unfamiliar brand is exactly the one people hesitate over.
A whole team, without the risk
Owners, team members and platform staff have different powers, and destructive actions are reserved for the owner, so a busy member of staff can send and chase requests without being able to delete the record of them.
What this proves, and what it does not
CrexiPay is live and run day to day by us: merchant onboarding, support and the flat platform fee that is disclosed before anyone signs up. Running a payments product means being answerable for it every day, which is a different job from building one.
What it means for a project of your own is not that we would build you a payments platform. It is that software where every number has to reconcile, where responsibility for risk has to be designed in rather than bolted on, and where a customer’s trust is the actual product, is work we have already had to get right somewhere real.
If you are weighing up whether to build something, the most useful conversation we can have is about the parts that stay invisible until they get expensive. Tell us what you are considering and we will be straight with you about what it involves, including when the answer is that you should not build it.
Ready for a website that pulls its weight?
Tell us about your business and we will come back with a straight answer on what it needs, what it costs, and how long it takes.