How can I prevent the creation of duplicate merchant accounts?
The best way to prevent the creation of duplicate accounts will depend on your integration. Below are some common approaches based on how you onboard merchants:
- Creating accounts via the console: Before initiating the creation of a new account, utilize the search functionality to verify that the new account isn't a duplicate.
-
Creating accounts via the API: When creating a connected account via the API, your application should store the
account_id
from the response, along with an initial merchant application status ofincomplete
, wherever you store user information. This will help avoid the creation of duplicate merchant accounts. For example, you can create new columns fortilled_account_id
andtilled_application_status
in the user table of your database. Please note that if your application doesn't have a concept of a user at the time of the request to create a connected account, you may need to employ cookies or implement measures to prevent the use of duplicate emails. -
Using Tilled's hosted merchant application: If a user attempts to create a new application while their application status is
incomplete
, redirect the user to their merchant application's auth link. -
Using a custom merchant application: If a user attempts to create a new application while their application status is
incomplete
, you can pass theaccount_id
in a request to update their existing application.