Skip to main content

March 14 2025

Treez Support avatar
Written by Treez Support
Updated this week

ACH Optimizations

This release introduces key ACH optimizations designed to improve reliability and handling of edge cases originating from external API integrations.

External API: Backward Compatibility with Legacy Token to Update ACH tickets

Prior to this release, the TreezPay service expected requests to update an ACH ticket to be authenticated with the latest version of authentication. While the TreezPay service is typically responsible for capturing an ACH payment and updating the ticket to complete, in certain cases, an external partner will do this. With this release we ensure that external partners can update an ACH ticket without error using either legacy or latest authentication..

Allow an ACH Payment Captured Outside of Treez to be Updated Complete in Treez

TreezPay ACH auth/capture flow is designed to allow ultimate flexibility, mitigate fraud, and streamline operations. To perform optimally, it is recommended to allow TreezPay to capture an ACH order based on pre-set fulfillment c. That said, with this release if a user captures an ACH order directly within their ACH portal, TreezPay will now treat an "already captured" provider response as "success" and allow it to be completed.

**IMPORTANT** If a user captures an order directly through the ACH provider && that order is adjusted in POS, the ACH payment will not reflect the new ticket total. It is highly advised to always allow TreezPay to perform capture in SellTreez to ensure charges reconcile with sales.

Handle Error Scenario Resulting from Missing ChargeId

In order for TreezPay to capture an ACH payment, the Treez ticket must have an ACH chargeID associated with it. Associating an ACH chargeID with a Treez ticket is the responsibility of the ACH originator. In most cases, the ACH originator is an eCommerce channel. Prior to this release, if an external partner failed to make proper charge association, capture would fail in Treez with a generic "null data" error. While a ticket without a chargeID association cannot ever be captured, an update was released to improve the error messaging allowing quicker issue identification and resolution.

Did this answer your question?