POST /signal/schedule

Use /signal/schedule to schedule a planned ACH transaction.

Servers

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
default_payment_method String No

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, Signal defaults to STANDARD_ACH.

SAME_DAY_ACH: Same Day ACH (as defined by Nacha). The Signal 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 (UTC): 2:30 PM, 6:45 PM, and 8:45 PM.

STANDARD_ACH: Standard ACH (as defined by Nacha), typically settled one to three business days after submission.

REAL_TIME_PAYMENTS: Real-time payments via Request for Payment through networks such as RTP (The Clearing House) and FedNow, where the consumer can authorize the payment in response to a RFP, and the transaction is processed and settled immediately.

DEBIT_CARD: Payments processed over debit card networks, leveraging the card-based infrastructure for real-time or near-real-time settlement.

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.

Possible values:

  • "SAME_DAY_ACH"
  • "REAL_TIME_PAYMENTS"
  • "DEBIT_CARD"
  • "STANDARD_ACH"
  • "MULTIPLE_PAYMENT_METHODS"
client_id String No

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.

amount Number Yes

The transaction amount, in USD (e.g. 102.05)

client_transaction_id String Yes

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.

account_id String Yes

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.

access_token String Yes

The access token associated with the Item data is being requested for.

secret String No

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.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.