Cap the ATIGA certificate. Keep the provider key.
An ATIGA origin extract, preference-coding, or certificate-of-origin packet job should not inherit a standing provider secret. Issue a Till key with a required request ceiling so the batch can finish and then cannot keep going.
Isolate the ATIGA-certificate traffic, not the provider account.
- 01Issue a disposable Till key
Set the required request ceiling from expected fields and retries, then add optional token, spend, expiry, and IP bounds when the worker needs a tighter envelope.
- 02The provider credential stays behind Till
The job uses a Till key, not an unconstrained provider secret in the worker process. Revoke or let expiry stop that key when the batch is retired.
- 03This is not a customs authority
Till does not issue ATIGA certificates, certify origin, or replace a customs authority. It is a hosted control layer with request, token, spend, expiry, and IP controls.
Connect provider accounts once. Give each ATIGA-certificate job a disposable key with a required request ceiling. Till is not a certificate issuer or a replacement for provider billing or IAM.
Size the envelope from the packet.
- 01Count the expected records
Start with the number of origin extracts, preference-code decisions, or certificate packets the job must process.
- 02Add deliberate retry headroom
Make the required request ceiling large enough for the worker’s documented retries, without turning it into a standing monthly allowance.
- 03Retire the key with the batch
Use expiry or revocation when the packet is complete so a finished ATIGA-certificate job cannot keep spending the provider account.
These are plan limits, not usage claims.
Pro
Scale
Public anonymous signup is closed. New accounts are approved and provisioned manually. Compare the full ledger on pricing.
Finish the queue. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually.