How ChargeBell secures your Stripe and Slack accounts

ChargeBell reads Stripe payment events and posts alerts to Slack. This page lists every permission it asks for and what it can't do with them.

Start freeNo card needed. Setup takes about 2 minutes.
Permission boundary
Stripeevents
Slackalerts
  • Payment events flow through
  • Money movement never does

ChargeBell reads events. You keep control of the account.

ChargeBell connects through Stripe's OAuth to receive the events you choose and add context to them. It has no control over your payments.

What ChargeBell can do

  • Receive payment and subscription events
  • Read the fields needed to format an alert
  • Calculate amounts after fees and MRR changes

What ChargeBell can never do

  • Move funds or start payouts
  • Create charges or subscriptions
  • Issue refunds or change customer data

Slack access to post alerts, not to read messages

ChargeBell asks Slack for permission to list channels, join public channels, post messages, and run the /chargebell command. It doesn't ask to read message history.

chat:write
Post ChargeBell alerts as the installed bot.
chat:write.public
Post to a public channel you pick, even before the bot is invited.
channels:join
Join a public channel you pick so alerts can post there.
channels:read
List public channels so an admin can pick where alerts go.
groups:read
List private channels only when the bot already belongs to them.
commands
Install the ChargeBell slash command and reply to it.

You approve access and you can remove it

  1. 1

    You approve OAuth

    Stripe or Slack shows the access ChargeBell requests before an organization owner or admin approves it.

  2. 2

    ChargeBell delivers

    ChargeBell stores the credentials for the organization and uses them only to receive events and deliver the alerts you set up.

  3. 3

    You can disconnect

    Remove either integration from ChargeBell. It removes or revokes the active credentials and connection records.

Each workspace is kept separate

ChargeBell separates tenants by organization. Connections, alert rules, delivery history, settings, and billing all belong to one organization.

Role-gated changes
Only owners and admins can change integrations, rules, team membership, billing, and workspace settings.
Isolated records
Every record is keyed to one organization. A user in several workspaces doesn't share data between them.
Protected transport
OAuth and app traffic use HTTPS. Credentials never reach the browser.
Auditable outcomes
Delivery history shows each attempted alert and whether each destination received it.

Need the legal detail?

The Privacy Policy covers what ChargeBell collects, how long it keeps data, which providers it uses, what happens on disconnect, and your rights.

Read the Privacy Policy

Security questions

Can ChargeBell move money or issue refunds?

No. ChargeBell uses its Stripe connection to read the payment events it needs for alerts. It can't create charges, move funds, issue refunds, or change your Stripe account.

Can ChargeBell read our Slack messages?

No. ChargeBell doesn't request Slack's message history scopes. It lists channels, joins the public channels you pick, posts alert messages, and runs the ChargeBell slash command.

What happens when we disconnect an integration?

ChargeBell removes the active credentials and the connection records that integration needs to keep working. Some non-secret records and delivery history may remain, as the Privacy Policy describes.

Who can change integrations and security settings?

Only owners and admins. Each organization is a separate tenant, and changes to connections, alert rules, team, billing, or workspace settings require the owner or admin role.

Connect Stripe and Slack with read-only access

Approve both integrations, choose the channels, and send a test alert. An owner or admin can disconnect either one from settings.

Create your workspace