mufassall

Business processes / 11 / 12

Refunds and chargebacks

A shop gives money back in two ways: it refunds on its own, in full or in part, or the cardholder's bank takes the money back through a chargeback. Both look like "minus some amount", and both break in the same places: an edited payment row, a click sent twice, two agents refunding at once, a status that only arrives later by webhook, and a dispute deadline nobody watched.

  • 14 min
  • Intermediate
  • 12 steps
Refunds paid twice
0 /mo
Refunds above captured
0 /mo
Refunds with a wrong status
0
Chargebacks lost
0 %
Report lines that differ
0
Open in Lab

  • request
  • reply
  • redelivery
  • duplicate
  • lost
  • call: the reply returns on the same line

Numbers are a model scenario, not measurements

The real request

Refund service → Payments DB

Request

SELECT id, status, captured_minor FROM payments WHERE id = 'pay_7731';1

Response

pay_7731 | captured | 4500002
-- order ord_5120: 3 items, 4 500.00 paid by card **** 44173
-- the customer returns 1 item of 1 500.00 and asks for the money back4
  1. captured_minor — How much the provider actually took from the card, in cents.
  2. captured — The payment is final: money moved, it can only be given back, not cancelled.
  3. **** 4417 — Only the last four digits are stored and shown; the full card number never reaches the shop.
  4. 1 500.00 — A partial refund: one item out of three.

Build it yourselfCheat sheetCompare lessons

Course: 74 lessons
  1. 01 Foundations

    1. The life of a request
    2. Latency and throughput
    3. Napkin math
  2. 02 Scaling

    1. Scaling up vs scaling out
    2. Load balancing
    3. Stateless servers
    4. Caching
    5. Cache invalidation
    6. CDN and edge caching
  3. 03 Data & storage

    1. SQL and NoSQL
    2. Database indexes
    3. Geo search: who is nearby
    4. Full-text search
    5. Vector search
    6. Storage engines: B-tree and LSM
    7. Bloom filters
    8. Database replication
    9. Sharding
    10. Consistent hashing
    11. Unique IDs
    12. CAP: when the link breaks
    13. Consensus and leader election
    14. Transactions
    15. File uploads
  4. 04 Communication

    1. API styles
    2. Message queues
    3. Pub/sub and event logs
    4. Real-time updates
    5. Reliable callbacks
    6. Sending webhooks reliably
  5. 05 Reliability

    1. Redundancy and failover
    2. Rate limiting
    3. Timeouts and retries
    4. Observability
    5. SLOs and error budgets
    6. Backpressure
  6. 06 Architecture

    1. Microservices
    2. Service discovery
    3. Sagas and the outbox
    4. Change data capture (CDC)
    5. Transactional outbox
    6. Distributed locks
    7. Batch vs stream
    8. Multi-tenancy
    9. Event sourcing
  7. 07 Security

    1. Authentication
    2. Authorization
    3. Encryption and secrets
    4. Secrets management
  8. 08 Shipping

    1. Testing
    2. CI/CD: from commit to production
    3. Zero-downtime migrations
    4. Feature flags
  9. 09 Whole systems

    1. From requirements to design
    2. Design a URL shortener
    3. Design a news feed
    4. Design a chat
    5. Design a video streaming site
    6. Design search autocomplete
    7. Design a job scheduler
  10. 10 Business processes

    1. Payment gateway
    2. Money and rounding
    3. Double-entry ledger
    4. Payment reconciliation
    5. Subscription billing
    6. Electronic digital signature
    7. Document lifecycle
    8. Audit log
    9. Notification delivery
    10. Bulk import
    11. Refunds and chargebacks
    12. Gapless document numbering
  11. 11 Case studies

    1. Case: how Discord stores messages
    2. Case: Figma multiplayer editing