The Locationinfos Endpoint is a great resource for retreiving information about Locations that already includes associated imforation that would otherwise require multiple API requests to obtain. Additionally, this endpoint can be used to determine any specific requirements for your terminals when using an ACH processor.
View Record List
Note: Empty Request Body.
Terminals supporting ACH can often have different requirements as well as different capabilities for processing transactions. These requirements and capabilities can easily be identified for your terminal so you know exactly what data you need to provide in order for the transaction to be accepted as well as what types of actions you can perform on a specific terminal.
If you are using a Terminal supporting ACH that has specific requirements, you will see this information under the associated Product Transaction. The code example below is similar to the one above although some areas have been omitted to give greater visibility to the Terminal specific data.
In the example above, you can see that within a Product Transaction there is a "processor_data" field containing an array of Terminals. For each terminal there will be an array of "actions" that the terminal can perform. Additionally, there will be a "required" array that will list all of the requirements that must be met in order for the Terminal to accept the transaction.
In general, the values within the "required" array are the exact names of the fields that must be provided in order to satisfy the requirement. However there are some values within the "required" array that correspond to a set of conditionally required fields.
|driver_license||dl_number AND dl_state|
|identity_verification||ssn4 OR dob_year.