React Native

Overview

SDK Updates
New versions of the SDK are released frequently, not only to add new features and address issues in the SDK, but also to continuously improve the conversion of merchant login flows. As a result, it is strongly recommended that you frequently update your SDK version across any platforms where you invoke the SDK.

The Knot Link SDK provides a seamless way for end users to link their merchant accounts to your React Native app, serving as the foundation for Knot’s merchant connectivity platform. It is a client-side integration, consisting of initializing & configuring the SDK and handling events.

Installation

The Knot SDK can be installed using npm or yarn in your react-native project directory, like below

npm install react-native-knotapi --save

yarn add react-native-knotapi

From React Native 0.60 and higher, linking is automatic. If you need to manually install the SDK, run the below:

Shell

react-native link react-native-knotapi

Usage

Import methods like the below:

import {
  Knot,
  addKnotListener,
 } from "react-native-knotapi";

import {
  Knot,
  addKnotListener,
  type KnotError,
  type KnotEvent,
  type KnotExit,
  type KnotSuccess,
 } from "react-native-knotapi";

Initialization

Your backend will create a session by calling Create Session and provide it to your frontend. To start a Knot session, you must first configure the session with a KnotConfiguration class. The configuration allows you to set the environment, entry point, and other user experience configurations.

It’s expected that your integration with Knot will retrieve and pass a new session into the SDK on each initialization.

Configure the session

The SDK is configured using the following parameters inside the open method:

Name	Type	Description
sessionId	string	The session created by calling `/session/create` in your backend.
clientId	string	Your organization’s client ID. Note that this varies between `development` and `production` environments.
environment	string	The desired environment (`development` or `production`).
entryPoint	string	Optional. The specific entry point from within your app where you are initializing the Knot SDK (e.g. `onboarding`).
merchantIds	number[]	Optional. A list of merchant ID(s) to display. It is recommended to provide 0 or 1 merchant ID depending on your desired user experience.
useCategories	boolean	Optional. Whether to display merchant categories and therefore group merchants into categories for discoverability. Default: `true`.
useSearch	boolean	Optional. Whether to display the search bar, enabling users to search for merchants. Default: `true`.
domainUrls	string[]	Optional. Android only. A set of domains for which Knot should explicitly not clear cookies.
metadata	Record<string, string>	Optional. Custom key-value pairs to include in webhook payloads. Maximum 10 keys with string values up to 500 characters each.
locale	string	Optional. A BCP-47 language tag to set the locale for the SDK. Currently supported: `en-US`, `es-US`, `en-CA`, and `fr-CA`. If not provided, defaults to `en-US`.
product	string	Optional. Ignored in version 1.0.7+. The Knot product the session will inherit — the same as the type of session created (e.g. `card_switcher`, `transaction_link`).

`CustomerConfiguration`

This class is entirely optional and infrequently used, typically only when you offer Knot for multiple, differently-named card programs in the same app. The Knot team will set pre-defined values of your choosing for each parameter that you can then subsequently pass into the SDK. Passing a value that is not pre-defined will result in an onError callback. To take advantage of this functionality, please contact the Knot team who will be happy to assist you.

Name	Type	Description
cardName	String	Optional. The differentiated display name for the card product, used inside the Knot SDK (e.g. `Debit Card`, `Credit Card`). This value will override the default value `card`.
customerName	String	Optional. The differentiated display name for the company, used both as a standalone and prepended to the `cardName` (e.g. `Smart Bank`, `Payment Corp`). This value will override your default customer name value. Only recommended if you issue cards under multiple brands.
logoId	String	Optional. The differentiated logo for the company. This value will override your default logo.

See the following examples for how the parameters are used together in text inside the Knot SDK: "Your [customerName] [cardName | card] was added."

Open the session

To begin the flow, use the open method like below:

 Knot.open({
      sessionId: 'session_12345', // Current session ID
      clientId: 'client_67890', // Your client ID
      environment: 'development', // 'development' || 'production'
      entryPoint: 'onboarding', // Defined by you
      useCategories: true, // Recommend true
      useSearch: true, // Recommend true
      merchantIds: [52], // Recommend 0 or 1 merchant IDs
      domainUrls: ["https://domain1.com", "https://domain2.com"], // Uncommon
      metadata: { // Optional metadata for webhooks
        reference_token: 'your-token',
        trace_id: 'your-trace-id'
      },
      customerConfig: { cardName: 'Card Name', customerName: 'Customer Name', logoId: 'LogoId' },
      locale: 'es-US', // Optional BCP-47 language tag
    });

