<user_uuid>, which refers to the unique identifier of the registered business
or individual that was obtained from the registration API.
Account/Routing Validation
Our ACH API supports account and routing number validation to prevent failed transactions and fund reversals. This validation is performed by setting thevalidate_account_routing flag to true when adding a bank account to an
existing user.
Validation Results:
- valid: The account and routing number are valid, and the account is added successfully.
- invalid: The account or routing number is invalid, and the account is not added to the application. This returns an HTTP response code - 406
- not_validated: Validation could not be completed, but the account is still added to the application.
Billing
Our ACH API supports associating specific billable events with a particular merchant, enabling precise attribution for billing purposes. This feature allows you to link the UUID of a user tied to a merchant (a business that has undergone KYB verification) to the billing event recorded for the API call. To attribute the billing event to a merchant, include the following parameter in your request payload:- billing_merchant_user_uuid: The unique identifier (UUID) of the user associated with the merchant to whom this billable event should be attributed.
