resolved
Stripe
stripe.com/
landed in 38msBookSlash for Stripe · Engineering
b/stripe.
b/customers. b/webhooks.
Stripe URLs are object IDs and account prefixes — impossible to memorise. BookSlash gives the customer view, webhook config, billing dashboard, and Sigma queries each a flat name finance, ops, and engineering types.
stripe
other shortcuts you might save
b/stripeb/customersb/webhooksb/sigma
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Stripe, with notes on why each one survives the URL changes that break personal bookmarks.
- b/stripe
Stripe Dashboard home.
Finance and engineering both reach it daily.
https://dashboard.stripe.com - b/customers
Customers list view.
Support reaches it for refund inquiries; finance for revenue analysis.
https://dashboard.stripe.com/customers - b/webhooks
Webhook configuration.
Engineers reach it during integration debugging.
https://dashboard.stripe.com/webhooks - b/sigma
Stripe Sigma SQL queries.
Finance and revenue ops reach it for custom revenue analysis.
https://dashboard.stripe.com/sigma - b/billing
Billing / Subscriptions dashboard.
Revenue teams reach it for MRR analysis; engineers for churn debugging.
https://dashboard.stripe.com/billing/overview - b/stripe-test
Test mode dashboard for development.
Engineers switch between live and test mode; the slug skips the toggle.
https://dashboard.stripe.com/test - b/disputes
Disputes / chargebacks queue.
Support and finance teams reach it weekly.
https://dashboard.stripe.com/disputes
Common workflows
Three patterns that pay back in week one.
01
Customer support refund flow
Support reaches b/customers, finds the customer, processes the refund. The slug ends the recurring "where is the customers tab?" friction.
02
Webhook integration debugging
When webhooks misfire, engineers reach b/webhooks to inspect deliveries and retry counts. Pairs with b/stripe-test for test-mode debugging.
03
Monthly revenue review
Finance reaches b/billing + b/sigma at month-end for revenue reporting. The slugs carry through Stripe Dashboard updates.
With and without
Same Stripe. Different team experience.
Without shortcuts
Each team member has private Stripe bookmarks. Refund support takes 30 seconds longer because of navigation friction. Finance pings engineering for the Sigma URL.
With BookSlash
b/stripe, b/customers, b/webhooks, b/sigma, b/billing, b/disputes, b/stripe-test. Seven slugs cover Stripe for finance, support, and engineering.
Related integrations
Pair Stripe with one of these.
Frequently asked
BookSlash + Stripe
No. Slugs are URL → URL redirects. Stripe handles all financial data on its infrastructure; BookSlash routes the navigation only.
The slug points at the URL; Stripe’s permissions still apply at the destination. Support agents see what their Stripe role allows.
Yes — namespace per customer: b/customer-acme. The slug carries the team to the same Stripe customer view.
It points at the test-mode dashboard URL. Engineers reach test mode in one keystroke instead of clicking the live/test toggle.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial