P5 · Handling payments and disputes
Preventing Payment Disputes Before They Happen
Prevent payment disputes with recognizable descriptors, clear scope and cancellation terms, written milestone acceptance, receipts, service evidence, and a complaint path.
Prevention begins before payment: describe the service, price, cancellation terms, delivery method, and timeline in writing so the card transaction is attached to an understandable bargain. Use a statement descriptor the client can recognize and repeat the business name on receipts. 'I don't recognize this charge' is easier to avoid than a quality dispute after delivery.
Show refund and cancellation terms before the client pays
Publish refund and cancellation terms where the buyer can see them before paying. A policy first revealed in a chargeback response is much harder to defend as an agreed term.
Get milestone acceptance while the project is still healthy
Get explicit milestone acceptance for larger projects. A short email—'approved, proceed to phase 2'—can be more useful later than a project-management status silently moved to done.
Most evidence is created before anyone files a dispute
Most service-business disputes can be made easier to defend before money moves. Put the service description, price, cancellation or refund rule, timing, and delivery method in writing before payment. Use a recognizable statement descriptor and send a receipt that repeats the business name the client saw in the proposal. On custom or multi-stage work, ask for written milestone acceptance rather than relying on silence or a call nobody documented. Those controls help customer service first and chargeback evidence second.
Payment design also changes risk. Charging 100% of a high-value custom project to a card months before delivery can create more exposure than a deposit followed by milestone payments. Use processor-hosted payment links instead of keeping raw card details in notes or messages. When a client complains, respond while it is still a service issue and summarize any resolution in writing. If a dispute is filed, the job changes from persuasion to evidence. The linked dispute guide can help with representment mechanics, while the processor's current portal and deadline remain authoritative. A clean packet should tell the same story the contract, receipt, delivery trail, and client messages already told.
Prevention begins before the card is charged. Make the statement descriptor recognizable, show the legal/business name consistently, and send a confirmation that identifies the project, amount, and refund/cancellation terms. For service work, convert vague progress into documented checkpoints: client approves the outline, prototype, draft, staging site, or other milestone before the next phase. Keep those approvals in writing. If the client requests a change, document the scope and price before collecting the next payment. A signed contract helps, but a six-week trail of clear delivery and acceptance is often more persuasive than relying on one broad signature at the beginning.
Design refund and cancellation rules for the way the service is delivered. A nonrefundable deposit, earned retainer, cancellation fee, or milestone payment can have legal and network-rule implications, so use wording appropriate to the jurisdiction and transaction rather than borrowing from a random template. Make the policy visible before payment and repeat important terms on the invoice or checkout where appropriate. Monitor dispute ratios and complaints by service type, customer source, invoice size, and payment method. If one sales channel produces confused buyers or one package repeatedly creates ‘not as described’ complaints, fix the offer instead of collecting more evidence after the fact. When a dispute still arrives, follow the processor’s representment workflow and reason-specific requirements; prevention reduces risk but never guarantees the issuer will decide in the merchant’s favor.
Add a high-risk transaction review for unusually large or rushed jobs. Confirm buyer identity through the normal processor/business process, verify the contract signer has authority, split delivery into milestones, and avoid taking a single large card charge for an engagement whose work will unfold over months when safer staged rails are available. Do not create invasive verification practices that violate privacy or processor rules; use the controls your payment platform supports. A business that knows its normal invoice size can spot an exception before the charge occurs. That is the moment to improve documentation and payment structure, not after the issuer has already reversed funds. Train anyone who sends invoices or communicates milestones to use the same terms as the signed agreement. A sales promise that conflicts with the contract or a casual message saying ‘unlimited revisions’ can undermine otherwise strong dispute documentation. Keep the buyer experience consistent from proposal through receipt.
Use deposits and milestone billing to limit accumulated dispute exposure
For high-risk custom work, combine a deposit with milestone billing rather than charging 100% to a card months before final delivery. Smaller checkpoints reduce both client anxiety and accumulated dispute exposure.
Preflight a $4,000 deposit before the card is charged
Pre-flight checklist for a $4,000 card deposit: signed scope, visible cancellation terms, recognizable descriptor, processor-hosted payment link, automatic receipt, kickoff confirmation, and a calendar reminder to request milestone acceptance. Each item removes a common ambiguity before it becomes a dispute.
Pre-dispute prevention controls
- Before payment
- Use a signed or affirmatively accepted scope, visible cancellation/refund terms, recognizable business name/descriptor, and a payment request tied to the exact project. Avoid collecting card data outside the processor’s secure flow.
- During delivery
- Send receipts, milestone updates, and delivery confirmations that connect the payment to the service. Ask for written approval or issue acknowledgment when the project reaches an acceptance point.
- When a complaint starts
- Respond while it is still a service problem. Clarify the scope, offer the contract-based fix/refund/cancellation path when appropriate, and keep the discussion in a channel that preserves the record.
- If a dispute is filed
- Freeze the evidence set, read the exact dispute reason and deadline, and submit only relevant, legible records through the processor. Use the outcome to improve the contract, descriptor, milestone, and refund workflow.
Before charging a card for custom work
- Make scope and cancellation terms visible pre-payment.
- Use recognizable descriptors and receipts.
- Collect milestone acceptance in writing.
- Keep card data inside processor tools.
- Address complaints before issuer escalation when possible.
- Store the version of terms and policy the client saw at payment time.
Dispute-prevention references
Prevention questions before the payment goes through
What prevents 'I don't recognize this charge' disputes?
Use a recognizable statement descriptor where your processor permits, show the same business identity on receipts and invoices, and tell the client what name will appear on the card statement. Clear identity is a simple control against avoidable friendly-fraud claims.
How does milestone acceptance help?
Written acceptance creates evidence that a defined portion of custom work was delivered and approved before the next payment or phase. It also surfaces dissatisfaction earlier, when you can still fix a service problem rather than discovering it after a chargeback.
Where should refund and cancellation terms appear?
Make them visible before payment and keep a record that the customer had access to them. Repeating the policy on the contract, checkout or invoice flow, and receipt can reduce ambiguity, but the terms still need to comply with applicable law and processor rules.
What should I do when a client complains before filing a dispute?
Respond quickly, document the issue, and try to resolve legitimate service problems through the agreed refund, cure, or change process. Once an issuer dispute opens, switch to the processor's evidence workflow and keep customer-service messages factual and consistent with the submitted record.