Copy page

Storefronts

A Storefront is a branded online store you stand up without writing any code. You pick a template, attach the products you sell, customize the look, and publish at a public slug like pay.kwiknkap.com/store/<slug>. Customers browse the page and pay you over Mobile Money right there, and the money settles into your Kwik Nkap merchant balance through the same collection engine that backs the public Payments API.

What a Storefront is

A Storefront is a hosted, multi-product web store. Where a payment link is a single shareable pay page for one thing, a Storefront is a full shopfront: a branded landing page, a product grid, and a hosted Mobile Money checkout, all served from one public slug.

Code
https://pay.kwiknkap.com/store/<slug>

The store is built from a few objects:

Concept	What it is
Template	A starting design with a type (ECOMMERCE), a theme, and default content and sections. Some templates are free; premium templates are purchased once.
Storefront page	The page you create from a template. It has a type, a public slug, a title, a description, and your customized theme and content.
Item	A sellable product on the page, referencing either a payment link or an inventory product.

Customers never need a Kwik Nkap account. They open the page, choose a product, and pay. You never have to build a checkout, host a site, or wire up a payment gateway.

Choosing a template

Every Storefront starts from a template. For an online store you use the ECOMMERCE template type, which gives you a product grid, product detail pages, and a hosted checkout wired for Mobile Money.

Free templates are usable immediately. For a premium template, the dashboard quotes an amount and you pay Kwik Nkap for it over Mobile Money, a platform collection from your own line. That purchase unlocks the template so a page can use it.

Adding products

Once you have a page, you add items to it. Each item references one of two things you already manage in Kwik Nkap:

• An existing payment link, reusing its amount, images, required fields, and pricing options.
• An inventory product, so the item is backed by real stock you track.

Because items are backed by payment links and inventory, the same pricing primitives carry over to the store:

Pricing option	What it does
Variants	Options for the same product, for example size or color, each with its own price.
Tiered (quantity) pricing	A price that changes with the quantity the customer buys.
Custom amount	A buyer-entered amount, validated against a configured minimum and maximum.
Base amount	The plain fixed price when no variant, tier, or custom amount applies.

Stock is tracked live from your inventory. The available quantity a customer sees is quantity - reservedQuantity, so products already reserved by pending checkouts are not oversold while a buyer is approving a prompt.

At checkout, the final price is resolved from the item's payment link: the base amount, the selected variant's price, the matching pricing tier, or a validated custom amount.

Branding the store

After the page exists you make it yours:

• Theme: edit colors and the overall look inherited from the template.
• Content and sections: edit the page copy and the default sections copied in from the template, and reorder items in the grid.
• Images: upload a logo, product images, and other media.

You can preview an unpublished page to check the theme and content before it goes live.

Publishing

A page stays private until you publish it. Publishing makes it reachable at its public slug:

Code
pay.kwiknkap.com/store/<slug>

After publishing, the hosted page is served to customers with your theme and content merged for their locale, and each item enriched with live price, stock, variants, and pricing tiers. You can keep editing and re-publishing as your catalog changes.

The customer checkout flow

Buyers pay over Mobile Money on the hosted checkout, with no account and no app to install.

1. The customer opens store/<slug>, browses the product grid, and selects a product, plus any variant or quantity.
2. The customer fills any required fields, enters their phone number, and picks an operator (MTN or ORANGE).
3. The checkout resolves the final price and initiates a Mobile Money collection. The customer approves the prompt on their phone with their PIN.
4. The hosted checkout polls the collection status until it settles. On success it may redirect to the success URL you configured.

Cart and invoice checkout

Instead of buying one product at a time, a customer can build a cart across multiple products. When they check out the cart, the store creates an invoice with a pay URL, and the customer settles the whole cart in one Mobile Money payment. This reuses the same invoice flow you would use for billing a customer directly.

How the money settles

All amounts are in whole XAF francs. There are two distinct money flows in this product:

1. The customer pays you. On a published store, the customer's Mobile Money payment is collected into your Kwik Nkap merchant balance. The final price is resolved from the item's payment link (base amount, variant, pricing tier, or an allowed custom amount); a cart checkout produces an invoice with a pay URL covering the whole cart.
2. You pay Kwik Nkap for premium templates. Buying a premium template runs a separate platform collection from your own Mobile Money line and unlocks the template for your pages.

Settled sales accrue to your merchant balance net of the application fee, the same way the public Payments API collections settle. Payouts from that balance are handled by Kwik Nkap's internal disbursement flow, not by this product.

Managing the store

Storefronts are built and managed in the dashboard, and the published pages are hosted on pay.kwiknkap.com. From the dashboard you can:

• Edit the page's theme, content, and item order, and re-publish.
• Add, remove, and reprice items as your catalog changes.
• Track sales: because every sale runs through the collection engine, paid and pending checkouts show up alongside your other transactions.

They reuse the same Mobile Money collection engine as the public Payments API, but the storefront, template, and item objects are not callable through the public developer API today.

Next steps

• See Payment links and Invoices, the building blocks that storefront items and cart checkout reuse.
• Selling event admission instead of products? See Events for ticketing pages.
• Read Payments & Collections to understand the collection lifecycle that settles every sale.