Imagine expecting a customer to pay $3,000. 

The customer opens your payment link, enters the amount—and accidentally types: 

$300,000. 

The payment goes through. 

A few minutes later, everyone realizes what happened. 

Obviously, you aren’t keeping the customer’s $300,000. You immediately want to reverse the transaction. 

Simple mistake. Simple fix. 

Right? 

Not necessarily. 

A merchant recently told us about this situation. According to the merchant, what should have been a $3,000 payment was accidentally entered as approximately $300,000. 

The transaction processed, and by the time the error was corrected, the merchant reported that the processing costs associated with the transaction were approximately $12,000. 

That story highlights something most businesses never think about when choosing a payment processor: 

What happens when somebody makes a mistake? 

Everyone compares processing rates. 

Everyone asks whether a processor charges 2.6%, 2.9%, 3.5% or some other number. 

Far fewer business owners ask: 

Can I void a transaction? 

When does my payment actually get captured? 

What happens to my processing fees if I have to issue a refund? 

Those questions can suddenly become extremely important. 

A $297,000 Typo Shouldn’t Become a Financial Disaster 

Entering $300,000 instead of $3,000 is obviously an extreme example. 

But payment mistakes happen every day. 

Someone enters an extra zero. 

A customer submits the same invoice twice. 

An employee charges $10,000 instead of $1,000. 

A customer selects the wrong invoice. 

Someone pays the entire outstanding balance when they intended to make a deposit. 

A staff member runs the wrong customer’s card. 

Most of these situations can be corrected. 

The question is how the transaction is corrected. 

That’s where understanding the difference between a void and a refund becomes important. 

Void vs. Refund: They Are Not the Same Thing 

To the customer, they may appear similar. 

The transaction is being reversed. 

But behind the scenes, they can be very different. 

What Is a Void? 

A void generally cancels a transaction before it has been finalized or settled. 

Stripe itself describes a void transaction as canceling a transaction before it is finalized or settled. 

Depending on the payment platform, transaction flow and timing, the merchant may be able to cancel an authorization before the transaction is fully completed. 

The money doesn’t need to travel through the entire payment cycle and then be sent back. 

That’s important. 

Stripe also explains that delayed capture can give merchants an opportunity to void an authorization when an error is discovered rather than refunding a completed payment. 

What Is a Refund? 

A refund happens after the payment has already been completed or captured. 

The transaction happened. 

The merchant received—or is scheduled to receive—the money. 

Now the merchant is sending the money back. 

Operationally, that is different from stopping the transaction before it finishes. 

And financially, the difference can be enormous. 

Here’s Where the Processing Fees Matter 

Let’s use the $300,000 mistake. 

Suppose a $300,000 transaction carried an effective processing cost of: 

2.9% 

The percentage portion alone would be approximately: 

$8,700 

At: 

3.5% 

The cost would be approximately: 

$10,500 

At: 

4% 

The cost would be: 

$12,000 

Now imagine discovering the mistake almost immediately. 

The customer gets the $300,000 back. 

But does the merchant get those processing fees back? 

Not always. 

Stripe currently states that its original payment processing fees are not returned when a transaction is refunded. 

PayPal similarly states that although it does not charge an additional fee simply to issue a goods-and-services refund, the fees paid when the merchant originally received the payment are not returned. 

That means a business can potentially lose a substantial amount of money even though the underlying sale never really occurred. 

That’s the Part Nobody Talks About When Comparing Processing Rates 

Business owners are constantly shown advertisements like: 

2.9% + $0.30 

or 

Simple flat-rate pricing. 

That sounds straightforward. 

But payment processing is about much more than the advertised rate. 

There are operational questions that may matter far more than a few basis points. 

For example: 

What happens when a transaction needs to be stopped? 

If the answer is: 

“Just refund it.” 

you need to understand what that refund actually costs. 

On a $50 transaction, nobody is losing sleep over a couple of dollars. 

On a $300,000 transaction, the financial consequences can be very different. 

Why Payment Capture Matters 

Behind every credit card transaction are multiple stages. 

In a simplified example: 

Customer enters card → Authorization → Capture → Settlement 

The authorization verifies that the card is valid and the funds or credit are available. 

Capture tells the system to complete the transaction. 

Settlement is when the transaction proceeds through the payment networks and funds ultimately move to the merchant. 

Some payment environments immediately authorize and capture a transaction. 

Others can be configured so authorization and capture occur separately. 

Stripe, for example, supports manual capture through its PaymentIntents technology. 

Neither approach is automatically better for every business. 

Immediate capture makes sense for many ordinary ecommerce purchases. 

But businesses processing: 

• Large invoices 

• B2B transactions 

• Equipment sales 

• Wholesale orders 

• Deposits 

• Professional services 

• Manufacturing invoices 

• Large-ticket transactions 

may want more control over how payments are processed. 

Large-Ticket Merchants Should Pay Particular Attention 

If your average sale is $25, there is only so much damage someone can do with an extra zero. 

If your invoices regularly run: 

$10,000 

$25,000 

$50,000 

$100,000 

or more, payment controls become much more important. 

Imagine someone intends to pay: 

$25,000 

but accidentally enters: 

$250,000. 

At a 3% processing cost, that’s potentially $7,500 associated with the transaction. 

The problem isn’t theoretical anymore. 

It has become a risk-management issue. 

Should Your Payment System Have Transaction Limits? 

This is another question businesses should consider. 

Should a customer normally be able to submit a $300,000 payment if your average invoice is $5,000? 

Maybe. 

Some businesses legitimately accept payments that large. 

But many do not. 

Depending on your payment environment, you may want safeguards such as: 

