Skip to main content
Stripe captures the full financial lifecycle of your customers — subscriptions, invoices, disputes, and payment methods. Pipe this data into Mavera to build revenue-grounded personas, generate retention messaging for at-risk accounts, and produce case studies from real growth trajectories.
Stripe API
  • Base URL: https://api.stripe.com/v1/
  • Auth: Bearer token (Authorization: Bearer sk_live_...)
  • Encoding: Form-encoded request bodies (not JSON)
  • Rate limit: 25 requests/second per endpoint
  • Docs: stripe.com/docs/api
Mavera API
  • Base URL: https://app.mavera.io/api/v1
  • Auth: Bearer token (Authorization: Bearer MAVERA_API_KEY)

​
Prerequisites

1

Get your Stripe API key

From Stripe Dashboard → API keys, copy your Secret key (sk_live_ or sk_test_). Use a restricted key with read-only access to Customers, Charges, Invoices, Subscriptions, Disputes, and Payment Methods.
2

Get your Mavera API key

From Mavera → API Keys, generate a key with personas:write, generations:write, and brand-voices:write scopes.
3

Set environment variables

​
Jobs

​
Rate Limits & Production Notes

Never log or commit Stripe secret keys. Use environment variables or a secrets manager. Keys starting with sk_live_ have full account access — a leaked key can move money. Rotate immediately if exposed.
Production checklist:
  • Use Stripe restricted keys with read-only access
  • Implement exponential backoff for both APIs
  • Store Mavera persona IDs mapped to Stripe segments for updates
  • Test with sk_test_ + Mavera sandbox before production
  • Set up Stripe webhooks instead of polling
  • Log responses (without sensitive fields) for debugging

​
Next Steps

Stripe Webhooks

Trigger Mavera jobs from events like invoice.payment_failed.

HubSpot Integration

Combine Stripe revenue with HubSpot CRM for full-funnel personas.

Persona Management

Version, merge, and archive personas as segments evolve.

API Reference

Full reference for all Mavera endpoints used in this guide.