Billing and Usage
Understand what counts as an accepted event, when plan changes take effect, and how Sandbox fallback works.
Use this guide to read billing usage and plan limits correctly.
Plans and the Team trial
Every new workspace starts with a 14-day Team trial. No card is required. The trial uses the same limits and features as Team, including team organizations and advanced retry policies. When the trial ends, the workspace remains active on Sandbox unless you subscribe.
| Display plan | API tier | Price | Accepted events/month | Active endpoints | Enabled outputs/endpoint | Retry cap | Members | Max payload | Requests/minute |
|---|---|---|---|---|---|---|---|---|---|
| Sandbox | FREE | $0 | 250 | 1 | 2 | 1 | 1 | 256 KB | 30 |
| Team trial | TRIAL | 14 days | 10,000 | 5 | 5 | 5 | 5 | 512 KB | 600 |
| Solo | BASIC | $9/month or $90/year | 1,000 | 1 | 3 | 3 | 1 | 256 KB | 60 |
| Team | PRO | $49/month or $490/year | 10,000 | 5 | 5 | 5 | 5 | 512 KB | 600 |
| Scale | ULTIMATE | $199/month or $1,990/year | 100,000 | 50 | 10 | 5 | Unlimited | 1 MB | 3,000 |
All plans support every destination type and failover. Sandbox and Solo use the standard retry schedule. Team trial, Team, Scale, and Unlimited can choose aggressive or conservative schedules and custom retry status codes.
What counts toward usage
- One accepted webhook or email event consumes exactly one event from the organization-wide monthly allowance.
- Destination fan-out, failover, delivery attempts, and retries do not consume additional event quota.
- Requests rejected before acceptance, such as authentication or validation failures, do not consume quota.
- Quotas reset on the first day of each calendar month (UTC).
- Alerts are sent once at 80% and once at 100% to the billing contact when quota alerts are enabled.
- Accepted-event quotas are hard caps. There is no metered overage billing.
Relay responses expose the current allowance in:
X-Monthly-Accepted-Event-LimitX-Monthly-Accepted-Events-RemainingX-Monthly-Reset-Date
HTTP requests-per-minute terminology remains separate from monthly accepted-event billing.
Output limits
The output cap applies per endpoint and counts only enabled, non-failover outputs. Disabled output configurations and failover rows do not consume the cap. If a downgrade lowers the cap, PayloadRelay keeps the oldest allowed outputs enabled and preserves later output configurations in a disabled state.
Forged over-limit updates return HTTP 402 with OUTPUT_LIMIT_REACHED. Advanced retry settings on an ineligible plan return 402 with ADVANCED_RETRY_POLICY_REQUIRED.
Subscribe after the trial
Selecting a paid plan first checks the workspace against that plan's limits. If Solo would disable trial endpoints or outputs, reduce retry settings, deactivate members, or leave current accepted-event usage above its allowance, Billing lists the exact impact and requires acknowledgement before opening Stripe Checkout. No resources change unless payment succeeds.
Team and Scale normally continue directly to Checkout because their limits are at least as permissive as the Team trial. A Checkout preview expires after 15 minutes, and PayloadRelay asks for a fresh review if the workspace changes materially before Checkout starts.
Change a paid plan
Selecting a plan creates a 15-minute preview. Review the amount due now, proration credit, estimated tax, recurring USD price, renewal date, and any accepted-event, endpoint, output, or member impact before confirming.
- Upgrades and monthly-to-annual changes apply after Stripe confirms payment.
- Downgrades and annual-to-monthly changes apply at the current period end.
- Scheduled downgrade previews identify endpoints and outputs that will be disabled, outputs whose retry settings will be reduced, and members that will be deactivated.
- At enforcement time, PayloadRelay preserves the oldest allowed endpoints and outputs and preserves the organization owner plus the oldest allowed members.
- Plan changes are disabled while cancellation is scheduled. Resume renewal before creating another preview.
Payment recovery
Checkout and immediate upgrades may show Processing or Payment required. New entitlements do not apply until Stripe confirms settlement. An authoritative recurring-payment failure starts the existing recovery period; access remains available during that grace window. Past-due subscriptions continue under the recovery/read-only rules until Stripe reports a terminal state.
Invoice-finalization errors do not remove an otherwise active subscription. Duplicate-subscription and unknown-price states pause billing mutations and require support reconciliation.
Cancel, resume, and view invoices
Cancellation stops renewal at the end of the paid period. Paid features remain available through that date, then the workspace automatically moves to active Sandbox with a fresh 250-event allowance. PayloadRelay preserves the Stripe customer and invoice history while clearing the ended subscription and price.
Cancellation fallback also:
- Keeps the oldest allowed endpoints and members active.
- Disables excess outputs without deleting their configuration.
- Clamps retries and advanced retry settings to Sandbox limits.
Use Resume subscription before the paid period ends to keep renewal active. The Stripe portal remains available for payment methods, tax details, and invoice history.
Activity retention and privacy
PayloadRelay keeps a 30-day metadata-only activity trail and delivery outcomes. Payload bodies are excluded from that history and are processed in delivery and retry queues while events are being forwarded. Failed queue messages may remain in an operational dead-letter queue until remediated or purged.
Common issues
- Usage looks stale: select Refresh usage and recheck after a short delay.
- Remaining events look wrong: verify the current calendar-month window and accepted traffic.
- An output cannot be enabled: disable another enabled primary output or upgrade to a plan with a higher output cap.
- An advanced retry setting is unavailable: Team trial, Team, Scale, or Unlimited is required.
- Payment is still processing: continue an open Checkout or wait for Stripe settlement; do not create a duplicate subscription.
- Need billing help: open Support with the organization, timeframe, and relevant Stripe invoice/customer references.