• Maximum transaction amounts 

• User permissions 

• Employee approval requirements 

• Large-transaction alerts 

• Duplicate transaction detection 

• Manual review procedures 

• Authorization-before-capture workflows 

• Dollar limits by user 

• Restricted access to refund capabilities 

Payment technology shouldn’t simply collect money. 

It should help protect the business from mistakes. 

Human Support Matters Too 

Now imagine the $300,000 transaction just happened. 

Who are you calling? 

That’s another question business owners rarely ask before choosing a processor. 

When everything works correctly, virtually every payment platform looks good. 

The difference becomes much clearer when something unusual happens. 

You might suddenly need someone who understands: 

• Authorization 

• Capture 

• Settlement 

• Voids 

• Refunds 

• Interchange 

• Transaction limits 

• Fraud controls 

• Gateway configuration 

And you probably don’t want to spend hours searching a help center while hundreds of thousands of dollars are involved. 

At Nationwide Payment Systems, we believe payment processing should include both technology and access to knowledgeable people who can help businesses understand what is happening with their transactions. 

This Is Why NPS Reviews How Your Business Actually Gets Paid 

One of the biggest mistakes in payment processing is assuming every merchant should use the same setup. 

A coffee shop processing $8 transactions has very different requirements than a distributor collecting $75,000 invoices. 

A SaaS company has different needs than a contractor. 

A manufacturer has different payment workflows than a restaurant. 

A professional-services business accepting large deposits may need completely different controls than a retail store. 

That’s why Nationwide Payment Systems looks at factors including: 

• Average transaction size 

• Monthly processing volume 

• B2B versus B2C payments 

• Card-present versus card-not-present activity 

• ACH usage 

• Invoice size 

• Payment workflow 

• Industry 

• Risk exposure 

• Refund patterns 

• Accounting integrations 

• Employee access 

Then we can help determine what payment configuration makes sense. 

Smart Invoicing Can Add Another Layer of Control 

With NPSONE Smart Invoicing, businesses can send professional invoices and payment links rather than simply asking customers to enter arbitrary amounts into a generic payment page. 

Depending on the payment workflow, businesses can collect: 

• Credit and debit cards 

• ACH payments 

• Deposits 

• Partial payments 

• Recurring payments 

• Scheduled payments 

Invoices can be delivered by email or text message, and businesses can maintain a clearer record of what the customer is actually supposed to pay. 

NPSONE can also integrate with accounting platforms including QuickBooks Online, Xero, and Sage Intacct, helping businesses keep their payment and accounting processes connected. 

For businesses collecting large invoices, having a clearly defined invoice amount can help reduce the opportunity for a customer to accidentally enter the wrong number. 

ACH May Also Make Sense for Large Transactions 

There is another conversation worth having when invoices become very large. 

Should a $100,000 or $300,000 B2B invoice even be paid by credit card? 

Sometimes the answer is yes. 

Customers may want rewards, extended terms, or the convenience of paying by card. 

But ACH may also make sense for certain transactions. 

Businesses accepting large payments should have multiple payment options available rather than automatically pushing every transaction through the same channel. 

At NPS, we can help businesses evaluate: 

Credit cards 

ACH 

Level 2 and Level 3 processing 

Surcharging where permitted 

Convenience-fee programs where applicable 

Dual pricing 

and other payment strategies. 

The goal is not simply to process the transaction. 

The goal is to determine the smartest way to get paid. 

10 Questions to Ask Your Payment Processor 

Before your next payment mistake happens, ask your processor: 

1. Can I void an unsettled transaction? 
2. When are my transactions captured? 
3. When does my batch settle? 
4. Are original processing fees returned when I issue a refund? 
5. Can I place transaction limits on employees or customers? 
6. Can unusually large transactions require approval? 
7. Can my system detect duplicate payments? 
8. Can I receive alerts when transactions exceed a certain amount? 
9. Should some of my larger payments be processed by ACH instead? 
10. Who can I call when something goes wrong? 

If you don’t know the answers, now is a good time to find out. 

Not after someone accidentally enters an extra zero. 

The Cheapest Transaction Is Sometimes the One You Stop 

Most conversations about payment processing revolve around saving: 

10 basis points. 

20 basis points. 

Half a percent. 

Those savings certainly matter. 

But preventing one large payment mistake could potentially save a business more money than shaving a small fraction off its processing rate for months. 

That is why businesses need to look beyond the advertised processing rate. 

Your processor should help you think about: 

Technology. 

Controls. 

Workflow. 

Risk. 

Support. 

And what happens when something goes wrong? 

Because eventually, something will. 

Maybe someone enters $300 instead of $3,000. 

Maybe they enter $30,000 instead of $3,000. 

Or maybe they enter: 

$300,000. 

When that happens, knowing the difference between a void and a refund could become one of the most valuable things you know about your payment system. 

Want NPS to Review Your Payment Setup? 

If you’re using Stripe, Square, PayPal, QuickBooks Payments or another flat-rate payment provider, Nationwide Payment Systems can review how you’re currently accepting payments. 

We’ll look at your: 

• Processing volume 

• Average ticket 

• Current effective processing cost 

• Refund activity 

• B2B versus B2C mix 

• Large-ticket transactions 

• Payment workflow 

• ACH opportunities 

and help you evaluate whether another pricing structure or payment configuration could make more sense for your business. 

For established businesses, especially those processing large invoices, the conversation should go beyond: 

“What’s my rate?” 

The better question is: 

“Is my payment system actually designed for the way my business gets paid?” 

Contact Nationwide Payment Systems for a payment-processing review and learn how NPS and NPSONE Smart Invoicing can help your business get paid smarter.