Rutter Link

White labeled authentication with full data controls

Rutter Link is the end-user facing authentication flow. It handles the entire end-to-end process of authenticating, handling permissions, data governance, and monitoring consent.

Explore Documentation

MERCHANT FLOW

Merchant Authentication

Rutter Link begins when a user wants to connect their commerce platform, payment processor, ads platform, and/or accounting system to your product.

Get started with Rutter

User consent

The user agrees to a white labeled disclaimer screen and the Rutter End User Privacy Policy.

Platform selection

They select a platform they want to integrate with along with consenting to the associated permission that the B2B product is requesting.

A purple background with a selection of icons and text.

OAuthentication flows

Rutter Link presents the native authentication of the selected third party platform, which the user goes through.

Receive access token

Upon successful authentication, an access token, a unique never-expiring credential, is generated that allows the business to interact with the user’s data.

A purple background with a white button that says "Copy Access Token".

User consent

The user agrees to a white labeled disclaimer screen and the Rutter End User Privacy Policy.

Platform selection

They select a platform they want to integrate with along with consenting to the associated permission that the B2B product is requesting.

OAuthentication flows

Rutter Link presents the native authentication of the selected third party platform, which the user goes through.

Receive access token

Upon successful authentication, an access token, a unique never-expiring credential, is generated that allows the business to interact with the user’s data.

IRONCLAD INTEGRATION

Data Integrity

Rutter provides multiple checks both during syncs and periodically across the entire data set to ensure accuracy and quality of data. Entities are compare at the ID level, amounts are reconciled, deletes are logged, and all data is refreshed with a cadence of down to 5 minutes.

UNIFIED PROTECTION

Data Security

All data is AES 256 encrypted at rest and in transit. All webhooks are signed with a webhook signature to verify the sender. OAuth2.0 is user to verify the identity of the customer making an API request. Both Internal and external requests are audited. Rutter is SOC 2 Type 2, GDPR, and ISO 27001 compliant.

CENTRALIZED CONTROL

Authentication & Data Stewardship

Rutter offers maximum control of data shared between the end-users and customers of Rutter. Integration level permissions allow the end user to agree to the narrowest scope of data access when giving consent. Data sync configuration allows the product to configure the types and time range of data they have access to from Rutter after end-user consent is given.

A purple background with a client secret used in API requests.

Chief Technology Officer

SMB Line of Credit Provider

“We tried building it out ourselves and it was very slow. For each of these platforms, you have to start with the authentication and authorization. Additionally, if something with the API changed, we didn’t have the capacity to do it since we wanted to focus on building our core features that help us underwrite and offer funding to our merchants.”

Read Lenkie’s case study

B2B PRODUCTS

Setting up Rutter Link

Rutter Link is how merchants connect their accounts to your product. In order for B2B products to fine tune permissions and own their user data, they must customize Rutter Link with their own branding and third-party app credentials.

Get started with Rutter

User consent

The B2B product customizes their Rutter Link disclaimer screen with their own logo and branded text.

OAuthentication flows

For each platform they want to support, the B2B product signs in using their developer credentials, which allows Rutter to authenticate merchants on their behalf.

Configure permissions

The B2B product configures the permissions they are requesting from the merchant. These permissions will be displayed to the merchant during the Authentication flow.

A purple background with a white box that says "Amazon" on it.

User consent

The B2B product customizes their Rutter Link disclaimer screen with their own logo and branded text.

OAuthentication flows

For each platform they want to support, the B2B product signs in using their developer credentials, which allows Rutter to authenticate merchants on their behalf.

Configure permissions

The B2B product configures the permissions they are requesting from the merchant. These permissions will be displayed to the merchant during the Authentication flow.

RESOURCES