Every product should not integrate payments separately.
That repeats work and makes changes harder to manage across the company.
Product
Karyopay
One payment layer. Fewer payment integrations to manage.
Karyopay is the payment aggregator we're building for Truvenda products and other business use cases. The idea is simple: products should be able to ask for a payment without each one rebuilding the payment layer from scratch.
Product site coming soon
How it works
01
What Karyopay is
Karyopay sits between a product that needs payment and the services that can process it.
A storefront, invoice, payment link or another product may all need to collect money. We do not want each one to carry its own separate payment integration and its own idea of what a payment means.
Karyopay gives us one payment layer to build around, while the product using it can stay focused on the customer experience it actually owns.
02
Why we're building an aggregator
Payment code gets complicated quickly when every product owns its own version.
The customer sees a pay button. Behind that button there is more work: starting the payment, handing it off, knowing what happened and giving the result back to the product that asked for it.
Provider details should not leak into every product.
The product should know it needs a payment, not carry all the provider-specific plumbing itself.
A payment result needs one clear meaning.
The calling product needs a dependable answer about what happened so it can continue its own workflow.
Changing the payment layer should not mean rebuilding the product.
A cleaner boundary gives us room to change what sits underneath without rewriting everything above it.
03
A payment through Karyopay
The product asks. Karyopay handles the payment path.
The exact provider may vary. The product using Karyopay should not have to rebuild its checkout or business logic every time the payment layer changes.
A product starts a payment.
It sends the amount and the context needed for that transaction.
Karyopay handles the payment layer.
The aggregator deals with the provider-facing part of the transaction.
The payment is processed.
The customer completes the provider's payment experience.
The result comes back.
Karyopay gives the calling product the payment outcome it needs to continue.
04
The boundary matters
The business product should not become the payment provider integration.
Truvenda Business owns things like the order, invoice and customer workflow. ZestGo owns its shopping experience. Karyopay's job is narrower: handle the payment layer and return a usable result.
Keeping those responsibilities separate makes the products easier to change without tying everything to one implementation.
05
Where it can be used
The payment layer can serve different products without turning them into the same product.
Karyopay is useful because the things above it can stay different. A storefront and an invoice may ask for payment for very different reasons.
Truvenda Business
Payments for storefront orders, invoices, payment links and other business workflows.
ZestGo
A payment layer underneath a very different video-based shopping experience.
Other Truvenda products
Future products can use the same boundary where payment is needed.
Other business use cases
Karyopay is being built as a payment product in its own right, not only as hidden plumbing.
06
What matters in the payment layer
The payment layer should be boring in the right ways.
Products above it should not need to care about unnecessary payment-provider detail. They should be able to make a request and receive a result they can use.
Keep the product-facing interface clear.
The calling product should not have to understand every provider-specific detail.
Keep provider logic in the payment layer.
That gives us one place to deal with differences underneath the products.
Give the calling product a dependable outcome.
It needs enough information to decide what happens next in its own workflow.
Make change cheaper.
The company should be able to improve the payment layer without rewriting every product that uses it.
07
Part of Truvenda, useful on its own
Karyopay starts inside the Truvenda ecosystem, but the product is not meant to exist only there.
Our own products give Karyopay real payment problems to solve from the beginning. At the same time, we're building it as a distinct product so its payment layer can make sense beyond one Truvenda application.
Karyopay