Reporting returns and decisions

It's critical that you report ACH activity (both decisions and returns) back to Plaid - reporting enables Plaid to help you tune your rule logic to optimize your integration.

For both decisions and returns, you can use API endpoints (recommended) or upload the transactions manually via the Signal Dashboard.

Reporting a decision allows Plaid to know that the transaction was processed. Once it knows the transaction was processed, if Signal doesn't hear about a corresponding return, it assumes the transaction was successful.

Plaid will automatically infer decisions for customers using Signal Rules with only ACCEPT or REROUTE results. There is no need to report decisions back to Plaid for these transactions unless the decision has changed (for example, your processor refused to process an ACCEPTed transaction).

If your rules integration uses REVIEW results, then you'll need to call /signal/decision/report once you've made the final determination for the transaction and it is convenient to do so.

If your integration is directly reading scores and attributes instead of using Signal Rules, then you'll need to call /signal/decision/report for all transactions.

To report an ACH return to Plaid, call /signal/return/report as soon as you're aware of the ACH return and it's convenient to do so.

If you would prefer to not report decisions and returns via API, you can upload them via the data import page in the Dashboard. It is recommended you upload reports on a weekly basis.

The CSV files for uploading decisions and returns must follow the schemas defined below. Ensure your data is properly formatted to avoid processing errors.