GoCardless vs Stripe ACH: choose the collection process behind bank debit

GoCardless and Stripe can both enter a shortlist for collecting recurring payments from US bank accounts. The useful comparison is the collection process your business will operate: obtaining permission, scheduling the right amount, recognizing a failed payment, and keeping the customer balance accurate. It is not enough to compare a general bank-payment headline with a card-processing rate.

This guide concerns GoCardless ACH collections and Stripe ACH Direct Debit. Stripe separately offers Instant Bank Payments with different characteristics, so do not mix the two products in a quote. Stripe describes ACH Direct Debit as a delayed-notification method with payment-failure and dispute risk. That distinction matters when deciding when to provide a service or release an order.

A subscription platform might calculate the bill while a bank-payment service collects it. An invoicing application might own both the due date and the customer reminder. Decide where the authoritative amount comes from before choosing another collection schedule. Two systems that each initiate a monthly debit can create a serious duplication problem.

For an illustrative $800 monthly contract with a separately approved $125 extra service, determine whether those amounts become one collection or two. Keep the invoice references and customer agreement visible either way. Ask each provider to demonstrate the proposed connection to the system that actually calculates the obligation.

GoCardless documentation distinguishes one-off, recurring, and standing consent types, with specific restrictions on the payment resources associated with each. Stripe requires customer authorization and bank-account verification for ACH Direct Debit. Having bank details on file should not be treated as an unrestricted right to debit them.

Review the proposed customer journey with the person responsible for payment operations. Include a fixed subscription, variable usage, a one-time invoice, and a canceled agreement if these are relevant. Ask how acceptance is retained, how customers receive the necessary information, and what stops future collections after authorization is revoked. Confirm the applicable scheme requirements with the provider for your actual arrangement.

Write down the collection request date, the date funds become available in the provider balance, and the expected bank payout date. They answer different questions. Stripe explicitly distinguishes ACH settlement into its balance from the payout schedule that follows. Obtain the corresponding dates and conditions for the GoCardless proposal.

A forecast that places every submitted debit into today's available bank cash can overstate what the business can spend. Keep pending collections separate until the agreed status supports the forecast treatment. For a large upcoming payroll, use the provider's actual account-specific schedule and an alternative funding plan rather than relying on an advertised fastest case.

Make the demonstration include an initially submitted payment that later fails. The customer obligation, collection attempt, and any fee should remain distinct. Ask who receives the notice and how the customer is contacted. A retry should follow the relevant return reason, authorization, and provider rules; it should not be a universal response to every failure.

Stripe warns that an ACH refund and a separate bank dispute can produce two credits for the same payment. Customer support therefore needs visibility into the collection investigation before issuing money back. The same operational question belongs in the GoCardless evaluation: who can refund, who sees disputes, and how those actions are coordinated?

Ask for a case where a customer reports a problem after the original invoice appears paid. The accountant should be able to follow the original debit, any reversal or refund, and the resulting customer balance. Avoid erasing the original payment merely to make the invoice status look tidy.

Request pricing for your transaction sizes, volumes, failures, refunds, currency needs, and connected applications. Include setup and the internal work of handling exceptions. If a proposal includes a protection or faster-payment product, state its eligibility and contractual scope separately. Do not assume that every bank debit receives the same protection.

Choose the arrangement that lets the billing owner, collections team, and accountant explain one payment from authorization through payout or return. Existing Stripe use may make one integration convenient; a bank-debit-focused workflow may make GoCardless worth adopting. The deciding evidence is the complete collection process your team can maintain.