Card, ACH, or RTP: The Reference Field That Picked the Rail
Archi4 min read
Contents
The Offer That Failed to Show Up#
A software firm that sells maintenance contracts to mid-sized manufacturers spent four months testing three ways to collect renewal payments: card networks, ACH debit, and real-time payments. The CFO expected the decision to follow fees. ACH costs a few cents per transaction. Cards average roughly 2.9 percent plus a fixed fee. Real-time payments, sent over the Federal Reserve's network, cost fractions of a cent at several banks. Fees did not decide the matter.
The firm's invoices carried long purchase order numbers. Buyers sent 34-character references that identified their own cost centers, projects, and amendment numbers. A renewal invoice might include "PO-2026-004731-NORTHEAST-FACILITY-EXPANSION" as the only link between the buyer's accounting system and the seller's billing database. That link mattered more than any interchange rate.
The Card Descriptor Ceiling#
Card networks cannot carry that text. The acquiring bank's gateway accepts a business name and an optional merchant descriptor. Most processors trim that descriptor to around 22 characters. The invoice reference above becomes "PO-2026-004731-NORTHEA". The buyer's accounts payable team sees a different number on the statement and flags it as an unknown charge. The seller's support queue filled with "What is this charge?" messages. One buyer disputed a $14,500 renewal because the statement text did not match its purchase order.
The ACH Addenda Gap#
ACH handles text differently. A standard ACH debit can carry an addenda record with up to 80 characters of payment information. But the receiving bank controls what appears on the customer's statement. Many banks display only the company entry description, a 10-character field. The full remittance detail sits in the addenda, which often reaches the customer only when a treasurer exports the batch file. In tests, 6 of 12 banks delivered the addenda to the client's portal. The other 6 buried it in a downloadable file that no one opened. The 10-character label "ACME MAINT" generated the same confusion as the truncated card descriptor.
The 140-Character Remittance Field#
Real-time payments use the ISO 20022 message framework. The pain.001 message includes an unstructured remittance information field that holds 140 characters. The full purchase order number fits without editing. The buyer's system receives it intact. Reconciliation becomes a direct database match. That was the smallest detail that mattered. A single text field, roughly four times longer than the card option and 75 percent longer than the ACH addenda, settled the rail selection.
The Adoption Constraint#
The company wanted to move every invoice onto the real-time network. The corporate bank account manager said only 38 percent of the firm's customer base could receive real-time payments. Many small manufacturers were still on ACH-only accounts. A separate fallback was required.
The final design used all three rails. The billing engine checks the invoice reference length before selecting a route. If the purchase order number is 25 characters or less, the firm sends it over a card network because the descriptor can hold it. If the reference is longer, the engine routes to real-time payment, provided the buyer can receive ISO 20022 messages. If the buyer cannot, the engine downgrades to ACH and accepts that the reference will arrive in the addenda, invisible to most AP staff.
The firm built a lookup table. It maps each customer's payment capability to one of three routes. The table is updated monthly through a questionnaire, not through live connectivity checks. There were surprises. Several large buyers had real-time payment addresses, but their enterprise resource planning systems truncated incoming remittance data at 30 characters. Those buyers stayed on ACH even though they appeared capable of faster settlement.
Refund Policy Reversal#
The team also changed its refund workflow. Card refunds can take five business days to appear. ACH returns take up to 60 days. Real-time payments do not support pullbacks. If the seller overcharges a customer, the money is gone until the customer sends it back. That shifted the firm's policy on credit notes. For transactions above $10,000, the billing system now requires an upfront payment confirmation before issuing a refund, reducing the need for reversals.
What a Routing Table Reveals#
The takeaway is not that real-time payments are always superior. The firm processes about 3,400 invoices per quarter. Of those, 1,100 have short references, 1,800 have long references, and 500 belong to buyers without modern payment capability. The routing rule solves a problem that standard analytics would have missed.
A payments professional can compare fees, settlement speed, return rates, and fraud liability. Those are all big numbers presented in slide decks. The reference field is a small paragraph in a technical standard. In this case, it changed the order of rails in a production system. The next time a payment migration stalls, look at the free-text fields first.
More articles