The Wrong Processing Setup Can Become Expensive Later

Start with the cash you can actually use

A processing proposal can look inexpensive until the business begins paying suppliers, returning customer money and financing its settlement delay. The headline merchant discount rate measures only one part of that experience. A useful assessment asks what reaches the operating account, when it arrives, which liabilities remain open and what happens if the transaction profile changes. This fifth instalment examines those questions through an illustrative merchant decision, rather than recommending a universal price or contract structure.

Stripe's reserve documentation describes reserves as funds retained against potential losses, including refunds and disputes. Visa's merchant dispute guidance emphasises timely, relevant evidence when responding through an acquirer. These references explain why liquidity and operational preparation matter; they do not establish the terms of a FixPays offer. The comparisons and worked example below are independent merchant analysis. Obtain the actual agreement and schedules for every proposed arrangement before assigning costs.

Compare two offers on the same transaction population

Imagine two hypothetical offers for a business processing USD 100,000 monthly. Offer A charges 3.5 percent and Offer B charges 4 percent. On those assumptions alone, A appears USD 500 cheaper each month. Now suppose A withholds a 10 percent rolling reserve and B withholds 5 percent. Before releases or other deductions, A retains an additional USD 5,000 from that month's volume. The retained funds are not automatically a permanent expense, but the merchant must finance the difference.

That example deliberately excludes fixed transaction charges, currency conversion, refunds, disputes, thresholds and release conditions. Add those using each provider's written proposal. Keep reserve principal separate from financing cost: counting the entire reserve as a fee overstates expense, while ignoring the cash restriction understates funding needs. A spreadsheet should show gross sales, permanent charges, restricted cash, expected releases and net bank receipts as different lines. Use identical assumptions for both offers, including customer geography and ticket size.

Turn settlement language into a dated cash forecast

A settlement schedule is useful only when its starting point and calendar are understood. Ask whether a delay begins at authorization, capture, batch closure or another event. Record cutoffs, business-day treatment, bank holidays, minimum settlement thresholds and payout frequency. A balance that becomes eligible on Friday may still reach the bank later. Model the actual sequence with dated example transactions rather than describing every arrangement as a simple number of days.

Test a normal week, a sales surge and a refund-heavy week. Include payroll and supplier deadlines alongside projected receipts. Then ask which events permit a reserve adjustment or settlement review, who communicates the decision and what evidence supports reassessment. Do not build a cash forecast on an informal promise of faster settlement after a clean period. A review opportunity and an agreed change are different things; the forecast should reflect the current binding terms.

Price the work behind disputes and refunds

A dispute can consume more than its transaction amount. Depending on the agreement, there may be handling charges, evidence-preparation time and a period before the outcome is known. Assign responsibility for retrieving order records, customer communications, delivery or access evidence and any refund reference. Measure actual staff effort instead of assuming that a dashboard eliminates the work. A lower processing rate can lose its apparent advantage when poorly organised evidence creates repeated manual investigations.

Keep refunds connected to disputes so two teams do not independently return the same payment. Document how partial refunds, unsuccessful refunds and disputed transactions appear in statements. Ask for sample reports showing the original payment, each deduction and the final adjustment. The purpose is traceability: finance should be able to explain a settlement difference without reconstructing the transaction from emails. This operating design is especially important when recurring billing or delayed fulfilment leaves customer obligations open after the original sale.

Check caps, approved scope and continuity

Capacity restrictions can be expensive when they conflict with the growth plan. Compare monthly volume caps, ticket limits, approved markets, currencies and business models against the transactions the merchant actually expects to send. A cheap arrangement that cannot accept the planned customer population is not a like-for-like alternative. Neither a technical integration nor another merchant's successful processing proves that your legal entity and traffic have been accepted.

Create a written change process for new domains, products, acquisition channels and material volume increases. A second processor can provide operational resilience where separately approved, but it does not authorise moving undisclosed activity between accounts. Preserve each provider's approved scope and reconciliation records. Also examine the exit process: unresolved refunds, reserves, recurring credentials, reporting access and customer support may continue after new processing stops. Budget for those responsibilities before announcing a migration date.

Make the decision reviewable

Give the decision owner a compact comparison with three scenarios: expected trading, slower settlement and elevated refunds. Show total permanent charges, peak restricted cash, minimum operating liquidity and manual workload. Mark every unconfirmed item clearly, identify its owner and attach the relevant contract wording or provider response. If a difference depends on future approval, leave it conditional. This approach allows commercial negotiation to focus on a specific constraint without pretending that protective controls can simply disappear.