Two platform-Stripe operations anchored on the registration row: a one-time send-invoice for the brand fee, and a monthly subscription started at campaign verification. Customer resolution walks the account's stored Stripe customer, then the funnel signup's customer, then creates one.
Also called: brand fee · 10DLC monthly · who pays for registration · carrier fees
- 1Brand submission triggers a one-time invoice at the account's rate-card price for the low-volume tier.
- 2The invoice is send_invoice with a seven-day window, so no stored card is required.
- 3Campaign verification starts the monthly subscription.
- 4Both are keyed to the registration row so a retry cannot double-charge.
- 5A billing failure never blocks the carrier registration.
The module states the timing rule: the subscription is 'fired when the campaign VERIFIES and texting turns on (fees start when the carriers actually start charging us)'. Both are 'IDEMPOTENT (ids anchored on org_a2p_registrations) and BEST-EFFORT from the callers' perspective — a Stripe hiccup must never block a carrier registration.'
- Monthly fees could start before texting was actually live.
- A payment hiccup could have blocked a compliance filing.
- A retry could have double-charged a registration.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →