Processor Credentials

Each processor type requires different credentials in the options object when calling tagada.processors.create(). This page documents the exact fields for every supported gateway.

Supported Gateways

Stripe

Cards, wallets, APMs

NMI

Direct gateway

Checkout.com

Global payments

Airwallex

Multi-currency

Mastercard

Enterprise gateway

Authorize.Net

US gateway

Finix

Platform payments

N-Genius

Middle East

CCAvenue

India gateway

Ovri

EU gateway

KessPay

Alt. gateway

ConvesioPay

WordPress payments

Tap

MENA payments

TagadaPay

Managed payments

Sandbox

Testing

Common Structure

All processors share the same creation format — only the options differ:

const { processor } = await tagada.processors.create({
  processor: {
    name: 'My Gateway',
    type: 'stripe',           // ← processor type
    enabled: true,
    supportedCurrencies: ['USD', 'EUR'],
    baseCurrency: 'USD',
    options: { /* credentials — see below */ },
  },
});

Sandbox

Type: sandbox | Use for: Testing and development No real credentials required — the sandbox processor simulates a payment gateway.

options: {
  testMode: true,
}

For which operations and payment methods each processor supports, see the capability matrix.

Field	Type	Required	Description
`testMode`	boolean	No	Always treated as test mode
`forceDecline`	boolean	No	Force all payments to decline
`targetApprovalRate`	number	No	Simulate a specific approval rate (0–100)
`simulatedDelay`	number	No	Add artificial latency in milliseconds

See the Sandbox Testing Guide for a full walkthrough.

Stripe

Type: stripe | Where to find credentials: Stripe Dashboard → Developers → API Keys

options: {
  secretKey: 'sk_live_...',
  publicKey: 'pk_live_...',
  webhookSecret: 'whsec_...',
}

Field	Type	Required	Description
`secretKey`	string	Yes	Stripe secret key (`sk_live_...` or `sk_test_...`)
`publicKey`	string	Recommended	Stripe publishable key (`pk_live_...`)
`webhookSecret`	string	Recommended	Webhook signing secret (`whsec_...`)
`testMode`	boolean	No	Use Stripe test mode
`sendReceiptEmail`	boolean	No	Let Stripe send payment receipt emails
`descriptor`	object	No	Statement descriptor override (see Descriptor Fields)
`radar`	object	No	Enable Stripe Radar: `{ enabled: true, publishableKey: 'pk_...' }`
`apmSettings`	object	No	Alternative payment methods (Apple Pay, Google Pay, etc.)

Stripe Connect: If you’re connecting via OAuth instead of API keys, Stripe provides an accountId (e.g. acct_...). In this case you don’t need secretKey — TagadaPay handles the authentication. This is typically done through the TagadaPay dashboard, not the API.

NMI

Type: nmi | Where to find credentials: NMI Merchant Portal → Settings → Security Keys

options: {
  apiKey: 'your-nmi-security-key',
}

Field	Type	Required	Description
`apiKey`	string	Yes	NMI Security Key
`username`	string	No	NMI username (for certain integrations)
`password`	string	No	NMI password
`testMode`	boolean	No	Use NMI test mode
`merchantName`	string	No	Merchant name for 3DS
`merchantUrl`	string	No	Merchant URL for 3DS
`merchantCountryCode`	string	No	ISO country code for 3DS
`enable3DS`	boolean	No	Enable 3D Secure authentication
`useProcessorToken`	boolean	No	Use NMI’s tokenization
`descriptor`	object	No	Statement descriptor override
`acquirerBinVisa`	string	No	Acquirer BIN for Visa 3DS
`acquirerBinMastercard`	string	No	Acquirer BIN for Mastercard 3DS
`acquirerBinAmex`	string	No	Acquirer BIN for Amex 3DS
`acquirerBinDiscover`	string	No	Acquirer BIN for Discover 3DS
`acquirerBinJcb`	string	No	Acquirer BIN for JCB 3DS
`acquirerBinDinersClub`	string	No	Acquirer BIN for Diners Club 3DS
`acquirerBinCB`	string	No	Acquirer BIN for Carte Bancaire 3DS
`amexRequestorType`	string	No	Amex 3DS requestor type
`cbSiretNumber`	string	No	SIRET number for Carte Bancaire
`discoverClientId`	string	No	Discover 3DS client ID

Checkout.com

Type: checkout | Where to find credentials: Checkout.com Dashboard → Developers → Keys Supports two authentication modes:

Secret Key (recommended)
OAuth

options: {
  apiKey: 'sk_...',
}

Field	Type	Required	Description
`apiKey`	string	Yes	Checkout.com secret key
`sandboxed`	boolean	No	Use sandbox environment

options: {
  clientId: 'ck_...',
  clientSecret: 'sk_...',
}

Field	Type	Required	Description
`clientId`	string	Yes	OAuth client ID
`clientSecret`	string	Yes	OAuth client secret
`sandboxed`	boolean	No	Use sandbox environment

Airwallex

Type: airwallex | Where to find credentials: Airwallex Dashboard → Developer → API Keys

options: {
  clientId: 'your-client-id',
  clientApiKey: 'your-api-key',
  webhookSecret: 'your-webhook-secret',
}

Field	Type	Required	Description
`clientId`	string	Yes	Airwallex client ID
`clientApiKey`	string	Yes	Airwallex API key
`webhookSecret`	string	Yes	Webhook signing secret
`testMode`	boolean	No	Use Airwallex demo environment
`descriptor`	object	No	Statement descriptor override
`apmSettings`	object	No	APM config (Klarna, Afterpay, PayPal, etc.)

Mastercard Gateway

Type: mastercard | Where to find credentials: Mastercard Gateway Merchant Administration portal

options: {
  merchantId: 'your-merchant-id',
  password: 'your-api-password',
  gatewayUrl: 'https://your-gateway.mastercard.com/api/rest',
}

Field	Type	Required	Description
`merchantId`	string	Yes	Merchant ID from your Mastercard Gateway account
`password`	string	Yes	API password (not your login password)
`gatewayUrl`	string	Yes	Your gateway API URL (region-specific)
`apiVersion`	string	No	API version (defaults to latest)
`testMode`	boolean	No	Use test mode
`descriptor`	object	No	Statement descriptor override
`acquirerBinVisa`	string	No	Acquirer BIN for Visa 3DS
`acquirerBinMastercard`	string	No	Acquirer BIN for Mastercard 3DS

Authorize.Net

Type: authorizenet | Where to find credentials: Authorize.Net Merchant Interface → Account → API Credentials & Keys

options: {
  apiLoginId: 'your-api-login-id',
  transactionKey: 'your-transaction-key',
}

Field	Type	Required	Description
`apiLoginId`	string	Yes	API Login ID
`transactionKey`	string	Yes	Transaction Key
`clientKey`	string	No	Public client key (for Accept.js tokenization)
`testMode`	boolean	No	Use sandbox environment

Finix

Type: finix | Where to find credentials: Finix Dashboard → Settings → API Keys

options: {
  username: 'your-finix-username',
  password: 'your-finix-password',
  merchantId: 'your-merchant-id',
}

Field	Type	Required	Description
`username`	string	Yes	Finix API username
`password`	string	Yes	Finix API password
`merchantId`	string	Yes	Finix merchant identity ID
`sandboxed`	boolean	No	Use sandbox environment
`webhookSecret`	string	No	Webhook signing secret

Network Ngenius

Type: ngenius | Where to find credentials: N-Genius Online Portal → Settings → API Keys

options: {
  apiKey: 'your-api-key',
  outlet: 'your-outlet-reference',
  apiUrl: 'https://api-gateway.ngenius-payments.com',
}

Field	Type	Required	Description
`apiKey`	string	Yes	N-Genius API key
`outlet`	string	Yes	Outlet reference ID
`apiUrl`	string	Yes	API gateway URL (must end with a lowercase letter, no trailing slash)
`sandboxed`	boolean	No	Use sandbox environment

CCAvenue

Type: ccavenue | Where to find credentials: CCAvenue Merchant Portal → Settings → API Keys

options: {
  accessCode: 'your-access-code',
  workingKey: 'your-working-key',
  merchantId: 'your-merchant-id',
}

Field	Type	Required	Description
`accessCode`	string	Yes	CCAvenue access code
`workingKey`	string	Yes	CCAvenue working (encryption) key
`merchantId`	string	Yes	CCAvenue merchant ID
`testMode`	boolean	No	Use test mode

Ovri

Type: ovri | Where to find credentials: Ovri Back Office → Configuration → API

options: {
  apiKey: 'your-api-key',
  websiteKey: 'your-website-key',
  secretKeyPos: 'your-secret-pos-key',
}

Field	Type	Required	Description
`apiKey`	string	Yes	Ovri API key
`websiteKey`	string	Yes	Ovri website key
`secretKeyPos`	string	Yes	Ovri secret POS key
`testMode`	boolean	No	Use test mode

KessPay

Type: kesspay | Where to find credentials: KessPay Merchant Portal

