Skip to main content

Market-neutral small-business guide

Compare Marketplace and Payment Fees

Translate your actual provider contracts and statements into percentage, fixed, recurring, refund and fulfilment components.

Build a dated source record

Contract and statement prerequisites

  • Record the contract or plan name, market, currency and date checked. (not complete)
  • Identify the transaction amount or fee base to which each percentage applies. (not complete)
  • Capture fixed, recurring, conditional, refund, dispute and currency-conversion components. (not complete)
  • Keep marketplace, payment, advertising, fulfilment and storage charges in separate rows. (not complete)
  • Record negotiated or account-specific terms instead of substituting a public headline rate. (not complete)
  • Reconcile at least one real settlement statement before using the stack in a decision. (not complete)

Normalise the fee stack without losing its source

  1. Copy each fee component from the current contract or statement into its own source row.
  2. Record the exact fee base for every percentage component.
  3. Keep fixed order charges separate from recurring period charges.
  4. Allocate a recurring charge per order only with a stated order-volume scenario.
  5. Add conditional, refund, dispute, conversion and fulfilment components only when they apply.
  6. Rebuild one settlement and explain every deduction or credit before comparing scenarios.
  7. Compare the complete effective cost and operating requirements, not one headline percentage.
Normalised fee cost per order

Fee cost per order = percentage fee base ร— percentage rate + fixed fee + allocated recurring fee + applicable conditional fees

percentage fee base
Contract-defined amount to which the percentage rate applies (currency units per order) โ€” current contract and order record
percentage rate
Current percentage component for the applicable scenario (percentage) โ€” current contract
fixed fee
Fixed transaction component that applies to the order (currency units per order) โ€” current contract
allocated recurring fee
Recurring period fee divided by the stated order-volume scenario (currency units per order) โ€” contract plus user volume scenario
applicable conditional fees
Only the other fee components triggered by the scenario (currency units per order) โ€” current contract and settlement record
Reusable fee-stack record to complete from your contract
ComponentFee base or unitCurrent valueContract or statement dateApplies when
Percentage transaction feeComplete from contractEnter valueEnter dateEnter condition
Fixed transaction feePer transactionEnter valueEnter dateEnter condition
Recurring feePer contract periodEnter valueEnter dateEnter allocation volume
Refund or retained feePer refund eventEnter valueEnter dateEnter treatment
Other conditional feeContract-definedEnter valueEnter dateEnter trigger
The intentionally empty cells prevent this durable workflow from becoming a stale provider fee table.

Reconcile a user-entered example

Normalise two contract scenarios

The values are invented user assumptions in currency units. They do not represent a provider, market or current fee schedule.

Same 80-unit order and same 400-order month
ComponentScenario AScenario B
Percentage component2.5% = 2.003.0% = 2.40
Fixed component0.300.10
Recurring fee allocated per order40 / 400 = 0.100
Normalised fee per order2.402.50
The ten-unit difference across 100 orders does not establish a winner. Refund terms, fee base, settlement, currency conversion, integration and operating fit remain separate criteria.

Keep fee source and conversion scenarios separate

Standard and buy-now-pay-later scenario hand-off
InputRequired basisSourceInterpretation limit
Standard percentage and fixed feeSame tax-excluded order value and currencyCurrent contract and settlement recordNot a provider benchmark
BNPL percentage and fixed feeSame tax-excluded order value and currencyCurrent contract and settlement recordNot a provider recommendation
Baseline conversionUser-defined cohort and periodBusiness record or labelled scenarioDoes not establish causality
Expected conversionSame cohort and periodLabelled user scenarioNot a predicted uplift
Send these aligned inputs to the BNPL Fee Impact tool. The result tests an entered fee-and-conversion scenario; it does not predict conversion or choose a provider.

Test the user-entered BNPL scenario

Compare operating fit as well as effective cost

Criteria that remain outside one headline fee
CriterionWhat to compareDecision boundary
Fee scopeBase, fixed, conditional, refund and conversion componentsUse the same order scenario
SettlementTiming, reserves, credits and reconciliation detailCost and cash timing are different measures
OperationsIntegration, controls, support and internal workDo not assign a universal value
ChannelService obligations, inventory allocation and customer reach assumptionsReach is a scenario, not guaranteed volume

Methodology sources

Expose how fixed and percentage fees change with order value

A fee stack can produce a lower effective percentage on a larger order even when no contract term changes. Keep percentage, per-order fixed, allocated recurring, marketplace, payment, fulfilment, refund and conditional charges in separate rows so the total can be reproduced against an actual statement.

Entered fee schedule

Total fee/order = order value ร— entered percentage fee + entered fixed fee + allocated recurring fee/order

Order value
Comparable customer order value on the declared tax basis (CU/order) โ€” completed orders or labelled scenario
Entered percentage fee
Current plan/contract percentage entered by the reader (percentage) โ€” current contract and settlement statement
Entered fixed fee
Per-order fixed component entered by the reader (CU/order) โ€” current contract and settlement statement
Allocated recurring fee/order
Recurring fee divided by the explicitly selected completed-order count (CU/order) โ€” current invoice and completed-order records

The fictional table uses 3%, 0.30 CU fixed and 0.20 CU allocated recurring per order. These are invented inputs, not provider prices.

Fictional unchanged fee schedule across three order values
Order value3% componentFixed + allocated recurringTotal fee/orderEffective fee percentage
25 CU0.75 CU0.30 + 0.20 = 0.50 CU1.25 CU5.00%
50 CU1.50 CU0.50 CU2.00 CU4.00%
100 CU3.00 CU0.50 CU3.50 CU3.50%
A lower effective percentage does not prove that a larger order is profitable, likely or operationally feasible.

Compare the complete entered fee stack

Change history

  1. โ€” Expanded the existing canonical owner with a bounded decision workflow, clearer interpretation boundaries and exact tool or methodology hand-offs without creating a competing article intent.
  2. โ€” Initial public release of the article after pre-launch factual, editorial, source and presentation review.