A note from Gnanadeep and Abhinav
Why we’re building OurPay.
We want people to be able to sell what they make, do, and know without rebuilding their payment setup every time the business changes.
Start with the seller
You have something to sell and someone who wants to buy it. Getting from there to money in your account ought to be easier to follow. Instead, there are payment methods to connect, billing rules to build, and separate records to piece together after the sale.
That is why we’re building OurPay as a merchant of record. We resell your products and services to your customers. You deliver what you promised; we bring the sale, payment, fee, and amount owed to you together.
Leave room for the next idea
We don’t want OurPay to decide that a business only counts if it sells software. A person selling a service or a physical product needs a clear way to get paid too. So does someone combining several kinds of work in one business.
There are no OurPay category exclusions for lawful products and services. We still have to connect the right payment methods and meet the requirements of each sale. When something needs more work, we want to tell you exactly what it needs.
Make the details understandable
A seller should be able to answer simple questions without a spreadsheet investigation: What did I earn? What did I pay in fees? What changed after a refund? What has actually reached my account?
We want that same clarity in the integration. Useful SDKs, readable docs, and source code you can inspect. These are things we can test and improve, one piece at a time.
Build it with us
Tell us about the payment problem you’re dealing with. A concrete example is useful: what you sell, how a customer tries to pay, and where it breaks down. That is the kind of conversation we want OurPay to grow from.