options: {
  clientId: 'your-client-id',
  clientSecret: 'your-client-secret',
  username: 'your-username',
  password: 'your-password',
  sellerCode: 'your-seller-code',
  apiSecretKey: 'your-api-secret',
  publicKey: 'your-public-key',
}

Field	Type	Required	Description
`clientId`	string	Yes	KessPay client ID
`clientSecret`	string	Yes	KessPay client secret
`username`	string	Yes	KessPay API username
`password`	string	Yes	KessPay API password
`sellerCode`	string	Yes	Seller code
`apiSecretKey`	string	Yes	API secret key
`publicKey`	string	Yes	Public key
`testMode`	boolean	No	Use test mode
`notifyUrl`	string	No	Webhook notification URL

Tap

Type: tap | Where to find credentials: Tap Dashboard → goSell → API Keys

options: {
  apiKey: 'sk_live_...',
  merchantId: 'your-merchant-id',
}

Field	Type	Required	Description
`apiKey`	string	Yes	Tap secret API key
`merchantId`	string	Yes	Tap merchant ID
`testMode`	boolean	No	Use test mode
`descriptor`	object	No	Statement descriptor override
`threeDSecure`	boolean	No	Enable 3D Secure
`saveCard`	boolean	No	Allow saving cards for future payments
`receiptEmail`	boolean	No	Send receipt email via Tap
`receiptSms`	boolean	No	Send receipt SMS via Tap

Paysafe

Type: paysafe | Where to find credentials: Paysafe Merchant Portal

Field	Type	Required	Description
`apiKey`	string	Yes	API key (Base64-encoded `user:password` pair from the portal)
`accountId`	string	Yes	Card-payments account ID the charges run on

TagadaPay

Type: tagadapay-router | How it works: Managed payment processing by TagadaPay. The processor is provisioned for you when your processing account is approved — you never enter credentials for it.

options: {
  accountId: 'acct_...',
}

Field	Type	Required	Description
`accountId`	string	Yes	Your TagadaPay account ID
`testMode`	boolean	No	Use test mode
`descriptor`	object	No	Statement descriptor override

Contact TagadaPay support to enable this processor and get your account ID.

Descriptor Fields

Several processors support a descriptor object for customizing the statement descriptor shown on customer bank statements:

descriptor: {
  descriptor: 'MYCOMPANY',
  descriptor_suffix: 'Order',
  phone: '+1-555-0100',
  address: '123 Main St',
  city: 'New York',
  state: 'NY',
  postal: '10001',
  country: 'US',
  mcc: '5411',
  merchantId: 'MERCH001',
  url: 'https://mycompany.com',
}

All descriptor fields are optional. Not all processors support all fields — check your gateway’s documentation for supported descriptor options.

Full Example

Here’s a complete example connecting Stripe with all common options:

import Tagada from '@tagadapay/node-sdk';
const tagada = new Tagada('your-api-key');

const { processor } = await tagada.processors.create({
  processor: {
    name: 'Stripe US',
    type: 'stripe',
    enabled: true,
    supportedCurrencies: ['USD', 'EUR', 'GBP'],
    baseCurrency: 'USD',
    options: {
      secretKey: 'sk_live_...',
      publicKey: 'pk_live_...',
      webhookSecret: 'whsec_...',
      descriptor: {
        descriptor: 'MYSHOP',
      },
      radar: {
        enabled: true,
        publishableKey: 'pk_live_...',
      },
    },
  },
});

console.log('Created:', processor.id);

Next Steps

Merchant Quick Start

Full 7-step setup from processor to live checkout

Multi-PSP Routing

Connect multiple processors and cascade transactions

Sandbox Testing

Test payments without real money

​Processor Credentials

​Supported Gateways

Stripe

NMI

Checkout.com

Airwallex

Mastercard

Authorize.Net

Finix

N-Genius

CCAvenue

Ovri

KessPay

ConvesioPay

Tap

TagadaPay

Sandbox

​Common Structure

​Sandbox

​Stripe

​NMI

​Checkout.com

​Airwallex

​Mastercard Gateway

​Authorize.Net

​Finix

​Network Ngenius

​CCAvenue

​Ovri

​KessPay

​Tap

​Paysafe

​TagadaPay

​Descriptor Fields

​Full Example

​Next Steps

Merchant Quick Start

Multi-PSP Routing

Sandbox Testing

Processor Credentials

Supported Gateways

Common Structure

Sandbox

Stripe

NMI

Checkout.com

Airwallex

Mastercard Gateway

Authorize.Net

Finix

Network Ngenius

CCAvenue

Ovri

KessPay

Tap

Paysafe

TagadaPay

Descriptor Fields

Full Example

Next Steps