ACH Tracing and Troubleshooting
This section describes identifiers used to trace outgoing and incoming ACH. It also describes statuses that indicate a failed outgoing ACH request.
Using identifiers to trace ACH transactions
You can use a combination of identifiers to trace ACH transactions within your system. Tracing methods depend on whether the transaction is outgoing or incoming ACH.
Note
See also Mapping Transactions Within Your System for a general guide on using identifiers to trace transactions.
Tracing outgoing ACH
When you call the Create ACH Transaction endpoint, you pass a unique identifier through the transactionId parameter. Galileo uses the value in transactionId to associate the endpoint call with Events API webhooks as well as RDF records.
- Events API webhooks — When Galileo sends a transaction event such as
BPMT: pmtorBADJ: adjas a result of an outgoing ACH transaction, the event’sext_trans_idfield matches thetransactionIdvalue from your call to the Create ACH Transaction endpoint. - RDF record — In the RDF record for an outgoing ACH transaction, the record’s
EXTERNAL TRANSACTION IDfield matches thetransactionIdvalue from your call to the Create ACH Transaction endpoint.
In the response data for a call to the Create ACH Transaction endpoint, Galileo returns the ach_transaction_id, which is unique to every outbound ACH transaction. The ach_transaction_id is not used for tracing Events API webhooks or RDF records, but is used to track any associated calls to the Cancel ACH Transaction and Get ACH Transaction History endpoints.
This table summarizes identifiers for outgoing ACH transactions.
Note
The labels for these identifiers in the Events API messages may differ according to the arrangements you make with Galileo. For example, each of these identifiers could be labeled
tran_idinstead of the identifier listed below.
| Identifier | Where this identifier is used | Description |
|---|---|---|
transactionId | Create ACH Transaction endpoint | Unique transaction identifier that you pass through the Create ACH Transaction endpoint. |
ach_transaction_id | Create ACH Transaction endpoint | Unique identifier that Galileo returns in the response data when you call the Create ACH Transaction endpoint. This value is used in associated calls to the Cancel ACH Transaction and Get ACH Transaction History endpoints |
ext_trans_id | Some transaction events (see the Transaction Events Index) | Matches the transactionId passed in the original call to the Create ACH Transaction endpoint. |
EXTERNAL TRANSACTION ID | RDF | Matches the transactionId passed in the original call to the Create ACH Transaction endpoint. |
AUTHORIZATION CODE | RDF | Matches the unique identifier that Galileo generates for a payment or adjustment. In the Posted Transactions RDF, the TRANSACTION CODE/TYPE for a payment starts with the letters PM and for an adjustment it starts with AD. |
pmt_source_id | Some transaction events (see the Transaction Events Index) | Identifier for the record that initiated the payment. This is not guaranteed to be unique. Galileo does not recommend using this identifier to trace transactions. |
ach_trans_id | Some transaction events (see the Transaction Events Index) | This value matches the pmt_source_id. Galileo does not recommend using this identifier to trace ACH transactions. |
Tracing incoming ACH
An incoming ACH transaction does not result in an external_trans_id in Events API webhooks or the RDF. This table summarizes identifiers for outgoing ACH transactions.
| Identifier | Where this identifier is used | Description |
|---|---|---|
AUTHORIZATION CODE | RDF | Matches the unique identifier that Galileo generates for a payment or adjustment. In the Posted Transactions RDF, the TRANSACTION CODE/TYPE for a payment starts with the letters PM and for an adjustment it starts with AD. |
pmt_source_id | Some transaction events (see the Transaction Events Index) | Identifier for the record that initiated the payment. This is not guaranteed to be unique. Galileo does not recommend using this identifier to trace ACH transactions. |
ach_trans_id | Some transaction events (see the Transaction Events Index) | This value matches the pmt_source_id. Galileo does not recommend using this identifier to trace ACH transactions. |
Troubleshooting outgoing ACH
This table lists ACH transaction statuses that prevent an outgoing transaction from reaching settlement and the next step to take.
| Status | Description | Next Step |
|---|---|---|
D | Deleted by account holder | Wait for the account holder to request a new transaction. |
E | Error | Return or cancel the transaction and notify the originator. |
L | Cancelled due to violation of debit limit | Notify the originator that the transaction was cancelled and that it is outside of the allowed range. |
R | Bad routing number | For outgoing ACH, obtain the correct routing number from the customer. |
X | On hold | Determine whether to post or return the transaction. |
l | Pending approval, limit exceeded | Notify the originator that the transaction is outside of the allowed range. |
Updated 7 days ago