Schedule a planned ACH transaction
Use /signal/schedule to schedule a planned ACH transaction.
Request body
Your Plaid API client_id. The client_id is required and may be provided either in the PLAID-CLIENT-ID header or as part of a request body.
Your Plaid API secret. The secret is required and may be provided either in the PLAID-SECRET header or as part of a request body.
The access token associated with the Item for which data is being requested.
The Plaid account_id of the account that is the funding source for the proposed transaction. The account_id is returned in the /accounts/get endpoint as well as the onSuccess callback metadata.
This will return an INVALID_ACCOUNT_ID error if the account has been removed at the bank or if the account_id is no longer valid.
The unique ID that you would like to use to refer to this transaction. For your convenience mapping your internal data, you could use your internal ID/identifier for this transaction. The max length for this field is 36 characters.
The transaction amount, in USD (e.g. 102.05)
The payment method specified in the default_payment_method field directly impacts the timing recommendations provided by the API for submitting the debit entry to your processor or ODFI. If unspecified, defaults to STANDARD_ACH.
SAME_DAY_ACH: Same Day ACH (as defined by Nacha). The API assumes the settlement will occur on the same business day if the /signal/schedule request is submitted by 6:00 PM UTC. Note: The actual cutoff time can vary depending on your payment processor or ODFI. Nacha has established three processing windows for Same Day ACH (Eastern Time): 10:30 AM, 2:45 PM, and 4:45 PM.
STANDARD_ACH: Standard ACH (as defined by Nacha), typically settled one to three business days after submission.
MULTIPLE_PAYMENT_METHODS: Indicates that there is no default debit rail or multiple payment methods are available, and the transaction could use any of them based on customer policy or availability.
Response
OK
The recommended optimal date to submit the debit entry, formatted in ISO 8601 "YYYY-MM-DD" (e.g., "2024-03-30"). The optimal_date is derived from the date with rank = 1 in the following recommendations array.
NOTE: The default_payment_method field specified in the request will affect the recommendation, since we're accounting for debit settlement time.
The debit scheduling evaluation starts from the day the /signal/schedule request is submitted (Day 0) or the next banking day if the submission day is not a banking day, and extends through the following five banking days (Day 1 to Day 5). If no date within this period is considered likely to result in a successful debit attempt, null will be returned for the optimal_date.
A unique identifier for the request, which can be used for troubleshooting. This identifier, like all Plaid identifiers, is case sensitive.