Payment Pricing Models Explained

Direct answer

A pricing model determines how underlying card and network costs, processor margin, and other service charges appear on the merchant bill. Interchange-plus usually shows wholesale interchange plus an agreed markup. Flat-rate or blended pricing applies one or a few packaged rates. Tiered pricing groups transactions into processor-defined buckets. Subscription or membership models commonly combine a recurring fee with per-transaction or basis-point charges. None is automatically cheapest or most transparent for every business. Compare models using actual channel, card, ticket, refund, and transaction-count data, then add every fixed and incidental cost and examine how the agreement permits prices to change.

What each model changes

Interchange-plus can make processor markup easier to identify, but statements may still include network, authorization, platform, and account charges. Flat-rate pricing simplifies forecasting, yet the spread between the packaged rate and underlying cost is not normally itemized and different rates may apply to keyed, online, invoice, international, or manually entered activity. Tiered plans classify transactions as qualified, mid-qualified, or non-qualified under definitions the processor controls; ask for written qualification rules and downgrade data. Membership or subscription pricing is not “at cost” merely because it has a monthly fee: identify all percentage, transaction, annual, gateway, and ancillary charges and test whether volume supports the recurring cost. Dual pricing, cash discounts, and surcharging are customer-price or tender-treatment programs rather than substitutes for understanding the underlying processor schedule. Dual pricing presents two prices, a genuine cash discount reduces a real regular price, and a surcharge separately adds an eligible credit-card amount under applicable rules. Their practical fit depends on customer price display, debit mix, receipts, staff training, software behavior, provider approval, network requirements, and jurisdiction-specific review. Also distinguish gross settlement from net settlement and processor pricing from separate POS, gateway, device, or software billing.

Normalize two proposals

Assume 1,000 monthly transactions and $60,000 in volume. Proposal A estimates wholesale costs of $1,020, adds 0.30% ($180), $0.08 per transaction ($80), and $45 monthly, totaling $1,325. Proposal B quotes 2.20% plus $0.10 per transaction and $20 monthly, totaling $1,440. On those assumptions A is $115 lower. But if the $1,020 wholesale estimate was based on an unrealistically favorable card mix, the result changes. Run the merchant’s actual transaction sample through both schedules, include card-not-present rates, refunds, authorization-only events, chargebacks, minimums, annual fees, software, and equipment, and show a plausible range rather than a single promised number. Effective cost here is total modeled fees divided by modeled volume; it is an analytical ratio, not the advertised rate.

Build a topic-specific comparison

For interchange-plus, flat-rate, tiered, blended, and membership pricing, compare like with like and retain the evidence behind every score. Collect the same transaction-level sample from the operating business, label its date and owner, and note whether it represents a fact, requirement, assumption, or unresolved dependency. Compare complete schedules under the same locations, channels, volume period, user roles, and exception conditions; reject a demonstration that changes the scenario between providers. Define an acceptance result for card-present and remote activity, identify which document or reproducible test proves it, and record limitations instead of reducing the result to yes or no. Ask who supplies, configures, bills, supports, and can change refunds; preserve the answer with the controlling proposal or agreement rather than relying on a meeting note. Test authorization counts with ordinary and difficult cases from this business, including a correction or failure path, so the comparison reflects daily work instead of a sales script. Score seasonal months separately for current fit, implementation effort, continuing ownership, and exit risk; a strong feature can still create an unacceptable operational dependency. Collect equipment terms from the operating business, label its date and owner, and note whether it represents a fact, requirement, assumption, or unresolved dependency. Compare every recurring charge under the same locations, channels, volume period, user roles, and exception conditions; reject a demonstration that changes the scenario between providers.

Calculate the relevant costs

The cost model for interchange-plus, flat-rate, tiered, blended, and membership pricing should expose dollars, timing, uncertainty, and operational effort. Quantify wholesale card costs as one-time, recurring, usage-based, loss-related, or internal labor, and state the time period and transaction assumptions behind the amount. Model basis-point markup at low, expected, and stressed activity, because a fixed monthly price and a per-event price behave differently as volume changes. Trace per-item charges to a proposal line, contract term, invoice, operating record, or documented estimate; leave it marked unknown when the evidence is incomplete. Identify which party controls qualification downgrades, what can trigger a change, whether notice is required, and whether the expense continues during migration or termination. Measure monthly membership separately from revenue or gross payment volume so a percentage headline does not hide dollars, staff effort, customer loss, or cash-flow timing. Reconcile actual gateway events after launch to the approved model, investigate the variance, and update the forecast without retroactively changing the original assumptions. Quantify minimums as one-time, recurring, usage-based, loss-related, or internal labor, and state the time period and transaction assumptions behind the amount. Model annual items at low, expected, and stressed activity, because a fixed monthly price and a per-event price behave differently as volume changes. Trace hardware to a proposal line, contract term, invoice, operating record, or documented estimate; leave it marked unknown when the evidence is incomplete. Identify which party controls software, what can trigger a change, whether notice is required, and whether the expense continues during migration or termination. Measure termination exposure separately from revenue or gross payment volume so a percentage headline does not hide dollars, staff effort, customer loss, or cash-flow timing.

Common mistakes

Use these failure patterns as review prompts, then document the control or owner that addresses each one.

• Comparing only the largest printed percentage ignores per-item and recurring charges.
• Treating interchange as one fixed rate ignores card product, merchant category, channel, data quality, and network differences.
• Assuming flat rate means all transactions receive one rate overlooks keyed, online, international, or special categories.
• Calling a membership plan zero-markup without testing every non-wholesale fee is unsupported.
• Projecting savings from a single month without contract and volume assumptions creates false precision.

Implement and test this topic

Implementation for interchange-plus, flat-rate, tiered, blended, and membership pricing is complete only when topic-specific success and failure paths have passed. Turn this into a witnessed acceptance test: reprice an identical month under each schedule. Record the starting configuration, expected result, actual result, identifiers, owner, and follow-up for any exception. Assign a trained role to test low and high volume, restrict permissions to what that role needs, and document the exact point where staff must stop and escalate. Exercise identify unpriced events in normal operation and under a realistic failure, correction, timeout, or duplicate condition; a single successful attempt is not adequate evidence. Pilot compare expected invoices with limited exposure where practical, preserve a continuity or rollback path, and name the person authorized to pause the launch. Verify reporting and reconciliation after audit the first live bill against the model, because a customer-facing success message does not prove settlement, downstream synchronization, or correct accounting.

Verify the decision

Verify interchange-plus, flat-rate, tiered, blended, and membership pricing with current, appropriately authoritative material and reproducible business records. Use current network interchange publications for the claims it is positioned to support, save its publication or version date, and distinguish direct evidence from interpretation. Cross-check final provider fee schedules against the implemented configuration and the controlling agreement; general documentation may not describe negotiated terms or enabled features. Record who reviewed signed agreements, when it was reviewed, what question it answered, and which material uncertainty remains before a decision can be approved. Recheck actual merchant transaction files whenever the provider, network rule, jurisdiction, product version, sales channel, or business workflow changes materially. Preserve written answers about classification and price-change provisions with related correspondence and test results so another reviewer can reproduce the conclusion without depending on memory or vendor assurances.

Primary and authoritative sources

Links were accessed 2026-09-08. Confirm the current version before relying on a rule or requirement.

1. Interchange reimbursement fees — Visa
2. Interchange programs and rates — Mastercard
3. What are credit card processing fees? — Federal Trade Commission