Introduction to Layer

Instantly onboard millions of people from the Plaid Network with Layer (US only).

When a user provides their phone number, Plaid Layer checks whether they are part of the Plaid Network and verifies that they meet your onboarding requirements. Plaid Layer then authenticates the device and performs real-time risk analysis to reduce the risk of fraudulent sign-up attempts. After the user confirms their details and decides which financial account they want to share, you can verify their identity using your KYC provider and connect their accounts with Plaid.

The user enters their phone number within your application.

To get started with Layer, contact Sales to request Sandbox access.

1. Configure a Layer template via the Dashboard. A template is created by default on first visit. You can customize the template's name, set logo and colors to match your brand, and configure eligibility requirements. In general, fill rates for different user data identity fields are highly correlated with each other (i.e., if Plaid has access to one piece of user identity information, it very likely has access to all of them), so you should set "required" and "optional" eligibility requirements based on your true business needs.

2. Call /session/token/create with the template ID for the Layer template you configured. This will return a link object that contains a link_token.

3. On your client, create an instance of Link using the link.link_token string returned by /session/token/create. With Layer, you should create the Plaid handler object (i.e. via Plaid.create(...)) as early as possible so Link can pre-load in the background. This ensures the fastest possible experience for your users.

   If you have an existing Android integration that does not use a PlaidHandler or that uses OpenPlaidLink instead of FastOpenPlaidLink, or an existing React Native integration that uses PlaidLink instead of create and open, you will need to update your client-side Link opening code to take advantage of the new faster loading scheme. For details and sample code, see React Native: opening Link and Android: opening Link.

4. Once you have a user's phone number, pass it to the Plaid handler object: handler.submit({ "phone_number": "+14155550015"}). Link will quickly check if the user is eligible for Layer, and call the Link onEvent callback with either LAYER_READY or LAYER_NOT_AVAILABLE. Note that if the phone number uses a country code other than +1, the result will always be LAYER_NOT_AVAILABLE, as Layer does not support international phone numbers.

5. When you receive LAYER_READY, it means the user is eligible and you should call handler.open() to immediately present the Layer UI.

6. (Optional, recommended) If you receive LAYER_NOT_AVAILABLE instead, collect the user's date of birth and submit it via the same handler as earlier, e.g. handler.submit({ "date_of_birth": "1975-01-18"}). If you receive LAYER_READY, the user is eligible for Layer Extended Autofill and you should call handler.open() to immediately present the Layer UI; the flow continues at step 8. If you receive LAYER_AUTOFILL_NOT_AVAILABLE, the flow continues with the next step.

7. If neither Layer nor Layer Extended Autofill are available, you may discard the handler object and continue with any non-Layer flow in your app. For example, if your application falls back to a non-Layer product flow, you'd create a new Link token and handler to present that flow. If your non-Layer flow involves creating a Link token, include the phone_number when calling /link/token/create for a faster end user experience.

8. After you have launched the Layer flow in Link via handler.open(), the end user enters the Layer flow. You will receive a LAYER_AUTHENTICATION_PASSED webhook once Plaid has determined that the end user has demonstrated ownership of the phone number, via either OTP or SNA. If the end user does not fully complete the Link flow but you receive this webhook, you can skip any OTP phone number verification steps you would otherwise implement.

9. Once the end user has successfully completed the Layer flow in Link, you will receive an onSuccess callback. Use the received public_token with the /user_account/session/get API in order to retrieve the user's profile information and any linked Items.

For a walkthrough of integrating Layer, including sample code across multiple platforms, see Add Layer to your app.

As Plaid is actively adding new Layer functionality, it is strongly recommended that you use the latest SDK version and keep up to date with SDK updates if your app uses Layer.

If you are developing for the web using the JavaScript SDK, Plaid will automatically provide the latest available SDK. Otherwise, see libraries for links to the latest SDKs.

If you are developing a native mobile application, Layer requires SDK versions from June 2024 or later. Minimum versions are 6.0.4 (iOS), 4.5.0 (Android), 11.11.0 (React Native), and 3.5.2 (React). For Extended Autofill support, minimum versions are 6.3.1 (iOS), 5.3.0 (Android), 12.4.0 (React Native), and 4.1.1 (React).

Layer is not compatible with the Hosted Link integration mode.

