Linking accounts and creating transfers

Before initiating a transfer through Plaid, your end users need to link a bank account to your app using Link, Plaid's client-side widget. Link will connect the user's account and obtain and verify the account and routing number required to initiate a transfer. Supported account types are debitable checking, savings, or money-market accounts.

See the Link documentation for more details on setting up a Plaid Link session. At a high level, the steps are:

1. Call /link/token/create, specifying transfer in the products parameter.

2. Initialize a Link instance using the link_token created in the previous step. For more details for your specific platform, see the Link documentation. The user will now go through the Link flow.

3. The onSuccess callback will indicate the user has completed the Link flow. Call /item/public_token/exchange to exchange the public_token returned by onSuccess for an access_token. You will also need to obtain and store the account_id of the account you wish to transfer funds to or from; this can also be obtained from the metadata.accounts field in the onSuccess callback, or by calling /accounts/get. You will use the account_id later, when authorizing the transfer, to specify which account to credit or debit.

Once a Plaid Item is created through Link, you can then immediately process a transfer utilizing that account or initiate the transfer at a later time.

The following Link configuration options are commonly used with Transfer:

• Account select: The "Account Select: Enabled for one account" setting configures the Link UI so that the end user may only select a single account. If you are not using this setting, you will need to build your own UI to let your end user select which linked account they want to use with Transfer. When using Transfer UI, this setting is mandatory.
• Embedded Institution Search: This presentation mode shows the Link institution search screen embedded directly into your UI, before the end user has interacted with Link. Embedded Institution Search increases end user uptake of pay-by-bank payment methods and is strongly recommended when implementing Transfer as part of a pay-by-bank use case where multiple different payment methods are supported.

When making debit transactions, it is important to collect and store Proof of Authorization (POA) for NACHA compliance and to dispute return requests if necessary. Transfer UI contains a built-in flow that captures NACHA-compliant POA. If not using Transfer UI, you must collect your own POA. For more details on best practices for collecting and storing POA, see NACHA guidance.

If an end user claims that a transaction is unauthorized and initiates a return request, their bank may contact Plaid to request a POA. POA requests will only ever be sent to Plaid, and not directly to you. Plaid will then contact you to request any additional information needed. You can provide this information via the Tasks pane in the Dashboard.

If you are migrating from another payment processor and would like to import known account and routing numbers into Plaid, planning to implement a custom account linking UI, or intend to use wire transfers as a payment rail, contact your account manager about using the /transfer/migrate_account endpoint. This endpoint can be used to import previously-verified account and routing numbers and will return an access_token and account_id for a given account and routing number pair. Items created in this way will always have an authorization decision rationale of MIGRATED_ACCOUNT_ITEM, since Plaid will be unable to assess transfer risk for these Items. This endpoint is not enabled by default; to request access, contact your Plaid Account Manager or Support.

To see if an institution supports Transfer, use the institution status page in the Dashboard or the /institutions/get endpoint. If an institution is listed as supporting Auth, it will support Transfer.

Transfer supports all of the same flows as Auth, including the optional micro-deposit and database-based flows, which allow you to increase the number of supported institutions and provide pathways for end users who can't or don't want to log in to their institutions. Items created with Same Day micro-deposits, Database Insights, or Database Match will always have an authorization decision rationale of MANUALLY_VERIFIED_ITEM, since Plaid will be unable to assess transfer risk for these Items. For more details about these flows and instructions on implementing them, see Full Auth coverage.

Before creating a transfer, transfers must pass a risk check and be authorized by Plaid's authorization engine. By default, the engine will run compliance checks including regulatory and program factors such as rate limits, prohibited accounts, suspicious behavior, etc. These will only decline a small portion (<1%) of account and routing numbers. For debit ACH, the account balance is also checked to ensure there are sufficient funds to complete the transfer.

To use Plaid's authorization engine, call /transfer/authorization/create. You will be required to specify the access_token and account_id from the account linking step, as well as a user.legal_name, the transaction amount, the type of the transaction (debit or credit), and the transaction network (ach, same-day-ach, rtp, or wire -- to request wire transfers, contact your Account Manager). For ACH transfers, an ach_class is also required. An idempotency_key is also strongly recommended to avoid creating duplicate transfers (or being billed for multiple authorizations). If you are a Platform Payments (beta) customer, you will also include an originator_client_id. For more details on these parameters, see /transfer/authorization/create in the API Reference.

Plaid will return 'approved', 'declined' or 'user_action_required' as the authorization decision along with a decision_rationale and the authorization_id. If the transaction is approved, you can proceed to Initiate the transfer. Approved authorizations are valid for 1 hour by default, unless otherwise configured by Plaid support. You may cancel approved authorizations through the /transfer/authorization/cancel endpoint if you no longer intend to use the authorization. Denied authorizations will have a code and description in the decision_rationale object that provide additional insight.

To avoid blocking transfers, /transfer/authorization/create may authorize transfers as approved in circumstances where Plaid can't accurately predict the risk of return. Always monitor the decision_rationale to understand the full risk of a transfer before proceeding to the submission step.

If the authorization decision is user_action_required, see Handling user action required.

See the table below to understand different scenarios of authorization decisions.

If your organization has your own set of rules you would like to use for transfer authorization logic, you can configure a custom ruleset via the Dashboard.

The ACH Standard Entry Class (SEC) code is represented in the Plaid API by the ach_class field and is required for all ACH transfers. SEC codes indicate the type of authorization the originator received in order to submit an ACH payment instruction into the ACH network. Using the incorrect code can result in a failed transfer authorization, ACH returns outside of the expected return window, or, if not remedied, eventual loss of access to Transfer.

Plaid permits only the following SEC codes to be utilized for ACH Transfers:

Transfer customers are approved for SEC codes based on the information supplied in the Transfer application. If an unapproved or unsupported SEC code is submitted, the transfer authorization request will fail with the error TRANSFER_FORBIDDEN_ACH_CLASS.

SEC code definitions:

ccd - Corporate Credit or Debit. The transfer moves funds to or from a business bank account

ppd - Prearranged Payment or Deposit. The transfer is part of a pre-existing relationship with a consumer. Authorization was obtained from the consumer in person via writing, or through online authorization, or via an electronic document signing, e.g. Docusign. For example language for online authorization, see the 2025 NACHA Operating Rules — Section 2.3.2, Authorization of Entries via Electronic Means. Can be used for credits or debits.

tel - Telephone-Initiated Entry. The transfer debits a consumer's bank account. Debit authorization has been received orally over the telephone via a recorded call.

web - Internet-Initiated Entry. The transfer debits a consumer’s bank account. Authorization from the consumer is obtained over the Internet (e.g. a web or mobile application). Can be used for single debits or recurring debits.

SEC codes and ACH returns

SEC codes determine how long Receiving Depository Financial Institutions (RDFIs, i.e. counterparty banks) have to submit ACH returns for the transfers. ACH debit transfers labeled with consumer SEC codes (web, tel) permit RDFIs to submit unauthorized returns (R07, R10, R11, etc.) for up to 60 days after the effective date of the transfer, even if the debit was to a business bank account. If a consumer account is debited using a business SEC code (ccd), the RDFI can return the transfer for up to 60 days with an R05 return code because is it not proper to debit consumers using a business SEC code.

Sometimes Plaid needs to collect additional user input in order to properly assess transfer risk. The most common scenario is to fix a stale Item. In this case, Plaid returns user_action_required as the authorization decision. To complete the required user action:

1. Create a new link token via /link/token/create. Instead of providing access_token, you should set transfer.authorization_id in the request.
2. Initialize Link with the link_token. Link will automatically guide the user through the necessary steps.
3. You do not need to repeat the token exchange step in Link's onSuccess callback as the Item's access_token remains unchanged.

After completing the required user action, you can retry the /transfer/authorization/create endpoint with the same request body. You can even reuse the same idempotency_key as idempotency does not apply to user_action_required authorizations.

After assessing a transfer's risk using the authorization engine and receiving an approved response, you can proceed to submit the transfer for processing.

