Skip to main content

Low Value and ACH Direct Debits

Use this API to initiate low value and ACH direct debit payments globally.

Overview

The Low Value and ACH Direct Debits API allows for the initiation of low value and ACH payments in a lightweight yet robust way. A POST request communicates the payment details, and the synchronous ACK/NACK responds with real-time information to communicate initial processing status.

Low value and ACH payments can be issued via API to the following regions:

  • United States and Canada (NA)
  • Europe, Middle East, and Africa (EMEA)
  • Asia Pacific (APAC)

Supported transactions

This API only supports U.S. ACH reversals.

Tip

View the API specification to learn more about request endpoints and parameter details.

To reverse a U.S. ACH debit, you must initiate a U.S. ACH credit with the following requirements:

  • Add value REVERSAL within paymentTypeInformation.categoryPurpose.proprietary with the same endToEndId of the payment you want to reverse. 
  • An original transaction was already submitted via API with the same endToEndId of the reversal being requested.
  • Original transaction is not in a status of PENDING, REJECTED, or RETURNED.
  • Reversal must be the opposite transaction type of the original transaction.
  • A reversal request was not previously submitted.
  • The requestedExecutionDate of the reversal must be within five banking days of the original payment.
  • All information besides requestedExecutionDate in the reversal payment instruction must be the same as the original payment (opposite transaction type).

Callbacks

  • In a callback message, updates for multiple payments can be included, with a maximum of 50 payments in one callback message. However, a single callback message will only contain updates for credits or debits, not both. Additionally, it is possible for a callback message to include ACH transactions from different regions.
  • When J.P. Morgan sends a callback message, they will wait for up to three seconds to receive a "200 OK" response. If no response is received, the callback mechanism will retry with an exponential gap of 10*3^x seconds, i.e., 10 seconds, 30 seconds, 90 seconds, 270 seconds, 810 seconds, etc. 

Third-party payment processing (TP3) SEPA flows

In addition to standard SEPA flows, we now support third-party payment processing (TP3) SEPA flows. TP3 payments are transactions where you are providing payment services to your underlying customers or merchants. For more information, please reach out to your service representative.

Holidays and weekends

ACH transaction processing on holidays and weekends is dependent on the account's configuration, or how it is set up.

  • If the account is configured for revaluation, the value date is automatically updated.
  • If the account is not configured for revaluation, the system rejects the transaction if it falls on a weekend or holiday.

Next steps

Complete the onboarding process to ensure you have everything you need.

Learn how J.P. Morgan protects your transactions.