Scans, enrichment, outreach drafts and account discovery spend credits. This page explains where credits come from, the two limits on them, and which are spent first. Owners can see all of it in Settings > Billing. Everyone else sees what an action costs where they use it, such as when they start a scan. How many credits are left, the seat price and credit usage need the Credits: View permission, which Admin, Full access, Team manager and Audit have. Standard and Read only do not.
Each charge is recorded against the person who ran it, and against the kind of work (a scan, an enrichment, a draft, and so on). A scheduled sweep has no person. Owners, admins and auditors can read the whole workspace. A manager sees their own teams. Standard members do not see credit usage. Another workspace's usage is never included. With Credits: View, open Credits in the sidebar to see the balance, this period's spend, the run rate at the current scan schedules, and every charge broken down by action type, member, account and scan run. Filter by period and by scheduled versus manual spend. Each account or run row opens that record. Members who can view billing also see what is left against the plan allowance and the cap; for everyone else the page says the plan allowance is not available. Bookmarks to the old Reports > Credits address still open this page. Members who can view credits also see the remaining balance as a chip in the top-right of the app bar; open it to go to the Credits page. When the balance drops below the cost of one scheduled scan, the chip turns amber.
An owner can also set a monthly allocation for a person or a team, in Settings > Billing. Until the first allocation exists, everyone draws from the workspace balance. After that, a member needs an allocation, their own or one through a team, to spend credits: with none, the work is refused and the message says an owner can set it in Billing. Owners are never held back by this. An allocation is a hard limit for the calendar month: the work is refused when it is used up, even if the workspace still has credits, and the message names whose allocation ran out. A role also needs permission to spend credits at all. Owners set that on the role.
Billing draws the credits you have left as a ring, against your allowance, or against the cap when one applies. A mark on the ring is how much of the period is left. A fill past the mark means you are ahead of that pace. The ring stays indigo unless spending so far would use up the balance before the period renews, in which case it turns amber. If usage cannot be loaded, or nothing has been spent, it does not turn amber. A complimentary workspace is a full ring and never amber.
Seats on the same page read as the people who hold one, including a pending invite that can still be accepted, out of the seats the plan includes plus any extra seats. An expired invite does not hold a seat. A frozen member does not either.
Where credits come from
- Plan credits arrive with each monthly renewal. The amount depends on your plan.
- Top-up credits are the packs you buy when you need more.
The cap on plan credits
Plan credits stop accruing at 1.5 times your monthly allowance; see Billing for your figure.
When a renewal would take you past the cap, only the credits that fit are added. Billing shows your plan credits and the cap together, and warns you (amber) once you are close to it and (red) when you are at it, so a renewal that adds less than usual is never a surprise. The cap applies to plan credits only. A top-up never counts towards it.
Auto top-up
A workspace owner can turn on auto top-up in Settings > Billing. They choose one existing pack (small, medium or large) and a monthly spend cap in the workspace's billing currency. It is off until they do, and a cap of zero turns it off again.
When the balance reaches 100 credits or fewer, Aptiro charges that pack to the card already saved for the workspace, as long as this calendar month's successful auto top-ups plus the pack still fit under the cap. The month resets at 00:00 UTC on the 1st. A charge that is still going through, or one that failed, does not count towards the cap.
Each auto top-up is a Stripe invoice with tax added, the same as a top-up you buy yourself, so you get a receipt for it. The cap counts what your card was actually charged, VAT or sales tax included. If the pack plus tax would not fit under what is left of the cap, nothing is charged.
If the card is declined, or the bank asks for the cardholder to approve it, nothing is charged and no credits are added. Aptiro switches auto top-up off and emails the owners. Update the saved card in Billing, then switch auto top-up on again. Until you do, Aptiro does not try the card again.
If the cap is already full, Aptiro does not charge the card. Owners are emailed once that month, and Billing shows the same notice until the cap is saved again or the month changes. Work that needs more credits stops. An owner sees that the cap was reached and can raise it in Billing. Everyone else is told to ask a member with billing access. A workspace on the Scale plan also gets an audit log row for the blocked top-up and for each automatic charge. If there is no saved card, nothing is charged, and the usual low-credit email still goes out.
Top-ups expire after three months
Each pack expires three months after the day you bought it, and each pack has its own date. Billing lists your packs with their expiry dates and flags any that lapse within 30 days. Credits left in a pack when it expires are removed.
Which credits are spent first
- Top-up credits, the earliest purchase first.
- Plan credits, last.
So the credits closest to expiring are used before the ones that never expire.
If an action fails and is refunded
Credits are refunded to the pack or plan credits they were taken from. If that pack has expired in the meantime, the refund goes to your plan credits instead, so you are not left out of pocket.
A refund in the same calendar month gives that amount back against the person or team allocation, as well as to the workspace balance. A refund booked in a later month still returns the credits to the workspace, but it does not free room in the new month: the allocation counts the month the charge was made, and it resets at the start of the next month.
If Aptiro support changes your credits
Sometimes our support team grants credits, for example as goodwill after an outage, or removes some to correct a mistake. Each change shows up in two places, always under the name "Aptiro support" and never under a person's name:
- Billing lists the most recent changes under your credit balance, with the date, whether credits were granted or removed, how many, and the reason.
- The audit log (Scale plan) has a matching entry. Choose "Aptiro support" in the Through filter to see only these.
Turning complimentary credits on or off for your organisation also appears in the audit log. Every such change has an entry, because the entry is written in the same step that changes the setting. Changes made before this was introduced are not listed.
When the change takes effect
The cap and expiry start on a date we announce in advance. Until then nothing is capped or expired. Billing shows the date, how many credits would be removed, and the rule.
On the date, a balance above the cap is reduced to it, and we keep a record of exactly what was removed. Credits you hold on that date don't expire. Everything you hold then counts as plan credits, including any top-up credits bought before it. Only top-ups bought after the date expire after three months.