To test logging in to a merchant in the SDK, please reference a set of available test credentials for the CardSwitcher product here and the TransactionLink product here.

Single Merchant Flow

If you decide to use List Merchants to retrieve a list of merchants, list them in your app, and then open the SDK with a single merchant, you can do so by passing a merchant ID when configuring the session in the KnotConfiguration. More in Retrieving & Listing Merchants. The merchant ID is the same across all environments.

Although available, it is not recommended that you provide a long list of merchants in order to remove a few, but rather “hide” certain merchants that you desire from your Knot Dashboard.

Entry Points

In your app’s user experience, you may choose to integrate Knot in one or multiple places (e.g. from different tabs or screens). How users behave when interacting with Knot from each of these “entry points” may vary and it will be useful for you to be able to differentiate these groups of users by entry point in order to assess the value of each entry point. You can provide a value for the entry point when configuring the session in Knot.open. This value will be returned in the AUTHENTICATED webhook.

Categories & Search

Users are presented with a list of merchants in the SDK (unless you provide a single merchant as described above). Accompanying the list is a set of categories and a search experience. Each of these components is visible to users by default (as set in Knot’s backend). You can choose to remove either of them by setting useCategories: false and useSearch: false in Knot.open. This is not recommended.

Events

To receive updates from the SDK, implement the addKnotListener method.

const onKnotSuccess = addKnotListener('knot:onSuccess', (event) => {
  console.log('onSuccess', 'event', event);
});

const onKnotEvent = addKnotListener('knot:onEvent', (event) => {
  console.log('onEvent', 'event', event);
});

const onKnotError = addKnotListener('knot:onError', (event) => {
  console.log('onError', 'event', event);
});

const onKnotExit = addKnotListener('knot:onExit', (event) => {
  console.log('onExit', 'event', event);
});

const onKnotSuccess = addKnotListener('knot:onSuccess', (event: KnotSuccess) => {
  console.log('onSuccess', 'event', event);
});

const onKnotEvent = addKnotListener('knot:onEvent', (event: KnotEvent) => {
  console.log('onEvent', 'event', event);
});

const onKnotError = addKnotListener('knot:onError', (event: KnotError) => {
  console.log('onError', 'event', event);
});

const onKnotExit = addKnotListener('knot:onExit', (event: KnotExit) => {
  console.log('onExit', 'event', event);
});

The provided Typescript types can be found below:

export type KnotError = {
  errorCode: string;
  errorDescription: string;
  product?: 'card_switcher' | 'transaction_link';
};

export type KnotEvent = {
  event: string;
  environment: string;
  product?: string;
  merchantName: string;
  merchantId?: string;
  metaData?: Record<string, unknown>;
  product?: 'card_switcher' | 'transaction_link' | 'link';
  taskId?: string;
};

export type KnotSuccess = {
  merchant: string;
  product?: 'card_switcher' | 'transaction_link' | 'link';
};

export type KnotExit = {
  product?: 'card_switcher' | 'transaction_link' | 'link';
} | void;

`onSuccess`

This event is called when a user successfully logged in to the merchant and their card was switched. It takes a single string argument containing the name of the merchant.

`onError`

This event is called when an error occurs during SDK initialization and emits a KnotError with the following errors:

errorCode	errorDescription	Debugging Steps
Invalid_Session	The session is invalid.	Ensure `KnotConfiguration.environment` matches the environment the `sessionId` was created for (`development` or `production`).
Expired_Session	The session has expired.	Sessions are valid for 30 minutes. It is best practice to ensure that you create a new session every time a user invokes the SDK using Create Session.
Invalid_Client_Id	The client ID is invalid.	Verify that the value you are providing for `KnotConfiguration.clientId` is for the environment matching the value you are providing for `KnotConfiguration.environment` (i.e. `development` or `production`). If you provide your production `clientId` but set `environment: development`, you will experience this error.
Internal_Error	An internal error occurred.	Simply retry invoking the SDK with a new `sessionId`.
Merchant_Id_Not_Found	The merchant ID is required.	The `type` of `sessionId` you are providing on invokation of the SDK requires that you also provide a value in `KnotConfiguration.merchantIds` to ensure the user is directed to a specific merchant’s login flow in the SDK. You can retrieve a list of merchant IDs (the same in all environments) in List Merchants.
Invalid_Card_Name	The card name is invalid.	The value you are providing for `customerConfiguration.cardName` must exactly match an allowlisted value for your organization. Please reach out to the Knot team for access to this allowlist.
Invalid_Customer_Name	The customer name is invalid.	The value you are providing for `customerConfiguration.customerName` must exactly match an allowlisted value for your organization. Please reach out to the Knot team for access to this allowlist.
Invalid_Logo_Id	The logo ID is invalid.	The value you are providing for `customerConfiguration.logoId` must exactly match an allowlisted value for your organization. Please reach out to the Knot team for access to this allowlist.
Invalid_Locale	The locale is invalid.	The value you are providing for `locale` must be a valid BCP-47 language tag. Currently supported: `en-US`, `es-US`, `en-CA`, and `fr-CA`.

