> ## Documentation Index > Fetch the complete documentation index at: https://docs.payrails.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code. > Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it. > Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code. > Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation. > Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent. > Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format. > Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code. # Network International > Connect Network International (N-Genius) to Payrails for cards and wallets, covering the outlet reference, API key and webhook. ![Network International logo](https://assets.payrails.io/img/logos/networkinternational/logo.svg) > [!NOTE] > > **Who should use this guide** > > This guide is intended for merchants who: > > * Use **Payrails** as a payment orchestrator > * Use **Network International** (N-Genius Online) for card and wallet processing > * Have access to the N-Genius portal *** ## Create a Network International integration in Payrails 1. Log in to the **Payrails** portal. 2. Go to **Settings** → **Integrations**. 3. Select **Add instance** to create a new integration configuration. 4. Select the **workspaces** where this integration should be available. > [!NOTE] > > **About workspaces** > > Workspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple workspaces. *** ## Step 1: Choose the integration type * Select **Payment**. * Continue to the next step. *** ## Step 2: Choose the provider * Select **Network International**. * Continue to the next step. ![A screenshot showing Network International selected as the provider.](https://mintcdn.com/payrails-42074109/95dm67yuCOH_Jo0o/images/docs/network-international-image-01.png?fit=max\&auto=format\&n=95dm67yuCOH_Jo0o\&q=85\&s=4d896e4a19764349579bf9fc2fef0ce7) *** ## Step 3: Configure your Network International integration > [!TIP] > > **What you'll need from Network International** > > Before you begin, make sure you can log in to the N-Genius portal. You'll copy your outlet reference and API key, and set up a webhook. *** ### Integration instance name > An integration instance is a specific payment provider setup in Payrails. You can create multiple instances for different regions, currencies, or business needs. Choose a clear, consistent name, as it is used in routing. **In Payrails** * Enter an **Instance name** for your integration, for example `merchant_ngenius`. ![A screenshot showing the integration instance name field.](https://mintcdn.com/payrails-42074109/145W1v58K5wnDMNC/images/docs/orchestration/integrations/shared/integration-instance-name.png?fit=max\&auto=format\&n=145W1v58K5wnDMNC\&q=85\&s=470be58979509680650b0cbf8b5eecc4) *** ### Account details **In N-Genius** * Go to **Settings** → **Organizational Hierarchy**, select your outlet in the left-hand panel and copy its reference. **In Payrails** | Field | Value | | :- | :- | | **Outlet Reference** | Your N-Genius outlet reference | | **Notification header key** | Optional. The name of the header N-Genius sends with each webhook, for example `Authorization`. Refer to [Webhooks or notifications](#webhooks-or-notifications). | | **Notification header value** | Optional. The value of that header. When you leave both empty, Payrails expects the `Authorization` header to carry your API key. | ![A screenshot showing the Network International account details fields.](https://mintcdn.com/payrails-42074109/95dm67yuCOH_Jo0o/images/docs/network-international-image-02.png?fit=max\&auto=format\&n=95dm67yuCOH_Jo0o\&q=85\&s=10b16f762cb1cabdf1352fae7f16fc75) *** ### Credentials **In N-Genius** * Go to **Settings** → **Integrations** → **Service accounts** and create or copy an API key. **In Payrails** | Field | Value | | :- | :- | | **API Key** | Your N-Genius API key | Payrails sends requests to the N-Genius sandbox in test mode and to the live environment in live mode, so use the API key for the matching environment. ![A screenshot showing the Network International credential fields.](https://mintcdn.com/payrails-42074109/95dm67yuCOH_Jo0o/images/docs/network-international-image-03.png?fit=max\&auto=format\&n=95dm67yuCOH_Jo0o\&q=85\&s=d60840079c76dc87b4492b33f8886a43) *** ### Payment methods **In Payrails** * Select **Card**, **Apple Pay**, **Google Pay** or any combination. ![A screenshot showing the Network International payment method selection.](https://mintcdn.com/payrails-42074109/95dm67yuCOH_Jo0o/images/docs/network-international-image-04.png?fit=max\&auto=format\&n=95dm67yuCOH_Jo0o\&q=85\&s=94e50bd860fe39609e655217d2c4e745) *** ### Webhooks or notifications > [!NOTE] > > Payrails uses provider webhooks or notifications to receive asynchronous > payment status updates. > [!WARNING] > > Create webhooks in the same mode (test or live) as your Payrails integration. **In Payrails** * Copy the **Notification URL** shown under **Account configuration** at the top of the integration form. **In N-Genius** 1. Go to **Settings** → **Integrations** → **Webhooks** and add a webhook with the Payrails notification URL. 2. Add a custom header: use the same key and value you entered in **Notification header key** and **Notification header value**. 3. Save the webhook. *** ## Request fields for Network International Send these fields in the [authorize request](https://docs.payrails.com/reference/authorizeaction.md) for card payments, in addition to the standard authorize fields. **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to Network International when you include them. For more about meta fields, refer to [Meta fields](https://docs.payrails.com/docs/orchestration/meta-fields.md). | Field | Status | Description | | :- | :- | :- | | `amount` | Required | Sent to N-Genius in minor units, with the currency. | | `meta.customer.name`, `meta.customer.lastName` | Required | Sent as the billing first and last name. You can send `meta.order.billingAddress.name` and `lastName` instead. | | `meta.clientContext` | Required | When N-Genius runs 3D Secure. Send `ipAddress`, `userAgent`, `acceptHeader`, `language`, `timeZoneOffset`, `colorDepth`, `screenHeight`, `screenWidth`, `javaEnabled` and `javaScriptEnabled`, sent as browser details. | | `instrument.holderName` | Optional | Sent as the card holder name. | | `meta.order.billingAddress` | Optional | Sent as the billing `street`, `city` and `country.code`. | | `meta.customer.email` | Optional | Sent as the order email. | *** ## Enable the integration **In Payrails** * Select **Save account** to enable the integration. * Confirm the integration shows as **Enabled**. Your **Network International** integration is now ready to process payments. *** ## Next steps 1. Run a test payment using an N-Genius [test card](https://docs.ngenius-payments.com/reference/sandbox-test-environment). 2. Verify that: * The payment appears in the N-Genius portal. * The payment status updates correctly in Payrails. 3. Once verified in test mode, repeat the setup in live mode. → Continue to: [Test a payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/test-payments.md) ## Related topics - [Android SDK API Reference](https://docs.payrails.com/docs/sdks/android/api-reference.md) - [Support co-branded cards](https://docs.payrails.com/docs/sdks/android/co-branded-cards.md) - [Android SDK concepts](https://docs.payrails.com/docs/sdks/android/sdk-concepts.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.