PayU and Stripe in Kiero Store — payments connected to Kiero OMS

Checkout payment and order fulfilment are two stages of the same purchase. Kiero Store connects a PayU or Stripe payment to the order your team later handles in Kiero OMS.

What you get

Kiero Store processes payments through the provider you configure and sends confirmed orders to OMS. Payment status is based on a verified provider event.

What makes it useful

Checkout stays in the store, while your team fulfils the order in the shared OMS workspace. Configure PayU or Stripe accounts and keys in Kiero Store's panel; this is separate from the Stripe Sales channel. Verify the provider setup and a complete transaction before accepting live payments.

Why this matters in practice

Separating Store payments from Stripe Sales prevents two different order sources from being combined accidentally. Store owns its PayU or Stripe configuration, and OMS receives the order for fulfilment after the right event has confirmed payment. Warehouse staff work from an order rather than an ambiguous sign that checkout was merely started.

A typical workflow

The customer completes checkout in Store. After a verified provider notification, Store confirms payment and hands the order to OMS. Warehouse staff fulfil it alongside other channels without manually creating an order from a payment receipt.

Who it suits and how to start

This applies to Kiero Store and is not a standalone OMS payment integration. Configure keys and webhooks in the Store administration panel. Before going live, verify a complete transaction, refund and provider setup in the target environment.

Compare all integrations · Connection guides · Explore Kiero OMS