Sessions are valid for 30 minutes. If a session expires while the SDK is open, an expired session error will be emitted via onError and the SDK will automatically close. To provide a seamless experience, handle the REFRESH_SESSION_REQUEST event via the onEvent callback to proactively extend the session using Extend Session before expiration occurs.

`onExit`

This event is called when a user closes the SDK.

`onEvent`

This event is called when certain events occur in the SDK. With this callback, you will be able to understand how a user is progressing through their lifecycle of authenticating to a merchant. The following list contains all possible events emitted in the KnotEvent.event property:

Name	Purpose
REFRESH_SESSION_REQUEST	Emitted when the session used to initialize the SDK needs to be refreshed. Use Extend Session to extend the session before expiration occurs.
MERCHANT_CLICKED	Emitted when a user clicks on a merchant from the merchant list.
LOGIN_STARTED	Emitted when a user submits their credentials to login to the merchant.
AUTHENTICATED	Emitted when a user successfully logs in to the merchant.
OTP_REQUIRED	Emitted when a user needs to enter an OTP code to login to the merchant.
SECURITY_QUESTIONS_REQUIRED	Emitted when a user needs to enter answers to security questions to login to the merchant.
APPROVAL_REQUIRED	Emitted when a user needs to approve the login - often via a push notification or directly in the merchant’s mobile app - to login to the merchant.
ZIPCODE_REQUIRED	Emitted when a user needs to enter their zip code to login to the merchant.
DOB_REQUIRED	Emitted when a user needs to verify their date of birth to login to the merchant.
LICENSE_REQUIRED	Emitted when a user needs to enter their drivers license to login to the merchant.

Other Options

Get current SDK version

If you need to retrieve the current SDK version for your own use case, implement the following:

JavaScript

const sdkVersion = Knot.getSdkVersion();
console.log('Knot SDK Version:', sdkVersion ?? 'Unknown');

Close the SDK

If you need to explicitly close the SDK, use the below method, otherwise end users will naturally close the SDK as they interact with the interface.

JavaScript

Knot.close();

Maintain cookies

Android only.

Knot clears cookies for security purposes. If your app relies on cookies, you can allowlist specific domains using the domainUrls configuration in Knot.open. This is uncommon.

JavaScript

Knot.open({
  sessionId: 'session_12345', // Current session ID
  clientId: 'client_67890', // Your client ID
  environment: 'development', // 'development' || 'production'
  entryPoint: 'onboarding', // Defined by you
  useCategories: true, // Recommend true
  useSearch: true, // Recommend true
  merchantIds: [52], // Recommend 0 or 1 merchant IDs
  domainUrls: ["https://domain1.com", "https://domain2.com", .....],
  customerConfig: { cardName: 'Card Name', customerName: 'Customer Name', logoId: 'LogoId' },
  locale: 'es-US', // Optional BCP-47 language tag
})

General

SDK

CardSwitcher

SubscriptionManager

TransactionLink

Detect

Vaulting

Shopping

Merchant Account Linking

React Native

Overview

Installation

Usage

Initialization

Configure the session

`CustomerConfiguration`

Open the session

Single Merchant Flow

Entry Points

Categories & Search

Events

`onSuccess`

`onError`

`onExit`

`onEvent`

Other Options

Get current SDK version

Close the SDK

Maintain cookies

​Overview

​Installation

​Usage

​Initialization

​Configure the session

​CustomerConfiguration

​Open the session

​Single Merchant Flow

​Entry Points

​Categories & Search

​Events

​onSuccess

​onError

​onExit

​onEvent

​Other Options

​Get current SDK version

​Close the SDK

​Maintain cookies

Overview

Installation

Usage

Initialization

Configure the session

`CustomerConfiguration`

Open the session

Single Merchant Flow

Entry Points

Categories & Search

Events

`onSuccess`

`onError`

`onExit`

`onEvent`

Other Options

Get current SDK version

Close the SDK

Maintain cookies