Stripe (Security Config)
Collect webhook-endpoint configuration and account security settings as read-only PCI-adjacent compliance evidence through the Stripe API. Scoped strictly to security configuration, not payment, billing, or customer financial data, and NOT a substitute for a real PCI DSS assessment. Note: Stripe does not expose API-key listing/rotation status via the API for security reasons, so key-management evidence must be tracked manually.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Read-only API inventory endpoint checks
- Evidence assets generated through the generic HTTP connector
Endpoints this template queries
The exact Stripe (Security Config) API endpoints called once connected. All read-only GET requests unless noted.
- GET/account
- GET/webhook_endpoints
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://api.stripe.com/v1)
- Endpoints (JSON)(prefilled: [ { "id": "account", "name": "Account", "path": "/account" }, { "id": "webhook-endpoints", "name": "Webhook endpoints", "path": "/webhook_endpoints" } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Stripe (Security Config) evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Stripe (Security Config) evidence
Get a guided demo, or start by scanning any domain for free.