Stripe logo
Slack logo

Workflow template

Send Slack alerts for new Stripe refunds

Notify Slack when a Stripe refund is created, including partial refunds. Send the refund ID, individual amount in minor units, currency, event ID and live mode without implying completed settlement.

How it works

From a Stripe refund creation to a Slack operations notice

1 Trigger · 1 Action
Stripe1 · Trigger

Refund Created

Receive refund.created after activation. Each partial refund is a separate event with its own amount; creation does not confirm funds have reached the customer.

Slack2 · Action

Notify the team about a new refund

Post refund ID, individual amount, currency, event ID and livemode as the FastHook bot, with a reminder to review Stripe. Disable mrkdwn and link/media previews; status and timestamp are not included.

The result

An individual refund reference in the operations channel

Example Slack Stripe refund notice

Stripe refund created Refund ID: re_example_slack_refund This refund amount (minor units): 1000 Currency: eur Event ID: evt_example_slack_refund Live mode: false Review the current refund status in Stripe; creation does not confirm arrival in the customer account.

Fictional EUR sandbox refund. The notice contains no status field, event timestamp or Stripe URL. It reports the amount of this refund, not a cumulative refunded total.

Before activation

Set up your workflow

  1. Connect Stripe Refund Created

    Choose Stripe sandbox for the first test and retain refund.created as the source. Existing refunds and later status updates are outside this workflow.

  2. Choose the Slack payment-operations channel

    Connect Slack and Browse to a channel where FastHook can post. Review access to refund IDs and amounts, and retain plain text with link and media previews disabled.

  3. Verify a fictional creation event

    Activate, wait for Connected and inspect a new sandbox refund notice. Compare the original amount, currency, IDs and Live mode=false. Use Stripe itself to review current progress before drawing a delivery conclusion.

Details and limitations
  • One partial refund is one notice. Two separate partial refunds produce two notices with their own amounts. The template does not report the payment’s accumulated refunded amount or merge events by payment.

  • The amount is unconverted minor units. 1000 EUR or USD means 10.00, while 1000 JPY means 1000. The action preserves the source amount and currency without conversion. No status or timestamp is mapped into this message.

  • Creation is not settlement confirmation. The recipe does not issue refunds or observe subsequent status updates. Contacts, card data, instructions email, metadata and destination details are excluded. Old refunds are not imported; manual reruns can send another notice.

Questions about this template

Does this show the total refunded across a payment?

No. It shows the individual refund amount from each refund.created event. Two partial refunds produce separate notices rather than one accumulated total.

Where is the current refund status?

Check Stripe. The message does not map status or timestamp, and later updates are not synchronized. Creation alone does not confirm receipt by the customer.

How is the amount converted for Slack?

It is not converted. Source minor units are preserved: 1000 is 10.00 for EUR or USD, and 1000 for JPY. Read the recorded currency with the value.

Does the workflow issue a refund or notify the customer?

No. It sends an internal Slack creation notice only. Historical refunds and later outcomes are not imported; manual reruns can duplicate messages.

Explore connected apps