The problem we help solve
A clearer handoff. Less uncertainty.
An order is authorised but not captured, or a payment reaches the wrong outlet configuration. Staff then have to compare the store with the payment portal to decide what can be dispatched.
How BrownBag helps
We design the store connection around the N-Genius account and outlet that will process the transaction. Hosted checkout, supported plugins and direct integration are evaluated against the buying journey and your operational responsibilities.
From requirement to operation
Your N-Genius Online workflow
Map the outlet and payment action
Confirm the outlet reference, permitted currency and enabled account capabilities. Decide whether the order needs immediate purchase or a separate authorisation and capture step. Agree who can release, cancel or refund an order before configuring checkout.
Implement the selected checkout flow
Set up the approved server connection and preserve the N-Genius references against your order. Validate the configured secret header on webhook requests and evaluate the event, order action and payment state together. Connect these results and server-side status checks to a clear internal state model. A customer returning to the site should see the verified outcome, including a pending state when needed.
Exercise the full transaction lifecycle
Use the sandbox to test approval, decline, cancellation and interrupted returns. Include capture and refund cases where those actions are in scope. N-Genius currently sends each webhook once without retries, so test missed-event recovery through order-status checks and reconciliation. Prepare a staff checklist for incomplete transactions and the switch to live credentials.
What we can deliver
- Outlet, currency and purchase/capture workflow specification
- Connected checkout with payment and order reference mapping
- Lifecycle test record and operational go-live checklist
We agree the systems, responsibilities, acceptance checks and support arrangements before implementation begins.
Define the right scope
Network International controls live merchant onboarding, regional availability and enabled products. Sandbox access does not establish live eligibility. Webhook endpoints require provider approval and whitelisting; payloads are not signed, so we use the configured secret header to verify the sender. Direct card handling, saved credentials, recurring payments and additional outlets require an explicit account-supported scope.
Provider requirements and interfaces can change. We recheck the applicable documentation and account access when scoping your project.
Official N-Genius Online reference →Your questions, answered
Should we take payment immediately or capture it after checking stock?
That depends on fulfilment and your approved account capabilities. We map when stock is confirmed, who authorises capture and how cancellations are handled, then test the selected purchase or authorisation/capture flow before staff rely on it.
What should we include in the first brief?
Share your current store and systems, provider account status, target markets and the workflow you want to improve. Include typical volumes and the person responsible for operations. Do not send passwords, API keys or customer records.