What Platform CFOs Actually
Care About in Payment Infrastructure

The engineering team evaluates payment infrastructure on API documentation quality, sandbox reliability, and integration complexity. That's the right set of criteria for engineers evaluating a payment API. It's not what makes or breaks the CFO approval that comes later.

Platform CFOs — particularly at growth-stage companies handling meaningful transaction volume — have a distinct set of concerns that don't always surface in technical evaluations. Understanding them early saves a lot of late-stage friction in the vendor selection process.

Reserve requirements: the balance sheet question

When a platform becomes a payment facilitator or processes significant transaction volume, the acquiring bank typically requires a reserve — a portion of processing volume held in a reserve account to cover potential chargebacks and refunds. This reserve can range from 5% to 20% of monthly processing volume depending on the platform's risk profile, industry, and dispute history.

For a platform doing $10M monthly in payment volume at a 10% reserve requirement, that's $1M sitting in a reserve account that doesn't appear in the platform's operating cash. For a growth-stage company, this is a meaningful working capital impact that the CFO needs to model before signing a PayFac agreement.

The questions CFOs ask: What's the initial reserve requirement? Is it rolling (held as a percentage of each month's volume) or fixed (a one-time deposit)? What are the conditions under which the reserve increases? What's the process and timeline for releasing reserves at the end of the relationship?

Reserve terms vary significantly between payment infrastructure providers and acquiring bank relationships. A provider who can offer lower reserve requirements (often possible with strong dispute history data or personal guarantees) or structured reserve release schedules is materially more attractive to a CFO than one who requires a flat 10% rolling reserve indefinitely.

Revenue recognition: what the GL entry looks like

Payment transactions generate a debit to accounts receivable and a credit to revenue — straightforward. What's less straightforward is how transaction fees, refunds, chargebacks, and settlements flow through the accounting system.

The CFO's question is whether the payment infrastructure can provide data in the format and frequency that the accounting team needs to post accurate journal entries. Specifically: settlement reports that separate gross transaction amounts from processing fees, daily reconciliation files that match internal records against bank settlement amounts, and month-end reports that break out the components needed for revenue recognition under ASC 606 or IFRS 15.

Most payment processors provide transaction reports. Fewer provide reports structured for accounting consumption. The difference matters more at scale — manually transforming transaction reports into journal-entry-ready formats is fine when your accounting team processes a few hundred transactions monthly. At 50,000 transactions per month, you need a report format that flows directly into your GL system or requires minimal transformation.

A CFO will specifically ask: what's the format and frequency of settlement reports? Can we get an API endpoint for settlement data rather than downloading files? Does your reporting distinguish between authorization date, settlement date, and funding date (these are three different dates that can fall in different accounting periods)? The more friction in the data pipeline between payment events and GL entries, the more the CFO will push back on the vendor.

Float and timing: when does money actually move

Payment volume processed today doesn't arrive in your bank account today. The typical cycle: card authorization happens in real-time, settlement instruction goes to the acquiring bank end-of-day, funding lands in the platform's bank account T+1 to T+2 business days later. For ACH payments, funding can be T+3 to T+5.

For cash flow forecasting, the CFO needs to understand the exact timing of each leg of this cycle. A $1M day in payment volume hits cash 2 business days later — but if that day is a Thursday, Monday is a business day, and Tuesday is when the money actually arrives. Holiday weekends compress or shift this timing. End-of-month processing surges can create multi-day delays if banks are processing high volumes.

The practical question: does the payment infrastructure provide next-day funding or T+2? Is accelerated funding available, and what does it cost? For businesses with tight operating cash cycles — platforms that need to pay out to sellers or contractors before they receive settlement from card transactions — the funding timing is not an engineering detail. It's a cash flow constraint that the CFO manages.

Audit trails and financial controls

When a platform's financials are audited — whether by external auditors for a formal audit, by investors during due diligence, or by the board during performance review — payment records are a primary data source. The auditor needs to be able to trace from a number on a financial statement back to individual transactions with confidence that the records haven't been modified.

This requires: immutable transaction records with timestamps and event logs, clear change history for any transaction state changes (refunds, disputes, adjustments), segregation between transactional records and any derived or computed figures in reports, and documentation of the reconciliation process that confirms reported figures are complete and accurate.

Most payment processors maintain immutable transaction records — this is table stakes. What varies is how accessible those records are to auditors, whether the API supports the kinds of historical queries auditors run, and whether the data model is documented clearly enough that an external auditor can understand it without assistance from the platform's engineering team.

A CFO who has been through a financial audit at a previous company will ask about this explicitly. "Show me how we'd respond to an auditor asking to verify the revenue reported for Q3 2025" is a real question. The answer needs to be cleaner than "we'd pull a CSV from the dashboard and clean it up in Excel."

Contract terms: indemnification and liability

The business terms of a payment infrastructure agreement matter as much to a CFO as the technical capabilities. Specific clauses that get attention in the CFO review:

Indemnification: who's liable if a security breach results in cardholder data exposure? If the infrastructure provider is breached, does the platform bear liability to affected cardholders? Payment infrastructure contracts vary significantly in how liability is allocated, and a CFO who's aware of the GDPR and state-level data protection exposure will read the indemnification provisions carefully.

Termination clauses and settlement: what happens when the contract ends? How long does the provider hold reserves post-termination? What's the data export process, and in what format? A platform that processes $100M annually and then switches providers needs to know exactly what the transition looks like contractually, not just technically.

SLA financial penalties: if the uptime SLA is breached, are there financial remedies? "99.99% uptime with no financial consequences for breach" is different from "99.99% uptime with service credits." This is less important for most platforms than the other factors above, but CFOs notice when a provider won't put financial commitments behind their uptime promises.

The conversation to have before the RFP

Most CFOs would rather have a candid conversation about reserve requirements, reporting format, and contract terms early in the evaluation process than discover late in the procurement cycle that a provider's terms don't work for their financial model. Payment infrastructure vendors who can speak the CFO's language — who can discuss working capital impact of reserves, reporting format options, and audit support without routing every question back to the technical team — shorten their sales cycles and have fewer late-stage deals fall through.

If you're the person shepherding a payment infrastructure evaluation, involve your CFO in the initial vendor conversations. The questions they'll ask are ones the vendor should be able to answer quickly. If the vendor can't, that's worth knowing early.