Gateway Settings

Documentation Index

Fetch the complete documentation index at: https://partner-docs.nuwebgroup.com/llms.txt

Use this file to discover all available pages before exploring further.

​

Overview

Gateway settings control which payment processors are available across a reseller’s portfolio of companies. Payment gateways are configured at the reseller level and then assigned to individual companies — a company can only use gateways that its reseller has enabled. This follows the same reseller funnelling pattern as feature flags: gateways must be enabled on the reseller before they can be assigned to any of its companies.

​

Supported Gateways

The platform supports a wide range of payment processors. Gateways fall into two categories based on where their credentials are managed.

​

Reseller-Managed Gateways

These gateways have their credentials configured once at the reseller level. Companies connect to the reseller’s account — the specifics of how this works depend on the gateway.

​

Company-Managed Gateways

All other gateways require credentials to be configured at the company level. The reseller enables the gateway (making it available), but each company provides its own merchant credentials.

​

How Gateways Are Assigned

​

Reseller Configuration

Gateways are assigned to resellers during reseller setup or editing. Each reseller maintains a list of enabled gateways, along with any reseller-level credentials for reseller-managed gateways.

​

Company Configuration

When creating or editing a company in the hub, the gateway assignment step shows only the gateways enabled on the company’s reseller. Companies can be assigned one or more gateways. Each company gateway has several configuration options:

​

During Self-Service Registration

Companies created through self-service registration are automatically assigned the reseller’s first available payment gateway. The registering user does not select a gateway — it is inherited from the reseller.

​

Gateway Credentials

​

Reseller-Level Credentials

For reseller-managed gateways, credentials are configured at the reseller level. Companies connect to the reseller’s account, though some gateways may have additional configuration options at the company level.

​

Company-Level Credentials

For company-managed gateways, each company provides its own credentials. The specific fields vary by gateway but typically include API keys, merchant IDs, and secrets. Companies can view and update their gateway credentials from their admin Payment settings page. Some gateways also support additional credential fields such as:

• MOTO enabled — allows mail order / telephone order transactions
• Terminal enabled — supports card-present payments via connected terminals

​

Self-Managed Payment Mode

The Company self manage payment mode feature flag controls whether companies can switch their own gateway between live and test modes. When enabled, companies can toggle between modes from their admin settings without hub intervention.

​

Gateway Requirements

Some gateways impose additional requirements on the checkout experience: When a gateway with these requirements is enabled for a company, the corresponding data capture fields are automatically set to mandatory in the company’s checkout settings.

​

Gateways and Parent-Child Companies

Gateway configuration interacts with the parent-child company hierarchy:

​

Automatic Fee Collection

Reseller-managed gateways handle reseller fee collection automatically — fees do not need to be settled separately after the fact. How this works depends on the gateway:

​

Fee-Splitting Gateways

These gateways split each transaction at the point of payment, directing the reseller’s fee to the reseller and the remainder to the company’s sub-account:

​

Transfer-Based Gateways

Curlec (Razorpay) charges the full amount to the reseller’s account and then transfers the company’s portion (total minus reseller fee) to the company’s linked account. The reseller retains the fee by default. Transfers can also be disabled entirely, in which case all funds settle in the reseller’s account for manual distribution.

​

Nuvei

Nuvei uses the reseller’s merchant credentials with a per-company merchant site ID. Unlike the gateways above, no reseller fee amount is passed to Nuvei at the point of payment — fee collection is handled outside of the transaction API. The platform treats reseller fees as collected automatically for Nuvei transactions.

​

Refund Behaviour

When a refund is processed, gateways handle the previously collected fee differently:

• Stripe — by default, the application fee is reversed proportionally when a partial refund is issued, and fully reversed on a full refund.
• Ryft — on a partial refund, the platform fee is not reversed (the reseller retains the fee). On a full refund, the platform fee is reversed automatically.
• PayPal — fee reversal follows PayPal’s default refund policy.
• Curlec — the original transfer to the company is reversed (partially or fully) so the refund comes from the company’s funds rather than the reseller’s balance.
• Nuvei — refunds are issued via the reseller’s merchant credentials.

​

Company-Managed Gateways

Gateways where the company provides its own credentials (e.g. Adyen, QuickPay, Worldpay) do not support automatic fee collection. For these gateways, the reseller’s fee is tracked by the platform and settled separately through company invoices.

​

Webhook Configuration

Some gateways support webhooks for receiving real-time payment status updates from the processor. For gateways that require webhooks:

• The webhook URL is generated automatically based on the gateway type and the reseller’s domain
• Webhook events are configured per gateway during reseller setup
• The platform handles webhook signature verification and routing internally

​

Related Pages