Pass the authorization_id, access_token, account_id, and a description (a string that will be visible to the user) to the /transfer/create endpoint. To make a transfer for less than the amount authorized, provide an optional amount; otherwise the transfer will be made for the full authorized amount. The authorization_id will also function similarly to an idempotency key; attempting to re-use an authorization_id will not create a new transfer, but will return details about the already created transfer. You can also provide the optional field metadata to include internal reference numbers or other information to help you reconcile the transfer.

/transfer/create will return transfer_id as well as the transfer_status. All transfers begin in a pending status. This status changes as the transfer moves through the payment network. Whenever the status is updated, a Transfer event will be triggered. To learn more about tracking the status of the transfer, see event monitoring.

If submitting a credit transfer, you must have enough funds in your Ledger balance to cover the transfer amount.

If you receive a retryable error code such as a 500 (Internal Server Error) or 429 (Too Many Requests) when calling /transfer/create, you should retry the request; Plaid uses the authorization_id as an idempotency key, so you can be guaranteed that retries to /transfer/create will not result in duplicate transfers.

Initiating an Instant Payout transfer via RTP or FedNow works the same as initiating an ACH transfer. When initiating an Instant Payout transfer, specify network=rtp when calling /transfer/authorization/create. rtp as the network refers to all real time payment rails; Plaid will automatically route between Real Time Payment rail by TCH or FedNow rails as necessary.

Roughly ~70% of accounts in the United States can receive Instant Payouts. If the account is not eligible to receive an Instant Payout, /transfer/authorization/create will return an INVALID_FIELD error code with an error message that the account is ineligible for Instant Payouts. If you'd like to see if the account is eligible for Instant Payouts before calling /transfer/authorization/create, use the /transfer/capabilities/get endpoint.

Only credit style transfers (where you are sending funds to a user) can be sent using Instant Payout transfers.

To send a wire to a recipient end-user, you must first create an Item for the recipient using the /transfer/migrate_account endpoint and provide a wire_routing_number in addition to the routing_number. Wire routing numbers should be collected directly from end users. While the routing number for a wire payment is often the same as the routing number for an ACH payment, some institutions have different wire routing numbers. Tokenized account numbers, such as those used at Chase and PNC, cannot be used for wire transfers, so account numbers must be collected directly from end users at institutions that use TANs.

Authorization requests sent with a network of wire will only be attempted via wire and will not fall back to any other payment method. Only transfers of type credit can be sent using wire transfers.

Wire processing hours through Plaid's banking partners are between 9am ET and 5pm ET. The same-day cutoff time for wire initiation to Plaid is 4:30pm ET; wires submitted after that time will be processed on the next business day.

The transaction limit for a wire is $999,999.99. Authorization requests sent with an amount greater than $999,999.99 will fail.

Wire transfers may be subject to an incoming wire transfer fee from the recipient's bank, which is typically deducted by the bank from the amount received by the recipient. In the rare instance that a wire is rejected by the receiving bank (RDFI), you will be returned the original wire transfer amount, less a return fee (if any) from the receiving bank. The status of an RDFI-rejected wire will be RETURNED with failure code REVERSAL and a failure reason description supplied by the banking partner.

Wire transfers may be subject to an incoming wire transfer fee from the recipient's bank, which is typically deducted by the bank from the amount received by the recipient. In the rare instance that a wire is rejected by the receiving bank, you will be returned the original wire transfer amount, less a return fee (if any) from the receiving bank.

Transfers that are submitted via the /transfer/create endpoint will be submitted in the next processing window. For a same-day transfer, the cutoff time for the last window of the day is 3:30PM Eastern Time. For a next-day transfer, the cutoff time is 8:30PM Eastern Time. It is recommended to submit a transfer at least 15 minutes before the cutoff time to guarantee that it will be processed before the cutoff.

Note that same-day transfers submitted after 3:30PM Eastern Time and before 8:30PM Eastern Time will be automatically updated to be next-day and submitted to the network in that following ACH processing window. This update applies to sweeps as well. This process minimizes the risk of return due to insufficient funds by reducing the delay between Plaid's balance check and the submission of the transfer to the ACH network. The settlement time remains the same as it would have been if the transfer had been submitted in next same-day window.

