Core flow
KompiPay is the payment experience layer, not the whole stack
Stripe moves the money. KompiPay helps shape the payment moment. That means the integration pattern is usually straightforward: your app or site creates the payment, hands off to checkout, then uses real confirmation state for fulfilment or operational next steps.
This is especially useful for merchants with custom sites, imported catalogues, service-led flows, premium independents, or private client journeys.
What developers usually need to understand first
Create a payment
Generate a payment and checkout URL from your own site, app, or internal workflow.
Go deeperSend the link
Share payment anywhere: custom site flows, email, WhatsApp, DMs, proposals, or private client journeys.
Go deeperTrack payment state
Use operational payment status rather than relying only on front-end redirects or visible success states.
Go deeperKeep brand continuity
Use KompiPay as the payment experience layer on top of Stripe while keeping your own site and sales flow intact.
Go deeperWhy this model is useful for custom builds
Many teams do not want to rebuild their whole product around store logic. They already have the website, the product surface, the proposal flow, or the customer journey they want. What they need is a clean way to finish payment without losing trust or building an oversized payments layer in-house.
That is where KompiPay is most useful. It lets developers keep the surrounding product exactly where it is while improving the act of payment itself.
If you want the commercial framing behind that, read accept payments without an online store.
Good fit for developers
- Custom websites
- Service-led flows
- Private client journeys
- Premium one-off transactions
Main mental model
- Create payment
- Send or redirect to checkout
- Track real payment state
- Use that state for fulfilment and workflow
Frequently asked questions
Who are these docs for?
Developers, technical founders, agencies, and product teams integrating KompiPay into custom websites or internal payment workflows.
Do I need a storefront to integrate KompiPay?
No. KompiPay is especially useful when you already have a custom site or sales flow and simply want to improve the payment layer.
What is the main integration idea?
Create the payment, send or redirect to checkout, then rely on confirmed payment state to drive fulfilment and internal workflow.
Where should non-technical merchants start?
Usually with the product page, pricing page, and resources section before diving into technical setup details.