Chrome extension payments in your own Stripe account
Payment orchestration through one unified API for multiple providers
Stage
Not given
Not given
Founded
Not given
Not given
Based in
Not given
Not given
Pricing model
Freemium
Freemium
Pricing
Hobby: free, takes 0.5% of each sale. Pro: $25 a month per workspace, or $20 a month billed yearly, with 0% fee on sales. Launch offer: first 3 months of Pro free with code PRODUCTHUNT, until 1 Nov.
Not given
Key features
Licenses, subscriptions, free trials and paywalls integrated with a single command
Offline-working licenses that check without a request
Analytics tracking from install to paid user
Hosted checkout and account pages in eight languages
Test mode with Stripe test cards, one-click switch to Live
Webhooks and REST API for custom integrations
Import existing customers from CSV or another Stripe account
Full data export to self-host on your own server
Works with Manifest V3, WXT, Plasmo and CRXJS frameworks
Integration with Claude and other coding agents via MCP server
Unified payments API for creating, verifying and refunding payments across multiple providers
Idempotency to prevent duplicate charges on retried requests
Signed webhooks with verified provider payloads and automatic retries
Hosted checkout with browser checkout script
Event inspector to view provider payload and normalized event side by side
Full delivery log tracking every webhook attempt and response
Webhook replay functionality to resend events after fixing handlers
Scoped API keys bound to projects and environments with explicit permissions
Encrypted provider credentials with vault interface and audit trail
What makes it different
Payments go directly to your own Stripe account, never held by Toolaby
No server, backend code or webhook handler needed to accept payments
Free Hobby plan with only 0.5% per-sale fee, no monthly cost unless you sell nothing
Complete data portability: export everything and switch platforms any time
Never holds customer money or becomes merchant of record, keeping provider relationships and settlements unchanged
Write payment integration once instead of separately for each provider
Shows raw provider payloads alongside normalized events for complete transparency
All dashboard figures calculated from team's own payment data without estimates
Incremental adoption without requiring upfront migration or money movement