Automated Clearing House (ACH) FAQs

Why am I getting a 400 - Invalid JSON Format error when creating an ACH token using Clover APIs?

The 400 - Invalid JSON Format error typically means the JSON payload in your API request is incorrectly formatted or contains invalid values. To resolve it:

• Check JSON syntax: Ensure all strings use double quotes, and the structure is properly nested.
• Validate required fields: Replace placeholder values like "string" with actual data. Fields such as bank_account_number, bank_routing_number, and customer_id must follow specific formats.
• Review field-specific requirements: Fields like check_type, customer_id_type, and customer_id_state may require predefined values. See the API documentation for accepted formats.
• Inspect the agreement object: Make sure all required fields within this object are present and correctly formatted.
• Use a JSON validator: Tools like JSONLint can help identify formatting issues before sending the request.
  If you're using dummy data in a sandbox environment, ensure it still adheres to the expected structure and types. For more information, see Create an ACH token.

Can I accept ACH payments using the Clover Hosted Checkout?

Yes, ACH payments are supported in Hosted Checkout through TeleCheck® ACH, but only for merchants who are enabled for ACH during onboarding. If your client was not set up for ACH initially, Hosted Checkout will not support ACH payments by default. In such cases, you would need to contact Clover Developer Relations at [email protected] to enable ACH functionality. For setup instructions, see Use TeleCheck ACH with Hosted Checkout.

Can I assign or save an ACH token to a Clover customer for future use using the Platform API or in the sandbox environment?

No, ACH tokens cannot be assigned or stored as a card-on-file for future use by default in the Clover Platform API or sandbox environment. Attempting this may result in errors such as pre-Authorization not supported or a 500 Internal Server Error. To enable ACH token testing and pre-authorization for your test merchant, email [email protected].