Skip to main content

​
Overview

BeatPass processes payment and payout events internally to keep purchases, licenses, and producer finance records up to date. There is currently no outbound webhook system for external developer integrations.
External apps should use the documented API to read purchase, license, and payout-history data. Do not send payment-provider webhook traffic to BeatPass or build against undocumented internal routes.

​
What Developers Can Rely On

No outbound webhooks

BeatPass does not currently send webhook callbacks to partner or developer applications.

Documented APIs only

Use the public developer docs for supported purchase, license, analytics, and payout-history reads.

Provider events stay internal

Card payment, Stripe Connect, and BEATPAY provider events are handled by BeatPass, not external integrations.

Use polling carefully

If your integration needs status updates, poll documented read endpoints conservatively and respect rate limits.

​
Purchase Confirmation Flow

1

Buyer starts checkout

A buyer starts a track purchase through the documented commerce flow.
2

Payment is confirmed

BeatPass receives the provider confirmation internally and updates the purchase record.
3

License becomes available

BeatPass activates the license, generates the certificate when applicable, and updates the buyer and producer views.
4

Integration reads status

Your integration reads purchase or license state through the documented API instead of waiting for an outbound webhook.

​
Payout and BEATPAY Events

Producer payout setup and payout-provider events are not public integration hooks. Producers manage payout setup in Finances, including BEATPAY bank payout setup when it is available to them. For external integrations:
  • Do not document, call, or probe BEATPAY setup routes
  • Do not attempt to create or manage producer bank details through the public API
  • Use documented read-only payout history or transaction endpoints only when your account is approved for them
  • Send producers to BEATPAY Bank Payouts or Producer Finances for setup guidance
Undocumented payout setup, provider, and administrative routes are off-limits. Unauthorized access attempts can result in token revocation and account action.

​
Security Expectations

BeatPass verifies provider-originated payment events internally before updating purchases, licenses, or payout records. External developers should focus on protecting their own integration:
  • Store Bearer tokens securely
  • Use HTTPS for all requests
  • Do not log payment secrets or user banking details
  • Respect API rate limits and retry guidance
  • Contact BeatPass before building any workflow that depends on near-real-time payment or payout state

Commerce & Licensing API

Purchase flow, license certificates, and safe finance references.

Rate Limits

Poll documented endpoints responsibly.

BEATPAY

Producer-facing bank payout setup guidance.
Last modified on June 19, 2026