Stripe
Add Carden-prepared commercial fields to an existing Stripe payment flow and confirm payment activity from signed Stripe webhooks.
On this page
Your backend owns the Stripe payment
Carden returns supported enrichment fields for the merchant's existing Stripe payment request. Signed Stripe webhooks confirm payment activity and update refunds and disputes. Webhook delivery does not import historical charges, balance transactions, or itemized fee reports; a separately pasted restricted read-only Stripe key (Charges: Read and Balance: Read only) lets Carden sync balance transactions into settlement and fee evidence on a schedule. The merchant keeps its own Stripe payment credentials, confirmation flow, and payment idempotency; webhook confirmation is separate from settlement evidence and verified savings.
| System | Responsibility |
|---|---|
| QuickBooks | Authoritative invoice and accounting facts when the linked-source workflow is used. |
| Carden | Invoice validation, prepared Stripe fields, immutable preparation history, and signed Stripe payment-event evidence. |
| Merchant backend | The existing Stripe payment request, merchant credentials, customer/payment-method selection, and normal checkout confirmation. |
| Stripe | Payment processing, provider events, balance transactions, and settlement records available to the merchant. |
Choose a supported implementation mode
| Mode | Use it when | Carden scopes |
|---|---|---|
| Linked QuickBooks source | One imported, fully unpaid invoice maps to the payment. | invoices:read + enrichment:write; signed Stripe webhooks supply payment confirmation. |
| Inline CanonicalInvoice | Your backend already has a complete authoritative CanonicalInvoice v1. | enrichment:write; add payments:write for reports. |
| Reporting only | An existing service optionally submits observations, not connected Stripe confirmation. | payments:write. |
These modes are independent. Linking QuickBooks does not change existing keys or remove inline and reporting-only paths. Use separate keys when preparation and reporting run in services with different responsibilities.
Implement Stripe in order
Setup
Link a source when needed, create least-privilege keys, and validate test mode.
Getting started
Enrich the existing payment request and read confirmation from signed Stripe events.
Stripe API usage
Send direct HTTP requests for preparation and optional reporting.
Troubleshooting
Recover provider, preparation, correlation, and delivery failures safely.
Keep the settlement boundary explicit
Carden confirms Stripe payment state from signed webhook events delivered to the configured Carden endpoint. Signed deliveries confirm that a Stripe event reached Carden; a verified signature is not a verified capture, settlement, or savings result. Settlement and cost evidence come from the scheduled balance-transaction sync when a restricted read-only key is connected: each Stripe balance transaction becomes a settlement row with gross, fee, net, and availability date, and each fee_details line is kept verbatim. Those are processor-reported costs, not an interchange category or network qualification result.
Use actual Stripe settlement and cost evidence, an evidenced qualification baseline, and the merchant's pass-through pricing terms before calculating verified savings. Keep processor markup and unrelated fees separate from any webhook-confirmation summary.