End-to-end quickstart
Set up Beacon with Stripe and validate the full flow in under 20 minutes.
tutorial • updated 2026-03-15
Before you start
| Requirement | Why it matters |
|---|---|
| Stripe account with Connect Standard | onboarding and payment capabilities |
| Beacon access token with integration scope | authenticated API operations |
| Public HTTPS webhook URL | secure event ingestion |
| Isolated test environment | safe validation before live |
End-to-end flow map
- Connect Stripe.
- Register and validate webhooks.
- Create subscription checkout.
- Confirm final state in dashboard.
- Validate fiscal and observability signals.
Step-by-step
11) Connect Stripe
Complete Connect Standard onboarding and verifycharges_enabledin dashboard.22) Configure webhooks
Register endpoints, store signing secret in a vault, and validate signatures.33) Create checkout
Create checkout session withIdempotency-Keyand redirect the user.44) Confirm outcome
After return callback, confirm subscription state and related event processing.55) Validate operations
Check final state across dashboard, logs, and key metrics.
API example
curl -X POST https://api.beacon.pt/v1/billing/subscription-checkouts \
-H "Authorization: Bearer <access_token>" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: chk_<operation_id>" \
-d '{"organizationId":"<organization_id>","plan":"plus","billingCycle":"monthly","mode":"test"}'
Final validation
- Checkout completes and subscription confirmation is consistent.
- Webhook processed with correlation by
event.id. - Dashboard state matches billing and operational timeline.
- No critical alerts in observability.
Quick troubleshooting
| Symptom | Likely diagnosis | Immediate action |
|---|---|---|
| checkout created but state unchanged | missing confirmation step | call .../confirm and verify events |
| webhook rejected | invalid signature | rotate/revalidate secret and clock drift |
409 conflict | duplicate logical operation | reuse first result and stop re-submitting |