The APIs
Stripe
Hosted one-time credit-pack checkout and signed payment notifications for verified customer credit fulfillment.
The facts a reader needs
| What it unlocks | Card checkout for credit packs and the signed payment notification that grants the credits. Off until the merchant account is confirmed; no report, balance read or provider call goes through it. |
| When it is called | Only for explicitly enabled credit checkout or fulfillment of already-paid sessions. Test mode is restricted to exact disposable QA users. No report acquisition or provider-balance read uses Stripe. |
| Cost basis | Payment-processing fees depend on the configured merchant account. Customer payment, granted product credits and report-provider spend are separate; no fee or payout balance is inferred here. |
| Environment | STRIPE_SECRET_KEY STRIPE_WEBHOOK_SECRET |
| Bring your own key | Not on this deployment. |
Session-only checkout creation and owner-scoped confirmation; signed webhook fulfillment re-fetches the paid session and requires durable idempotent ledger readback.
Endpoints we call
| Endpoint | Why we call it |
|---|---|
POST v1/checkout/sessions | A hosted checkout page for one credit pack, created only from a signed-in session. |
GET v1/checkout/sessions/{id} + signed webhook | Confirming a paid session before exactly one credit grant is written to the ledger. |