Data Credit overages
When your Data Credit balance hits zero, behavior depends on your overage setting — block (prevent further pulls), allow (charge for overages), or temporary (allow for a window). Auto-reload prevents the question entirely by topping up before zero.
In short: Pick an overage policy that fits your usage. Auto-reload is the smoothest — set a threshold and SALT tops you up before you run out.
What runs out
Data Credits cover paid lookups against external data providers (Estated, Fenris, MeasureOne, etc.). Each pull costs a configured number of credits per vendor.
Credits live at the agency level. When the balance reaches zero, the next pull triggers your overage policy.
Overage policies
You can configure how SALT handles a zero balance:
| Policy | Behavior |
|---|---|
| Always allow | Continue running pulls; charge for overages on the next invoice |
| Block | Stop running pulls; integrations that depend on data lookups don’t fire |
| Temporary allow | Continue running pulls for a configurable window, then block |
Pick the policy from your data credit settings.
Auto-reload
Auto-reload prevents overages by topping up your balance before it hits zero:
- Set a trigger threshold (e.g. when balance drops below 10% of pack size)
- Set a reload amount (which Data Credit pack to buy automatically)
- When the trigger fires, SALT charges your card and adds credits to your balance
This is the smoothest option — you never run out, integrations always work, charges are predictable.
Pack sizes and discounts
Data Credit packs have volume discounts:
| Pack size | Discount |
|---|---|
| 100 credits | None |
| 500 credits | 5% |
| 2,000 credits | 10% |
| 5,000 credits | 15% |
Buying larger packs is cheaper per credit. If your usage is predictable, larger packs save money.
Threshold notifications
You’ll get notifications as your balance approaches zero:
- 20% remaining
- 10% remaining
- 5% remaining
These help you intervene before a hard zero. If you have auto-reload, you may not see these because the auto-buy fires first.
What integrations are affected
Data Credit-consuming integrations:
- Estated — property data lookups
- Fenris — property and risk data
- MeasureOne — declaration page retrieval
- Fize — alternative dec page vendor
Non-consuming integrations (CRMs, raters, automation) are unaffected by Data Credit balance.
Common questions
What’s the per-pull cost? Per-vendor cost is configured in SALT. Check your data credit settings to see the cost per vendor (typical range is 0.8 to 2.0 credits per pull).
Can I see how many credits each integration is using? Yes — see Tracking Data Credit usage. Reports break down usage per vendor and date range.
My pulls stopped working but I have credits in my balance. Check whether a per-vendor monthly threshold has been hit. The integration may be paused by data thresholds even if your overall balance is fine.
Are gifted Data Credits subject to the same overage rules? Promotional credits behave like regular credits in your balance — they’re consumed first (typically). Once exhausted, regular credits and overage rules apply.