Added ACH Events to Auth Rules API

Overview

Customers using Lithic ACH can now use Auth Rules endpoints to set custom logic for approving and returning ACH payments. ACH Auth Rules work with ACH credit receipts and ACH debit receipts, and unlock the ability for customers to create ACH stop payments.

Details

Customers now have the ability to set approve/decline logic based on:

• Name of the company that originated the payment
• Company ID of the originator
• Amount of the ACH payment
• SEC code of the ACH payment
• Memo passed through on the ACH payment

Multiple of the above attributes can be defined combined in a single rule. Rules can be set to apply to the customer's entire program, or select accounts within a program.

Examples

Example 1. Stop Payments

Let's say a customer has revoked authorization for a biller whose service they are no longer using. We'll want to create a rule that returns ACH debit receipts that come from a specific originator ID, to a specific account token. In this case, the account token is 29c98870-1e7e-489c-b4c8-40d1cab0b6c3and the originator ID is 5330903621

First we'll create the rule by calling Create Auth Rule with the following parameters:

{
  "account_tokens": [
    "29c98870-1e7e-489c-b4c8-40d1cab0b6c3"
  ],
  "type": "CONDITIONAL_ACTION",
  "parameters": {
    "action": {
      "type": "RETURN",
      "code": "R07"
    },
    "conditions": [
      {
        "attribute": "COMPANY_ID",
        "operation": "IS_ONE_OF",
        "value": [
          "5330903621"
        ]
      }
    ]
  },
  "name": "b6c3_revoke_auth",
  "event_stream": "ACH_DEBIT_RECEIPT"
}

We'll get the following response:

{
  "token": "d6c78b3b-c738-49dd-9718-a2de34567bbc",
  "state": "INACTIVE",
  "program_level": false,
  "card_tokens": [],
  "excluded_card_tokens": [],
  "account_tokens": [
    "29c98870-1e7e-489c-b4c8-40d1cab0b6c3"
  ],
  "business_account_tokens": [],
  "type": "CONDITIONAL_ACTION",
  "current_version": null,
  "draft_version": {
    "version": 1,
    "parameters": {
      "action": {
        "code": "R07",
        "type": "RETURN"
      },
      "conditions": [
        {
          "attribute": "COMPANY_ID",
          "operation": "IS_ONE_OF",
          "value": [
            "5330903621"
          ]
        }
      ]
    }
  },
  "name": "b6c3_revoke_auth",
  "event_stream": "ACH_DEBIT_RECEIPT",
  "lithic_managed": false
}

Note that the rule is created in a state of inactive. To activate it, we'll call the promote endpoint using the rule's token d6c78b3b-c738-49dd-9718-a2de34567bbc

After calling the endpoint, we now see the rule has been made active, and payments will start returning if they come through from this COMPANY_ID

{
  "token": "d6c78b3b-c738-49dd-9718-a2de34567bbc",
  "state": "ACTIVE",
  "program_level": false,
  "card_tokens": [],
  "excluded_card_tokens": [],
  "account_tokens": [
    "29c98870-1e7e-489c-b4c8-40d1cab0b6c3"
  ],
  "business_account_tokens": [],
  "type": "CONDITIONAL_ACTION",
  "current_version": {
    "version": 1,
    "parameters": {
      "action": {
        "code": "R07",
        "type": "RETURN"
      },
      "conditions": [
        {
          "attribute": "COMPANY_ID",
          "operation": "IS_ONE_OF",
          "value": [
            "5330903621"
          ]
        }
      ]
    }
  },
  "draft_version": null,
  "name": "b6c3_revoke_auth",
  "event_stream": "ACH_DEBIT_RECEIPT",
  "lithic_managed": false
}

ACH Auth Rules can be updated, deactivated, and managed just like Auth Rules for card events. See Auth Rules to learn more

Release Timeline

Available now: November 21, 2025

User Impact

No impact, this change is additive only. Click here to learn more about ACH at Lithic

If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.

The Lithic changelog has an RSS feed! To monitor for new update announcements, subscribe with your preferred RSS reader.