Explore storefronts, ticket sales, invoice payments, and contributions built with Inttegro SDKs. Try the customer journey, then follow the source from the form to the order and checkout.
Four sample businesses show how Inttegro fits into different products. Each web app offers embedded, modal, and hosted Checkout, so you can compare the payment experience around the same server-side order flow.
01 / Kora Market
From product to purchase.
Follow a product purchase through a branded storefront, customer details, and checkout. Next.js, Nuxt, Rails, and Laravel implementations show how that journey fits the framework you already use.
Trace how the server looks up the configured product and price, validates the customer’s details, and uses the SDK to create the order.
An event page leads into a guest reservation form and checkout. Explore the same ticket-purchase flow in Express, Django, and FastAPI, with attendee details carried into the Inttegro order.
See how a repeated submission keeps the same checkout attempt, how errors reach the guest, and where the customer returns after checkout or cancellation.
A focused invoice portal brings the amount, customer details, and payment action together. Go and Spring Boot implementations show how to connect a service invoice to Inttegro Checkout.
Follow the invoice reference into the order request and see how the app uses the hosted invoice URL returned by Inttegro.
Spring Boot’s setup guide includes a local Java SDK install. Use the Go demo for a hosted invoice walkthrough.
04 / Openfield
Turn support into a contribution.
A campaign page gives supporters a choice of contribution amounts before checkout. NestJS, RedwoodSDK, and Astro implementations connect that choice to a cause and its saved pricing rules.
Follow the suggested amounts through server validation. The Astro app also accepts a custom amount within the campaign’s configured limits.
Kora Market continues on iOS and Android with SwiftUI, Jetpack Compose, Flutter, and React Native with Expo. Each app uses the Inttegro SDK to present a native mobile-money payment sheet while keeping its own product browsing and checkout flow.
Follow the handoff from the shared Next.js backend to the payment sheet: the server creates the order, the app receives its ID, and the SDK handles payment entry and customer confirmation. Run the source on a simulator or device to explore the complete interaction.
Every demo includes the application source and setup instructions. Integration comments explain the consequential choices, link to the documentation, and describe when another approach may fit your product better.
01
Start with the customer’s task.
Choose a purchase, ticket reservation, invoice payment, or contribution. Follow the form, checkout, and return screens to see what your application needs to present around the payment.
02
Read how the order is created.
Find the server’s SDK call, input validation, catalog lookup, and retry behavior. The API key and order creation stay on the server; the browser or mobile app receives only what it needs to present checkout.
03
Connect it to your own business.
Use the demo’s setup guide with your own catalog and backend configuration. Add your application’s customer and order records, then verify the order’s payment state on your server before delivering the purchase.
Before you build.
What do I need to run a demo?
To connect a local web app to Inttegro, you need an account, a dedicated server API key, and the Product and Price IDs described in its setup guide. Each project includes its own dependency, run, and check commands. Cloud deployment options vary by framework; the guide shows the options packaged for that demo.
How do the three web checkout options differ?
Embedded Checkout appears within the app’s page. Modal Checkout opens in a dialog over it. Hosted Checkout takes the customer to the invoice page supplied by Inttegro. The demos use the same server order flow for all three, so you can compare presentation without changing how the purchase is created.
How do I try the mobile demos?
Build the app for a simulator or device and connect it to the companion backend. The mobile SDKs are publicly available; these demo projects currently reference local SDK directories, so follow their repository setup instructions. Expo requires a development build, and the Flutter example requires locally generated iOS and Android project files.
When should my application treat a payment as complete?
After your server checks the order’s recorded payment state. A browser return or payment-sheet callback helps your interface continue, but does not authorize fulfillment. The demos make that boundary explicit so you can connect payment confirmation to your own delivery, admission, or service workflow.
Make it yours
Your product. Built with Inttegro.
Create your account, choose the demo closest to your idea, and connect it to your own catalog. You’ll have an application to explore and the source to understand every step.