Card Rails, Bank Debit, or Open Banking: One Renewal Decision

Archi4 min read

paymentsfintechbillingoperations

Contents
  1. A Failed Renewal, Three Payment Paths
  2. Card rails: the default with a bill
  3. Bank debit: cheap, but the mandate is the product
  4. Open banking: fast, and less predictable
  5. The Decision Inside the Spreadsheet

A Failed Renewal, Three Payment Paths#

At 7:40 on a Monday, the finance lead at a 40-person software company watches 312 renewal charges fail in the dashboard. Most are expired cards. A few are bank declines. The company sells annual project templates to small firms in the United States and the European Union. Its card-only checkout is simple, but the failures expose a cost problem: card fees on a 240 euro annual plan can eat 6 to 8 euros, and a failed renewal can cost a support ticket, a dunning email, and a lost month.

The company had to pick a default for European renewals. It narrowed the choice to three: keep cards on file, move to bank debit mandates, or use open banking pay-by-bank at checkout. Each option changes who owns the failure.

Card rails: the default with a bill#

Cards are the easiest to explain. A customer types 16 digits, the issuer authorizes in seconds, and the payment processor handles settlement. Recurring billing works through stored credentials and network tokens. Disputes go through a formal chargeback process. For a small team, that is a lot of operational weight lifted.

The cost is visible. Online card acceptance commonly runs in the low single digits as a percentage of the sale, and premium or cross-border cards can push it higher. In the company's model, a 2.4 percent effective rate on 1 million euros of annual renewals is 24,000 euros. A failed card also creates a specific kind of work: the customer did not choose to leave, but the payment lapsed.

Card rules change by region. Strong Customer Authentication in Europe adds a bank check for many online payments. The company's checkout had to handle a redirect, a timeout, and a customer who closes the tab. Cards still won on familiarity. They lost on cost and on the slow decay of stored credentials.

Bank debit: cheap, but the mandate is the product#

Bank debit, such as SEPA Direct Debit in Europe or ACH debit in the United States, moves money from the customer's account under a signed mandate. The per-transaction cost is usually lower than cards, and the payment method suits annual invoices and business customers who already pay by transfer.

The hard part is not the transfer. It is the mandate. The customer has to authorize the company to pull funds, and the company has to store proof, notify before debits where required, and handle returns. A return can arrive days after the charge. For a 240 euro renewal, a returned debit plus a bank fee can wipe out the savings on several good payments.

Bank debit also changes the sales conversation. Business buyers accept it. Consumers often prefer the familiar card flow. Settlement is not instant, so the company cannot treat the payment as final when the invoice closes. Refunds take longer. Reconciliation needs a clean reference on every line.

The company's first trial put bank debit behind a manual invoice, not at self-serve checkout. That kept support load low. Customers who wanted it could choose it, but the default stayed on card.

Open banking: fast, and less predictable#

Open banking pay-by-bank lets a customer approve a transfer inside their banking app. The money can arrive quickly, and the fee can be lower than card processing. There is no card number to expire. For one-time payments, the flow is attractive: invoice, redirect, approval, confirmation.

For recurring revenue, the picture is messier. Recurring open banking needs a mandate or a payment initiation setup that varies by provider and bank. Coverage differs. Some banks drop out during maintenance. A customer who changes banks has to reauthorize. The company also has to reconcile incoming transfers that may arrive with sparse reference data.

The company tested open banking on a checkout link for one-time top-ups. It worked, but the support team saw a new pattern: customers approved the payment, then closed the browser before the redirect returned. The payment existed. The order did not. The fix was a webhook and a search by payment reference, not a better button.

The Decision Inside the Spreadsheet#

The finance lead built a simple model with four columns: fee per payment, failed payment rate, support minutes, and days to cash. The company did not need a single winner for every customer. It needed a default that reduced involuntary churn without creating a reconciliation backlog.

Cards won on conversion for monthly self-serve plans. The failures were annoying, but the fix was operational: card updater services, retries timed to payday, and a clear email before the charge.

Bank debit won on annual European invoices above 200 euros. The savings were real, and business customers already understood direct debit. The company made it the default for those renewals, with card as a fallback. It kept the mandate flow in the invoice, not the product checkout.

Open banking stayed as an option for one-time payments and for customers who asked for it. It was not the default for recurring revenue because the mandate and reconciliation work did not fit a 40-person team.

The company now watches two numbers every week: the return rate on bank debits and the share of open banking payments that need manual matching. Those numbers decide whether the mix changes. The card fee is no longer the only cost on the page.

More articles