2 auth methods · updated 2026-10-01
Stripe connects two ways: a key you create yourself, or Stripe's own sign-in. Both give Verslay read access to what you approve. Start with a restricted key or a test-mode key if you only want to try it.
stripe.com ↗Uses your own credential — Verslay stores it encrypted
Your Stripe secret key — starts with sk_live_ (or sk_test_ for test mode), not the publishable pk_ key. Find it at https://dashboard.stripe.com/apikeys.
Matches every Stripe payment, fee, and refund against your orders.
Unpaid Stripe invoices get polite, aging-appropriate reminders.
Failed and expiring subscriptions get one personalized recovery email each.
What came in, what went out, refunds, fees, and MRR movement.
The Verslay agent built around Stripe revenue operations.
Use a restricted key when you can. It gives the least privilege that still works. Stripe's own dashboard at dashboard.stripe.com/apikeys is where you create it.
Yes. Test mode keys (sk_test_) connect safely for evaluation. Swap to live keys when you are ready.
OAuth opens Stripe's official sign-in and Verslay only gets the scopes you approve. The key route uses your own credential, which Verslay stores encrypted.
Connect the new credential first, confirm it works, then revoke the old one.
See also Verslay use cases and agents.
Verslay agents share your connections. Connect Stripe in the Hub and every use-case that needs it lights up — no per-agent setup.
Open the Hub →