Skip to content
Search Articles/

less than a minute read • Updated an hour ago

ACH.com

Connect Foxy to ACH.com for secure payments.

Countries

United States

Features
  • Refunds

ACH.com is an ACH-only payment provider. It processes bank debits over the US Automated Clearing House network — it does not handle cards, so it is added alongside a card gateway rather than instead of one.

Supported country: United States. ACH is a US-only network, so this gateway processes USD from US bank accounts only.

Setting up ACH.com

You will need an ACH.com merchant account before you start. ACH origination is underwritten — signing up is not instant, and adding the payment method in Foxy does not enable ACH processing on its own.

From ACH.com, obtain:

  • your NACHA ID, the identifier for your ACH origination account

  • your Security Token, the credential Foxy authenticates with

ACH.com's support team can tell you where these are shown in their merchant portal. Then, in Foxy:

  1. 1

    Go to the Foxy admin and open Settings > Payments.

  2. 2

    Open or create a payment method set. If you only have one, it will be the Default Payment Method Set.

  3. 3

    Click Add payment method + and choose ACH.com.

  4. 4

    Under Live setup, enter your NACHA ID and Security Token. This setup only takes effect once Use live credentials is turned on for the payment method set.

  5. 5

    Click Create — or Save, if you are editing an existing entry.

The panel is split into a Live setup block and a Test setup block carrying the same two fields. (The Live heading reads "Live setup (inactive)" while the set has Use live credentials switched off — that is the current state of the set, not a different set of fields.)

What the customer fills in at checkout

For an ACH.com payment, Foxy collects:

  • Routing number — Notes: The nine-digit ABA routing number of the customer's bank.

  • Account number — Notes: The bank account number.

  • Name on account — Notes: The name on the bank account.

  • Account type — Notes: A dropdown offering Checking or Savings.

  • Account-ownership checkbox — Notes: See below.

ACH.com is the only ACH gateway on Foxy that asks the customer whether the account is checking or savings. If savings-account support matters to you, that is a reason to choose it over the alternatives.

The checkout also shows a checkbox the customer has to tick, reading "I represent that I am the owner and/or authorized signer on the checking account above". The checkout will not submit without it, and there is no setting to turn it off. ACH is a pull from someone's bank account, and NACHA — the body that governs the ACH network — expects the account holder to have authorised the debit. See ACH payments on Foxy for more.

Testing

Foxy does not supply shared test credentials for ACH.com. To run test transactions you will need test credentials from ACH.com — a test NACHA ID and Security Token — and enter them in the Test setup block.

As with every ACH gateway on Foxy, you can confirm that the checkout accepts bank details and that the gateway accepts the submission, but you cannot rehearse settlement or a return. Foxy is not told the outcome in production either, so plan your reconciliation process before your first live ACH order rather than after one bounces.

There are no test card numbers for this gateway — it does not touch cards at all.

Advanced features

  • No 3-D Secure, no client-side JavaScript. ACH has no equivalent of card authentication, and this gateway needs no SDK or JavaScript on your checkout. It is a plain server-side integration: nothing to load, nothing to style, nothing extra to configure in your checkout template.

  • No card verification, no AVS, no CSC. There is no card, so none of these apply.

  • No multi-currency and no authorization-only. ACH.com processes USD only, and does not support authorising a payment without capturing it.

Important notes and caveats

  • Transactions stay pending forever. Covered above and in ACH payments on Foxy. If you have a datafeed, the status node on an ACH transaction will read pending and no further datafeed will arrive to change it. Do not write fulfilment logic that waits for approved on an ACH order.

  • ACH is slow and reversible. Settlement takes several days, and a debit can be returned after the fact for insufficient funds, a closed account or a customer dispute. Decide deliberately whether you are willing to fulfil against an unsettled ACH payment.

  • Refunds and voids can be issued from Foxy. ACH.com is one of only two ACH gateways where Foxy can send a refund or void request to the gateway — most cannot. Foxy sending the request is not a guarantee ACH.com will accept it: that depends on ACH.com's own rules and on how long ago the debit was submitted. If it is declined, or if the debit has already settled, take it up with ACH.com directly.

Troubleshooting

Every ACH transaction is declined. Check with ACH.com that your account is approved and live for origination, and that the NACHA ID and Security Token in Foxy are the ones for the mode you are running in — Live setup if the payment method set has Use live credentials on, Test setup if it does not.

A transaction shows as pending days later. That is expected and permanent. See above.

Anything about a specific transaction's fate — settled, returned, held — has to come from ACH.com or your bank. Foxy does not have that information.

Need Help?

Did this article answer your questions? Need help with anything? Please click below to contact us.