Auto-refill tops up your balance automatically when it runs low, so a big event day never stops mid-batch. This article shows you how to turn it on, what the limits are, and what happens if you leave it off.
How auto-refill works
You set two numbers: a trigger ("when my balance drops below $X") and a refill amount ("charge $Y to my saved card"). Whenever a render would take your balance below the trigger, Templified charges your saved card for the refill amount and keeps going — no interruption, no manual top-up in the middle of a shoot.
Turn on auto-refill
Auto-refill requires a saved card — if you haven't added one yet, do that first (see the related article below). Then:
- Go to Settings → Billing (organization owner only).
- Find the Auto-refill card and switch it on.
- Set the Trigger (USD) — refill when your balance drops below this amount. Allowed range: $1 to $500.
- Set the Refill amount (USD) — what's charged to your saved card per refill. Allowed range: $5 to $2000.
- Click Save auto-refill.
The authorization step
Before auto-refill activates, an Authorize automatic refills dialog summarizes the terms: your trigger, your refill amount, that charges happen automatically on your saved card with no further confirmation, and that you can disable it any time. Click I authorize to confirm.
This step exists because card networks require your explicit consent before a merchant can charge a stored card without you present. Templified records when you gave consent, and the Billing page shows that timestamp. Turning auto-refill off stops all automatic charges immediately.
Built-in safeguards
- Maximum 5 auto-refills per 24 hours — a runaway batch can't drain your card.
- A receipt is emailed for every refill, so charges never happen silently.
- Disable any time from the Billing page — no further charges will be made.
What happens with auto-refill off
If your balance runs out and auto-refill is off, new renders are blocked until you add funds. In the app you'll be prompted to top up; if you use the API or Zapier, requests fail with an HTTP 402 (payment required) error. Nothing is lost — rendering resumes as soon as funds land.
If a refill charge fails
If your card declines (expired, canceled, over limit), your account becomes suspended and rendering pauses. The Billing page shows a red banner with a Top up button — a successful top-up restores everything. If the card itself is the problem, use Manage Payment Method to update it first. If your saved card was removed or is no longer on file, Billing now repairs itself and lets you update the card through that same button — you won't be forced to make a top-up charge just to fix the card.
Comments
0 comments
Article is closed for comments.