Extended Autofill allows you to use the user's date of birth as a fallback for autofilling their identity data if their phone number is not Layer eligible. For Extended Autofill support, minimum SDK versions are 6.3.1 (iOS), 5.3.0 (Android), 12.4.0 (React Native), and 4.1.1 (React).

To use Extended Autofill, after receiving LAYER_NOT_AVAILABLE, submit the date of birth, e.g. handler.submit({ "date_of_birth": "1975-01-18"}). This must be in a separate call, made only after calling submit with the user's phone number. You will get either a LAYER_READY callback (success) or a LAYER_AUTOFILL_NOT_AVAILABLE callback (failure).

Extended Autofill is still subject to the same eligibility requirements that you defined in your Layer template. You may wish to make Collect financial accounts "Optional" instead of "Required" in your eligibility requirements, as Extended Autofill users are less likely to have connected account information.

When using Extended Autofill, in order to reduce onboarding friction, it is strongly recommended to prompt the user for their date of birth only after receiving LAYER_NOT_AVAILABLE, rather than requesting it upfront.

In Sandbox, the authentication code for all phone numbers is 123456. The basic test phone number is 415-555-0011, which will connect to a standard profile with full PII and two connected banks. The date of birth (for Extended Autofill testing) is 1975-01-18. The following phone numbers are all valid in Sandbox for Layer testing:

Note the area code is not the same in all of these test numbers.

In Production, the authentication step of Layer is dynamic and may authenticate the user via Silent Network Authentication, SMS OTP, or Passkeys (coming soon), depending on the user and the device; authentication checks such as trusted device matching or mobile carrier checks (for SIM swaps, port outs, etc.) are also run in Production.

Sandbox provides a simplified authentication experience: in Sandbox, users can only be authenticated via OTP, and authentication checks are not run.

To test Layer with specific combinations of account types, transactions, or other data, you can create a custom Sandbox user. To use this user in Layer:

• After launching Layer with an eligible phone number, on the Confirm details pane, click the edit button (the pencil icon) next to the Bank Account entry.
• Then select Add new account
• From there, complete the flow, logging in as your custom Sandbox user.
• When you complete Link and make API calls, you will see the custom Sandbox data you seeded.

To test Extended Autofill, you can follow one of two different scenarios:

• Submit any phone number that fails Layer eligibility completely, like 415-555-0000, with a template that specifies Collect financial accounts as Optional or Skip. The user will be eligible for Extended Autofill, and you will receive a full set of identity information.

• Submit any of the phone numbers above that are missing some identity information (such as 515-555-0017) while using a Layer template that requires that information. The user will not initially be eligible for Layer, but they will be eligible for Extended Autofill, because it will fill in the missing gaps in the user data. In this scenario, you will receive a full set of identity information and a connected bank account.

In both cases, submit 1975-01-18 for the user's date of birth.

In addition to the standard Link events, Layer has the following events:

For a full list of events, see the Link onEvent documentation.

The sections below illustrate typical frontend event sequences for different Layer scenarios. For more details on frontend events, see the Link onEvent documentation.

1LAYER_READY
2OPEN
3TRANSITION_VIEW: CONSENT
4TRANSITION_VIEW: VERIFY_PHONE
5TRANSITION_VIEW: PROFILE_DATA_REVIEW
6VERIFY_PHONE
7HANDOFF (with onSuccess callback)

1LAYER_READY
2OPEN
3TRANSITION_VIEW: CONSENT
4TRANSITION_VIEW: VERIFY_PHONE
5SUBMIT_OTP
6ERROR: INVALID_OTP
7SUBMIT_OTP
8ERROR: INVALID_OTP
9SUBMIT_OTP
10TRANSITION_VIEW: ERROR
11ERROR: PROFILE_AUTHENTICATION_FAILED
12EXIT (with onExit callback)

1LAYER_NOT_AVAILABLE
2LAYER_AUTOFILL_NOT_AVAILABLE

To track Layer performance, measure the following ratios:

Layer eligibility percentage: LAYER_READY event count / handler.submit(phone_number) count. Ensure you do not count handler.submit calls for date of birth. Layer conversion: onSuccess callback count (or HANDOFF event count) / OPEN event count

When using Layer, a billing event is incurred for each converted Link session (when onSuccess fires). You will not be billed for Layer eligibility checks or unconverted Layer sessions.