![]() ![]() You can create Checkbook processor_tokens in all three API environments: To Checkbook and they will use it to securely retrieve account and routing numbers from Plaid. Once you have identified the account you will use, you will send the access_token and account_id property of the account to Plaid via the /processor/token/create endpoint in order to create a Checkbook processor_token. When this setting is selected, the accounts array will always contain exactly one account. Set Account Select to "enabled for one account" in the Plaidĭeveloper Dashboard. Want the user to specify only a single account to link so you know which account to use with Checkbook, User, and may contain multiple accounts if the user has more than one bank account at the institution. The accounts array will contain information about bank accounts associated with the credentials entered by the Using the /item/public_token/exchange API endpoint. Exchange this public_token for a Plaid access_token On the metadata object, via the onSuccess callback. Instead, the Link module returns a public_token and an accounts array, which is a property The Link module handles the entire onboarding flow securely and quickly, but does not actually retrieve accountĭata for a user. Calling open will display the "Institution Select" view, calling exit will close Link, and calling destroy will clean up the iframe. Plaid.create accepts one argument, a configuration Object, and returns an Object with three functions, open, exit, and destroy. See the Link parameter reference for complete documentation on possible configurations. To see your client_id and secret, visit the Plaid Dashboard. ![]() For a full list of link_token configurations, see /link/token/create. Required parameters from your app server. Make a /link/token/create request with your client_id, secret, and a few other Is a short-lived, one-time use token that is used to authenticate your app with Link. In order to integrate with Plaid Link, you will first need to create a link_token. This step helps your end-users learn more how your product uses their bank information and is also required for connecting to some banks. If the integration is off, simply click the 'Enable' buttonįinally, you'll need to complete your Plaid Application Profile in the Dashboard, which involves filling out basic information about your app, such as your company name and website. To enable your Plaid account for the integration, go to the Integrations Next, verify that your Plaid account is enabled for the integration. To sign up for a Checkbook account, if you do not already have one. Plaid account for the Checkbook integration.įirst, you will need to work with the Checkbook team You'll need accounts at both Plaid and Checkbook in order to use the Utilizing Plaid + Checkbook enables a seamless workflow for sending and receiving payments. Verify a bank funding source via Checkbook's API without having to store any sensitive banking information. From there, you'll receive a PlaidĪccess_token and a Checkbook processor_token, which allows you to quickly and securely Your customers will use Link to authenticate with their financial institution and select theīank account they wish to use for payment transactions. Integration for the Plaid API that handles input validation, error handling, and multi-factorĪuthentication. You'll first want to familiarize yourself with Plaid Link, a drop-in client-side Checkbook's wide range of payment options - including ACH, real-time payments, push to card, virtual cards, and checks - enable customized payment solutions for every business need. With Plaid Link, users can quickly and securely onboard a bank account to natively issue payments through Checkbook’s API. Plaid and Checkbook have partnered to provide a seamless way to integrate Plaid’s instant account verification with Checkbook’s digital payment solution.
0 Comments
Leave a Reply. |