Simple Stripe Donation: A Lean Payment Solution for Drupal 10 & 11

When deploying personal blogs, NGO websites, or community platforms on Drupal, the requirement to accept credit card donations is incredibly common. However, the default reflex within the Drupal ecosystem is often to install the Drupal Commerce suite.

While Drupal Commerce is an outstanding e-commerce framework, if the use case is simply "a reader wants to donate $5 to support the author," dragging in the entire commerce ecosystem represents a massive architectural and maintenance trade-off.

• Domain Complexity: Introducing abstractions like Store, Order, Order Item, Cart, and Customer Profile creates far more domain complexity than the use case actually requires.
• PCI DSS Compliance: Self-hosting a credit card input form on the website demands rigorous security standards and compliance overhead.
• Asynchronous Reliability: Asynchronous payment transactions are prone to duplicate states without a secure Webhook handling mechanism and strict idempotency.

Design a completely standalone module, decoupling the logic entirely from carts and orders:

• Offload Payment UI: Utilizing Stripe-hosted Checkout significantly reduces the Drupal application's PCI DSS compliance scope, as card information is entered and processed entirely on Stripe's infrastructure.
• Event-driven & Idempotency: Building a dedicated webhook endpoint to handle asynchronous flows from Stripe, guaranteeing data integrity.
• Drupal Native Integration: Leveraging Drupal Core's Block API and Form API to provide a flexible UI for administrators.

Instead of manually managing the transaction state on the frontend UI, the module acts purely as an integration layer between the user and Stripe.

[ User on Drupal Site ]
      │
      ▼ Synchronous flow
[ Drupal Controller / Service ]
      │ (Create Checkout Session)
      ▼
[ Stripe Hosted Checkout ]
      │ (Payment Processing)
      ▼
[ Stripe Server ]
      │
      │ Asynchronous flow (Webhook)
      ▼
[ Drupal Webhook Endpoint ]
      │
      ├── Signature Verification
      ├── Idempotency Check
      ├── Persist Donation State
      └── Dispatch Event (DonationSuccessEvent)

This architecture clearly illustrates the separation of concerns: Drupal handles internal business logic, Stripe manages the payment UI and card security, and the two communicate via reliable Webhooks.

• System Streamlining: Completely eliminated the dependency on Drupal Commerce for one-time donation use cases.
• Security First: Card information is never processed or stored on the Drupal application; the payment lifecycle happens entirely on Stripe Checkout.
• Open Source: Released under the GPL-2.0-or-later license, ready to be dropped into any Drupal 10/11 project.

Let Stripe own the payment UI; let Drupal own the business integration. Not attempting to own complex, high-risk domains (like credit card processing) keeps the codebase lightweight, secure, and highly reliable.

Design for evolution: Dispatching a custom event after successfully saving a transaction allows the module to be easily extended later (e.g., triggering emails, logging to a CRM) without modifying the core logic.

Technical Deep Dive: I wrote a dedicated architectural note on why I chose to build a standalone donation module instead of utilizing Drupal Commerce. Read more here: Why I Skipped Drupal Commerce for a Simple Donation Feature.