ACH processing windows are active only on banking days. ACH transfers will not be submitted to the network on weekends or bank holidays. Any transfer created when an ACH processing window is closed will automatically be submitted to the network at the opening of the next processing window.

See the flow of funds overview for more details on how, and when, funds move.

Each bank has discretion in how they format an ACH, RTP, or FedNow transaction in their bank statements. The most common pattern used is [Company Name] [Phone Number] [Transfer Description].

• [Company Name] is the name provided in your Transfer application. This must match a legally registered name for your company.

• [Phone Number] is the phone number that you provided in your Transfer application.

• [Transfer Description] is the string that you passed into the description field of your /transfer/create request.

To request a change to your phone number or company name, file a support ticket.

To cancel a previously created transfer, use the Dashboard, or call the /transfer/cancel endpoint with the appropriate transfer_id. Note that once Plaid has sent the transfer to the payment network, it cannot be canceled. Practically speaking, this means that Instant Payouts via RTP/FedNow cannot be canceled, as these transfers are immediately sent to the payment network. You can check use the cancellable property found via /transfer/get to determine if a transfer is eligible for cancelation.

If the transfer is not cancellable, you may be able to undo it in another way. For undoing debit transfers, see refunds. For information on undoing an ACH credit transfer, see ACH investigations.

There are two types of bank accounts in the Plaid Transfer system.

The first is a consumer checking, savings, or cash management account connected via Plaid Link, where you are pulling money from or issuing a payout to. In the Transfer API, this account is represented by an access_token and account_id of a Plaid Item. A "transfer" is an intent to move money to or from this account.

The second type of account involved is your own business checking account, which is linked to your Plaid Ledger. This account is configured with Plaid Transfer during your onboarding by using the details provided in your application. A "sweep" pushes money into, or pulls money from, a business checking account. For example, funding your Plaid Ledger account by calling /transfer/ledger/deposit will trigger a sweep event.

To learn about all the different ways you can trigger a sweep event, see Moving money between Plaid Ledger and your bank account.

Sweeps can be observed via the /transfer/sweep/list and /transfer/sweep/get endpoints. /transfer/event/sync will also return all events types, including sweep events.

When you sign up with Plaid Transfer, you will be assigned transfer limits, which are placed on your authorization usage. These limits are initially assigned based on the volume expectations you provide in your transfer application. When you successfully create an authorization using /transfer/authorization/create, the amount authorized will be counted against your limits. Authorized amounts that aren’t used will stop counting towards your limits if the authorization expires or is canceled (via /transfer/authorization/cancel).

Any authorization you attempt to create over your limits will be automatically declined.

Daily limits refresh every day and monthly limits refresh on the first day of the month at 12:00 AM EST.

You can view your current limits on the “Account Details” page in the Transfer Dashboard. You can monitor your usage against your daily and monthly limits via the Account Information widget on the Overview page. You can also monitor your authorization limits and usage through the Transfer APIs.

The /transfer/configuration/get endpoint returns your configurations for each of the transfer limits. The /transfer/metrics/get endpoint contains information about your daily and monthly authorization usage for credit and debit transfers.

Plaid will also send you automatic email notifications when your utilization is approaching your limits. If your daily utilization exceeds 85% of your daily limits or your monthly utilization exceeds 80% of your monthly limits, you will receive automated email alerts. These alerts will be sent to your ACH, Technical, and Billing contacts. You can configure those contacts via the Company Profile page on the Plaid dashboard.

Any call to /transfer/authorization/create that will cause you to exceed your limits will return the decision "declined" with the decision rationale code set to TRANSFER_LIMIT_REACHED. The rationale description identifies which specific limit has been reached.

If you need to change your limits for any reason, you can request changes via the Account Details page in the Plaid Dashboard.

Plaid Transfer does not support peer to peer transfers or transfers between two accounts held by the same person. For these use cases, see Auth.