IdempotencyKey · StripeWebhookEvent · PlaidWebhookEvent

Idempotency & Deduplication Hashing

The architectural guarantee that processing the same API request, webhook delivery, or bank statement import multiple times produces the exact same ledger result without creating duplicate entries.

Payment processors (Stripe) and banking networks (Plaid) deliver webhooks on an 'at-least-once' basis—meaning the same invoice.paid or TRANSACTIONS_REMOVED event may arrive 3 times if a network timeout occurs. Raindum stores unique event IDs in StripeWebhookEvent, PlaidWebhookEvent, and IdempotencyKey collections so retries are safely acknowledged without double-posting to your ledger.
Formula / Posting
f(f(x)) === f(x) · Duplicate Webhook / Import Retry → HTTP 200 { received: true, duplicate: true }
In Raindum
Backend Infrastructure (IdempotencyKey, StripeWebhookEvent, PlaidWebhookEvent, CSV Import Hasher)Importing Bank Statements, CSVs & Historical Accounting Records

How Idempotency & Deduplication Hashing applies across operating models

Startups
Prevents double-counted revenue or duplicate burn lines when bank APIs retry webhook deliveries.
Businesses & Enterprises
Allows staff to re-upload overlapping monthly CSV bank statements without creating duplicate ledger rows.
Self-Employed
Guarantees clicking 'Submit' twice on a slow internet connection never posts two invoices or two expenses.
Accountants & CPAs
Satisfies the Existence/Occurrence audit assertion by preventing duplicate ledger postings at the database index layer.

More in Banking & Reconciliation