Visiting Cards and Wedding Cards: Taking Order Advances on Cards

Published: 23 October 2026

Category: buying-guides | cardbuzz

Tags: visiting cards, wedding cards, order advances, payment links, gst time of supply

No print shop prints a wedding card order on a promise. Advances — typically a part of the order value upfront, the balance on delivery — are the industry's immune system against cancellations and design-change disputes. Taking those advances on cards, through POS or payment links, makes the advance easier for the customer and gives you a clean digital trail. This guide covers how to structure advances, the GST timing rules that apply to them, and how to handle the refunds and changes that wedding season inevitably brings.

Why advances exist and how to set them

An advance does two jobs: it commits the customer, and it funds your upfront costs — special paper, foil dies, plate-making, designer time. Set the advance high enough to cover your sunk costs if the order dies, but not so high that it scares the customer. For visiting cards (small, standardised, quick turnaround), a modest advance or even full prepayment is normal. For wedding cards (large value, customised, long lead time), stage it: a booking advance to start design and die-making, and the balance when the printed lot is ready for collection. Whatever you set, put it in writing on the order form — amount, what it covers, and what happens to it if the customer cancels.

Taking advances on cards: the practical routes

At the counter, a POS swipe or QR works for walk-in advances. For customers finalising designs over WhatsApp, a payment link is the workhorse: send it with the order confirmation, and the advance lands with a reference you can match to the job. Payment links typically carry a slightly higher MDR than counter swipes, so factor that into your pricing rather than adding it to the customer's bill. For corporate visiting-card orders, ask whether the client prefers a link or a formal proforma invoice against which their accounts team releases payment — large companies often cannot pay a link and need the invoice route. Match every advance to its order number the same day; wedding season volume makes next-week reconciliation a nightmare.

GST on advances: the time-of-supply rule in plain words

Under GST, tax on an advance is generally due when you receive it, not when you deliver the job — this is the time-of-supply rule for advances. In practical terms: when a customer pays a wedding-card advance, that receipt is a taxable event and the GST on it belongs in that month's return, even though the cards ship weeks later. When you deliver and raise the final invoice, you adjust for the advance already taxed. The mechanics vary with registration type and the nature of the supply, so confirm the exact treatment with your tax advisor — but the discipline is universal: log every advance with its date and amount, because your GST return must reflect money received, not just jobs delivered.

Linking large wedding orders to EMI — carefully

Some customers ask to pay a large wedding-card bill in instalments. If you accept cards, you can offer to run the full amount as a single charge and let the customer convert it to EMI through their own issuer app — the EMI is between the customer and their bank, and you receive the full amount (less MDR) on settlement. Do not offer to "split it into monthly charges" yourself by storing card details and charging monthly: you would be taking on collection risk, PCI-type data risk, and a reconciliation mess. If the customer wants instalments, the single-charge-plus-their-EMI route keeps your books clean and your cash flow whole.

Refunds, design changes and cancelled orders

Wedding orders change: the date shifts, the design is reworked, sometimes the order is cancelled outright. Your advance policy decides whether these moments are arguments or transactions. Write the policy on the order form: the booking advance covers design and die costs and is non-refundable once work begins; the balance is refundable if you have not printed. When a refund is due on a card advance, process it as a card refund to the same card — never as cash or a fresh UPI transfer, because the audit trail must show the money returning along the path it came. Card refunds take a few working days to reach the customer; tell them so upfront. For design changes after approval, charge a revision fee rather than reopening the whole price — it protects your designer time and teaches customers to approve carefully.

Documentation that prevents disputes

Every advance should generate four things: a written order form (specification, quantity, rate, advance amount, delivery date, cancellation policy), a payment receipt referencing the order number, a design approval (a signed proof or a clear "approved" message on the chat thread), and a delivery acknowledgement. Wedding families sometimes dispute through a relative who was not part of the original discussion — your paperwork is what settles it. Store these digitally by order number; a phone gallery full of unsorted proof photos is not a filing system.

An advance routine for busy season

Fix your advance slabs before the season starts, print them on the order form, and brief your counter staff so every customer hears the same terms. Route counter advances through POS or QR, remote advances through payment links matched to order numbers daily. Log every advance for GST time-of-supply the same week it arrives. Offer the single-charge-plus-customer-EMI route for large bills instead of informal instalments. Process refunds back to the source card with a clear timeline communicated upfront. Advances taken cleanly are working capital; advances taken messily are disputes waiting for their date.