Lunch & Learn: How to Build Bill Pay Automation 101
Sign Up
Lunch & Learn: Building an Accounting Integration 101
Sign Up
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.

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.

1
User consent

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

Rutter User Consent Illustration
2
Platform selection

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

3
OAuthentication flows

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

4
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.

1
User consent

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

Rutter User Consent Illustration
2
Platform selection

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

3
OAuthentication flows

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

4
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.

Rutter Data Integrity Illustration
Rutter Data Security Illustration
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.

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.”

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.

1
User consent

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

Rutter User Consent Illustration
2
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.

3
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.

1
User consent

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

Rutter User Consent Illustration
2
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.

3
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.

Get up and running.

Building integrated products is hard. We can do that together. Let's chat.

By submitting your information, you agree to be contacted by a Rutter representative.
By submitting your information, you agree to be contacted by a Rutter representative.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.