Skip to main content

Introduction

Knot’s Detect product enables you to detect and identify the merchant accounts for a given user, allowing you to then personalize your user experience.

Getting started

Start the flow

Access your dashboard

Ensure you have access to the Knot Dashboard and retrieve your client_id and secret to create an API key. Learn more about creating an API key and authentication to the API here.

Retrieve available merchants

Call List Merchants to retrieve a list of merchants that are available for merchant account detection by passing type = detect in the request. These are merchants you can allow users to link in your app and subsequently detect merchant accounts.You will be notified via the MERCHANT_STATUS_UPDATE webhook when/if the available merchant list changes, even if temporarily.

Create a session

With your API key for the development environment, call Create Session with type: link to create a session used when invoking the SDK. More here on how to create an API key.

Install the SDK

Install an SDK of your choosing, for example on iOS here and android here.

Initialize the SDK

Initialize the SDK with the session_id retrieved from Create Session and a merchant Id retrieved from List Merchants in KnotConfiguration or you can use merchant_id: 60for Apple to get started quickly. The SDK is where users will interact with the Knot UI to authenticate to various merchants. All login flows, including step-up authentication, are handled within the SDK. Users will see real-time feedback as they progress through authenticating with a merchant.

Login

In the development environment, login to a merchant account using user_good / pass_good credentials to link your user’s merchant account.

Handle webhook events

Subscribe to webhooks in the Knot Dashboard so your backend can be notified about user-generated, server-side events. Listen for the following events:
  • AUTHENTICATED: fired when the authentication to a merchant is successful and the merchant account is therefore successfully linked to Knot. Similarly and as applicable, listen to the client-side onEvent callback in the SDK to receive the authenticated event.
  • ACCOUNT_DETECTION_SUCCEEDED: fired when account detection succeeded.
  • ACCOUNT_DETECTION_FAILED: fired when account detection failed.

Identify detected accounts

When you receive the ACCOUNT_DETECTION_SUCCEEDED webhook, call Identify Detected Accounts to identify detected accounts for the user.