How to receive Stripe webhooks on localhost

By Karolis Rusenas · Dec 26, 2017

stripe webhooks

In recent years Stripe has become a major payments provider. It is loved by managers and developers for a reason. Stripe has easy to use APIs, SDKs in multiple languages and outstanding documentation.
Like other payment platforms, Stripe utilizes webhooks to inform about customer, subscription, card and many other changes in the state.

While this strategy works great in production, during development it can be tricky to receive these webhooks, especially when webhooks are critical for building subscription (or recurring payment) based systems where your backend system needs to track subscription status.

In this article, we will:

  • Build a simple application to handle several Stripe webhooks that indicate subscription change.
  • We will use relay forward command to receive webhooks on localhost.
  • We will use Stripe’s webhooks testings dashboard to simulate subscription change events.


This post/guide assumes that you have:

Building application

There are many libraries available for Stripe. You can find a maintained list on Stripe’s documentation page here:

Our sample app is written in Go. Application source is pretty straightforward. There is only one handler to receive webhooks (documentation on how to use webhooks is here:, validate signature and print to the terminal customer ID and current subscription status:

package main

import (

    stripe ""

// port - default port to start application on
const port = ":8090"

// webhook event types
const (
    stripeEventTypeSubscriptionUpdated string = "customer.subscription.updated"
    // canceled subscription
    stripeEventTypeSubscriptionDeleted string = "customer.subscription.deleted"
    // card deletion event
    stripeEventTypeSourceDeleted string = "customer.source.deleted"

func validateSignature(payload []byte, header, secret string) (stripe.Event, error) {
    return webhook.ConstructEvent(payload, header, secret)

func main() {
    secret := os.Getenv("SIGNING_SECRET")
    if secret == "" {
        fmt.Println("SIGNING_SECRET env variable is required")

    // preparing HTTP server
    srv := &http.Server{Addr: port, Handler: http.DefaultServeMux}

    // incoming stripe webhook handler
    http.HandleFunc("/stripe", func(resp http.ResponseWriter, req *http.Request) {
        body, err := ioutil.ReadAll(req.Body)
        if err != nil {

        // validating signature
        event, err := validateSignature(body, req.Header.Get("Stripe-Signature"), secret)
        if err != nil {
            fmt.Printf("Failed to validate signature: %s", err)

        switch event.Type {
        case stripeEventTypeSubscriptionUpdated, stripeEventTypeSubscriptionDeleted:
            // subscription status change
            customerID, ok := event.Data.Obj["customer"].(string)
            if !ok {
                fmt.Println("customer key missing from event.Data.Obj")

            subStatus, ok := event.Data.Obj["status"].(string)
            if !ok {
                fmt.Println("status key missing from event.Data.Obj")

            fmt.Printf("customer %s subscription updated, current status: %s \n", customerID, subStatus)
        case stripeEventTypeSourceDeleted:
            customerID, ok := event.Data.Obj["customer"].(string)
            if !ok {
                fmt.Println("customer key missing from event.Data.Obj")
            fmt.Printf("card deleted for customer %s \n", customerID)

    fmt.Printf("Receiving Stripe webhooks on http://localhost%s/stripe \n", port)
    // starting server
    err := srv.ListenAndServe()

    if err != http.ErrServerClosed {
        log.Fatalf("listen: %s\n", err)

Source code can be found here:

To install and run it, in your Go working environment you can just do:

go get
cd $GOPATH/src/
go install

Our application will expect Stripe webhooks on http://localhost:8090/stripe.

Receiving webhooks on localhost

To start receiving webhooks on localhost, we will use relay CLI:

relay forward --bucket stripe http://localhost:8090/stripe

flag –bucket stripe is optional but helps a lot when we restart relay CLI as it reuses the same public endpoint.

Output of the command should display your{id here} public endpoint:

relay forward --bucket stripe http://localhost:8090/stripe
Forwarding: -> http://localhost:8090/stripe

Testing webhooks via Stripe

getting webhooks on localhost

Let’s go to our Stripe dashboard, API webhooks section ( and:

  1. Add an endpoint with your unique Webhook Relay URL.

  2. Get a signing secret, set it for our stripe-webhook-demo application, and launch it:

    $ export SIGNING_SECRET=whsec_********************************
    $ stripe-webhook-demo
    Receiving Stripe webhooks on http://localhost:8090/stripe
  3. Click on “Send test webhook”, select customer.subscription.updated and send it.

  4. View the stripe-webhook-demo output. It should display a customer ID and subscription status:

    $ stripe-webhook-demo
    Receiving Stripe webhooks on http://localhost:8090/stripe
    customer cus_00000000000000 subscription updated, current status: active

Wrapping up

In this post we created a sample application that can receive webhooks from Stripe. We used relay forward command to receive webhooks on localhost and checked out Stripe’s webhook testing dashboard to speed up development.