Skip to main content

​
Overview

BeatPass processes payment events from Stripe via . There is currently no outbound webhook system for external developer integrations.
BeatPass does not send webhooks to external applications. This page provides an overview of how payment processing works on the platform.

​
Stripe Events Handled

The webhook controller processes the following Stripe events:

payment_intent.succeeded

A succeeded. Success Completes the purchase and activates the license.
Failed Records the payment failure. The buyer sees an error on their next visit.
Refund Processes the refund (supports both partial and full refunds).

​
How It Works

1

Payment Initiated

User initiates a track purchase through the BeatPass checkout flow.
2

Payment Processed

Stripe processes the payment securely.
3

BeatPass Updated

BeatPass automatically:
  • Updates purchase records
  • Generates license certificates for successful purchases
  • Marks tracks as sold for exclusive purchases
  • Sends notifications to producers

​
Webhook Security

All payment webhooks are cryptographically verified to ensure authenticity. Invalid or tampered requests are rejected automatically. All webhook processing is logged for audit purposes.

​
No Outbound Webhooks

BeatPass does not currently offer outbound webhooks for external integrations.
If you need real-time updates for your integration, contact contact@beatpass.ca to discuss your use case.

Commerce & Licensing API

Purchase flow, license certificates, and Stripe Connect endpoints.

Exclusive Licenses

How exclusive purchases and licensing work.

Stripe Connect

Producer payout setup guide.
Last modified on February 10, 2026