Link Account - Testing in Sandbox

Testing for Link Account

The /link_account endpoint triggers the fuzzy name algorithm. Sila utilizes this algorithm to verify that the entity name, the user registered with, matches the account name associated with the linked bank account.

In the Sandbox, you can test the fuzzy name match algorithm against a pass and fail scenario.
When testing in Sandbox, failing the fuzzy name match will result in the linked account being frozen. You can use the no match trigger to simulate a frozen bank account.

UNHAPPY PATH: To test the scenario when the entity name does not match the account holder name, enter the information as shown below:

When testing in Sandbox, passing the fuzzing name match will result in the Account Owner Name matching the entity name. You can use the Test Usertrigger to simulate the passing account name.

HAPPY PATH: To test the scenario when the entity name matches the account holder name, enter the information as shown below:

🚧

Fuzzy Name Match and the /link_account response body

Within the response body of /link_account you may see the error message: "Bank account linked, but in a frozen state. Requires manual review." In the sandbox, frozen account will not be unfrozen.

Make a call /get_accounts where you'll see the following meta for the linked account: "match_score": 0.825, "account_owner_name": Test User, and "entity_name": Test User.
The account owner name is the name on the account provided by Plaid, while the entity name is the name of the person or business as provided to Sila through your request to /register. These two names need to closely match otherwise the account will not be useable.

If the match score is less than 0.73 the account will be frozen and not useable, and the users must provide proof they own the account or proof that they changed their name. They can also choose to link a different account.