Skip to content

Proposed pricing

Straightforward enough to plan around.

Use the target model below to estimate your starting economics. It is illustrative, not a binding processor rate.

The starting model

2.00% + $0.20 per card transaction

Customer processing charge = (card volume × 2.00%) + ($0.20 × number of card transactions) + disclosed pass-through or optional fees.

2.00%proposed card rate
$0.20per card transaction
Planned $0 initiallymonthly platform fee, subject to final terms
Quoted separatelyrefunds, disputes, ACH, and optional services

Proposed starting model. Pricing may vary by business type, risk, card mix, volume, underwriting, and final partner terms.

Use your own recent month as the best planning reference. Count the card volume, count the transactions, and note which channels, refunds, disputes, recurring charges, or optional services affect the business. That context helps the sales team explain where the proposed model fits and where a final quote may need additional detail.

Illustrative only

See how the math works.

These examples exclude pass-through or optional service fees.

$100 card transaction$2.00 + $0.20 = $2.20
1,000 transactions · $50,000 volume$1,000 + $200 = $1,200
$250,000 monthly volume$5,000 + $0.20 × transaction count

Need a final quote?

Request pricing and share the details that shape an approved offer.

Pricing that can be explained

Build a forecast around real transaction behavior.

A percentage rate is only one part of payment economics. The per-transaction amount, card mix, average ticket, refunds, disputes, ACH activity, and optional services all influence the final cost. MatosPay presents the proposed model in plain language so owners can compare scenarios before they commit to a new provider or workflow. The examples on this page are illustrative and should be used for planning, not as a binding quote.

When you request pricing, share your estimated monthly volume, average ticket, business type, sales channels, and recurring-billing needs. Those details help the team identify the right questions and avoid a one-size-fits-all recommendation. A business with many small card transactions may experience the per-transaction component differently from a business with fewer, larger tickets. A seasonal operator may need a different conversation from a subscription business or a company that accepts payments in person and online.

Final terms remain subject to business review, risk considerations, card mix, volume, underwriting, processing-partner availability, and any pass-through or optional services. The goal is a transparent starting point, a clear explanation of assumptions, and a quote that can be reviewed by the people responsible for the business.

Plan with your own numbers

An illustrative estimate in seconds.

Adjust the inputs below to understand the proposed model. This is planning math, not a quote.

Illustrative planning toolUpdates instantly
Try an example
Illustrative monthly card cost2.00% proposed rate + $0.20 per card transaction
$1,200.00
$1,000.00 percentage component$200.00 transaction component

Make the quote easier to review

Know which details can change the final number.

A transparent estimate is more useful when its assumptions are visible.

What is excluded?

Pass-through fees, optional services, refunds, disputes, ACH activity, and partner-specific terms may change the final economics.

Why does transaction count matter?

The per-transaction amount affects businesses differently depending on average ticket size and the number of monthly card payments.

What should I bring to a pricing call?

Bring a recent month of volume, transaction count, average ticket, sales channels, business type, and recurring or refund needs.