Storefront payment control

Keep the payment connected to the sale, customer and stock movement.

A bank alert is not enough to explain which order was paid, what stock should move, or whether fulfilment can begin. IGFirstERP storefront checkout supports configured Paystack card, dedicated transfer, and manual transfer paths while retaining the order, amount, customer, payment state, and review context.

Payment collection and payment control are different. The provider moves money; IGFirstERP keeps the business record around the money and exposes what still needs verification.

Find my plan Book an Operations Fit Call

Published 2026-07-11 · Verified 2026-07-11 · Editorial policy

Quick fit signal

Use this path when online payments arrive but staff still match alerts to orders by hand or begin fulfilment before payment status is clear.

The operator says: “The customer says they paid, but we cannot quickly match it to the order.”
The control needed: Configured channel, order reference, customer, amount, currency, provider response, payment state, and fulfilment gate.
The owner verifies: Which order was paid, by which path, for what amount, whether confirmation succeeded, and what remains pending.

Decision points before a demo

What the owner needs to know

What record is created?

Checkout retains an order or payment intent with customer, amount, currency, selected payment channel, reference, and status.

What else changes?

Confirmed payment can advance the supported order and fulfilment path; pending or manual payment remains visible for verification.

What can management verify?

Managers can review payment-profile readiness, channel availability, references, status, webhook result, and manual-transfer evidence where configured.

Best fit

Nigerian storefronts using a verified tenant-owned Paystack setup.
Businesses that want card, supported dedicated transfer, or manual transfer attached to an order record.
Teams that need payment status visible before fulfilment proceeds.

Probably not fit yet

An unverified claim that Nomba is integrated.
Assuming every currency is supported by every configured payment channel.
Treating a screenshot or customer message as final provider confirmation.

Why it returns

Payment alerts lose the order context

When money and orders live in separate places, staff search names, amounts, chats, and screenshots before deciding whether to release goods. That delay also creates room for mistakes.

Keep provider reference and order reference connected.
Retain customer, amount, currency, channel, and status.
Separate confirmed payment from manual evidence awaiting review.

Supported paths

Configure the payment paths the business can actually operate

The storefront payment profile exposes Paystack card, dedicated virtual account transfer, and manual transfer options according to verified setup and channel readiness.

Use tenant-owned Paystack keys and verification.
Show manual transfer instructions only when configured.
Keep channel availability and provider responses reviewable.

Fulfilment control

Do not release an order from a payment screenshot alone

Payment state should remain attached to the order and the fulfilment decision. Pending, failed, manually evidenced, and confirmed paths require different operating actions.

Verify the supported provider result.
Review manual-transfer evidence and instructions.
Investigate unmatched or failed payment work before dispatch.

Demonstration workflow · not customer data

Trace one storefront payment

Demonstration data uses an NGN storefront order, a configured tenant Paystack profile, and card, dedicated transfer, and manual transfer options.

Step 1

Prepare the order

Retain customer, items, amount, currency, shipping selection, and order reference.

Step 2

Choose a channel

Initialize a configured card or transfer path, or show approved manual transfer instructions.

Step 3

Record the result

Keep provider reference, response, status, and manual evidence where applicable.

Step 4

Release or investigate

Advance fulfilment only when the business payment rule is satisfied; otherwise retain the exception.

What the owner can verify

Payment-profile verification and channel readiness are explicit.
Each payment attempt remains tied to customer, order, amount, currency, reference, and status.
Manual and provider-confirmed paths are not presented as the same evidence.

When the happy path fails

Failed or pending provider work remains reviewable instead of silently marking the order paid.
Webhook signature and provider verification protect supported confirmation paths.
Manual transfer stays pending until the business completes its verification process.

Explicit limitations

What this page does not promise

Nomba is not published as an integrated provider without verified product evidence.
Dedicated virtual account support is scoped to the provider and currency configuration currently available.
Provider uptime, settlement, disputes, refunds, chargebacks, exchange, and regulatory obligations remain subject to the payment provider and business process.

Operational proof, not vanity claims

These proof assets show what became visible, traceable, faster, or easier to review after IGFirstERP was implemented. Named customer metrics are used only where permission has been granted. Results vary by operating discipline, data quality, implementation scope, and adoption.

Proof library Named customer evidence Review what became traceable, visible, or easier to control, with limitations stated. Methodology How claims are governed See the evidence, permission, review-date, and limitation rules behind public claims. Product Walk through the operating system See how stock, sales, staff, storefronts, and reporting connect.

Control hub Start from the operating problem Find the stock, staff, branch, website, or reporting problem that keeps returning. Academy Operator education Use practical lessons to strengthen the process around the system. Documentation Product guides and SOPs Review current operating instructions for IGFirstERP workflows.

Questions serious buyers ask

Which online payment provider is verified here?

The current verified storefront paths use tenant-owned Paystack configuration for supported card and dedicated-transfer flows, alongside configurable manual transfer.

Does IGFirstERP currently integrate Nomba checkout?

This page does not claim a Nomba integration because a current production integration has not been verified for this public release.

Can the storefront collect every international currency?

No universal currency claim is made. Currency support depends on the business configuration, channel, provider, settlement setup, and country scope.

Operations Fit Call

Choose the path that fits your operation

Use Find my plan when the workflow is clear. Book an Operations Fit Call when locations, integrations, migration, permissions, or reporting need to be mapped first.

Book an Operations Fit Call