Overview

Stripe is the external payment processor we use to charge customer cards. It is owned and operated by Stripe, not by our team — it is modelled here as an external system so the catalog can show how our Payment Gateway Service Payment Gateway Service Service • v0.0.1 Manages integration with external payment processors (Stripe, PayPal, etc.) Publishes PaymentFailed , ChargeCard Subscribes ProcessPayment , FraudCheckCompleted +2 Owner dboyne Map Repo View docs integrates with it.

The Payment Gateway Service Payment Gateway Service Service • v0.0.1 Manages integration with external payment processors (Stripe, PayPal, etc.) Publishes PaymentFailed , ChargeCard Subscribes ProcessPayment , FraudCheckCompleted +2 Owner dboyne Map Repo View docs sends Charge Card Charge Card Command • v0.0.1 Request sent from PaymentGatewayService to Stripe to charge a customer's card. Maps to Stripe's `POST /v1/charges` API. Map View docs requests to Stripe and consumes the resulting webhook events:

• Stripe Charge Succeeded Stripe Charge Succeeded Event • v0.0.1 Stripe webhook event delivered when a charge completes successfully Map View docs — delivered when a charge completes
• Stripe Charge Failed Stripe Charge Failed Event • v0.0.1 Stripe webhook event delivered when a charge attempt fails Map View docs — delivered when a charge is declined or errors

API Version

We pin to Stripe API version 2024-06-20. When Stripe releases a new API version we evaluate the changelog before bumping. The catalog version (1.0.0) tracks our integration contract, not the upstream Stripe API date.

Webhooks

Stripe webhooks are delivered to POST /webhooks/stripe on the Payment Gateway Service Payment Gateway Service Service • v0.0.1 Manages integration with external payment processors (Stripe, PayPal, etc.) Publishes PaymentFailed , ChargeCard Subscribes ProcessPayment , FraudCheckCompleted +2 Owner dboyne Map Repo View docs . The signing secret is rotated quarterly and stored in AWS Secrets Manager.