When you add a new site, you can configure it and draft job posts immediately — but actual publishing requires the first successful payment for that site to clear, which typically takes seconds via the Stripe webhook.
Why this happens
- New sites are payment-gated to prevent abuse.
- Jobs you create show as pending_payment until the first charge confirms.
- Once the charge succeeds, jobs auto-publish without further action.
- Trial periods count as "payment satisfied" — jobs publish normally during trial.
Three scenarios where this affects you
- First-time site creation: new site, first job, first charge all happen close together.
- Job renewal: extending a job past its natural expiry consumes a job-post slot from your capacity.
- Job reactivation: bringing back a job after 21 days of inactivity also consumes a slot.
What to do if your job is stuck in pending_payment
- Wait 30 seconds — most webhooks arrive within seconds and the job auto-publishes.
- Check your billing dashboard for any "payment pending" or "payment failed" notice.
- If you see a failed-payment banner, update your card and retry.
- If the charge succeeded but the job is still stuck, contact support — there may be a webhook delay.
If you're out of job-post capacity
- Renewal or reactivation is blocked with an explicit message.
- You'll be prompted to purchase an extra job post inline ($50/month, prorated).
- Once purchased and paid, the renewal/reactivation completes immediately.
| Good to know This applies per site, not per organization. If you have multiple sites, each one needs its own first successful payment before its first job can publish. Sites added mid-cycle are charged prorated immediately — usually a small amount that clears in seconds. |
Comments
0 comments
Please sign in to leave a comment.