mufassall

Business processes / 4 / 12

Payment reconciliation

A shop records card payments from the provider's answers and callbacks. Some of them get lost, time out or arrive twice, so the ledger and the real money drift apart. Every morning a job compares the ledger with the provider's settlement report, fixes what is safe to fix and hands the rest to a person.

  • 14 min
  • Intermediate
  • 11 steps
Mismatches
0 /day
Unmatched amount
0 $
Fixed automatically
0 %
Open review cases
0
Open in Lab

  • request
  • reply
  • redelivery
  • duplicate
  • lost

Numbers are a model scenario, not measurements

The real request

Provider → Payments API

Request

POST /payments/callback HTTP/1.1
Host: api.example.com
Signature1: hidden

{
  "event": "charge.succeeded",
  "provider_txn_id": 2"ptx_8812",
  "order_id": "ord_3301",
  "amount_minor": 3129000,
  "currency": 4"USD"
}

Response

HTTP/1.1 200 OK
  1. Signature · hidden — Proves the callback came from the provider. A shared secret, hidden here.
  2. provider_txn_id — The provider's id for this payment. It is the key everything is matched on later.
  3. amount_minor — 129000 cents = $1,290.00. Integers add up exactly; floats like 0.1 + 0.2 do not, and 48 000 rows of rounding errors become real money.
  4. currency — Always stored next to the amount. Minor units differ: 2 digits for USD, 0 for some currencies, 3 for others.

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