Why void transaction matters to a first-time founder
Voiding a mistaken transaction quickly can prevent money from settling and keep records accurate. If a founder treats a void as a refund, customer communications, fees and reconciliation may be wrong. Payment processors, banks and accounting systems use the term differently, so the system’s documented status controls.
Examples of void transaction
A customer is accidentally charged ₹24,000 instead of ₹2,400. The merchant voids the card authorisation before the day’s batch closes, so the ₹24,000 should not settle. The customer may still see a temporary pending amount until their bank releases the authorisation.
Common misunderstanding
A void is usually not a refund. Voiding stops an authorised transaction before final settlement; a refund sends money back after a completed payment. It is also different from a chargeback, where a customer asks their bank to reverse a payment through a formal dispute process.
When to use it
Use a void when a duplicate, incorrect or cancelled payment has not yet settled and your provider supports reversal. Record who approved it and tell the customer what they may see. Once settlement has occurred, follow the provider’s refund process rather than trying to relabel the completed transaction.