Design a Donation Service with Reliable Payment State

Quick Overview

Design a donation service with durable payment intent, idempotent provider calls, verified callbacks, pending-state handling, and failure reconciliation.

Design a Donation Service with Reliable Payment State

Company: DoorDash

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

Design a donation service that lets a user select a beneficiary and submit a donation. Explain how the system records payment intent, calls a payment provider, and recovers from failures without losing or duplicating donations. ### Clarifying Questions to Ask - Which currencies, eligibility rules, and beneficiaries are supported? - Is payment confirmation synchronous, asynchronous, or both? - Are refunds and beneficiary payouts part of this design's scope? ```hint Persist intent before relying on a response A network failure can separate the provider's outcome from what your application observes. ``` ### What a Strong Answer Covers - Durable donation records and a defined payment state machine. - Idempotent submission, authenticated callbacks, and reconciliation. - Sensitive-data boundaries and operational visibility. ### Follow-up Questions - How do you distinguish an unknown payment outcome from a confirmed failure? - What should happen when the same provider event is delivered twice?

Overview: Design a donation service with durable payment intent, idempotent provider calls, verified callbacks, pending-state handling, and failure reconciliation.

Read the full DoorDash Software Engineer interview experience this question came from

DoorDash logo
DoorDash
Nov 15, 2026
mediumSoftware EngineerOnsiteSystem Design
0
0

Design a donation service that lets a user select a beneficiary and submit a donation. Explain how the system records payment intent, calls a payment provider, and recovers from failures without losing or duplicating donations.

Clarifying Questions to Ask Guidance

  • Which currencies, eligibility rules, and beneficiaries are supported?
  • Is payment confirmation synchronous, asynchronous, or both?
  • Are refunds and beneficiary payouts part of this design's scope?

What a Strong Answer Covers Guidance

  • Durable donation records and a defined payment state machine.
  • Idempotent submission, authenticated callbacks, and reconciliation.
  • Sensitive-data boundaries and operational visibility.

Follow-up Questions Guidance

  • How do you distinguish an unknown payment outcome from a confirmed failure?
  • What should happen when the same provider event is delivered twice?