Three distinct layers of evidence
XML structure
Reviews the structural rules applied to a document and preserves their results. Correct structure alone does not prove fiscal authenticity.
Issuer signature
Checks the signature, original string and attached certificate key when compatible material is available. Certificate trust and revocation are shown separately as unverified.
SAT status query
When enabled, preserves the query response and its date. An unavailable provider or unverifiable response is not converted into a valid result.
Current service configuration
An enabled capability indicates available configuration, not granted account access or a successful result for every query. A ViciousByte evidence signature attests to application evidence integrity; it is not a SAT stamp.
XML structural checks
Checking…Issuer signature against the attached certificate
Checking…Batch jobs
Checking…JSON evidence export
Checking…ViciousByte evidence signature
Checking…SAT status query
Checking…UUID watchlists
Checking…Signed webhooks
Checking…Certificate trust and revocation
Checking…SAT stamp signature
Checking…
Privacy and retention
Projects belong to one account. Original XML is kept in private storage together with JSON evidence; reads and downloads require authorization. No invoice upload is needed to request access.
Each batch shows its effective expiry date in the dashboard. Expiry or a deletion request blocks access and queues XML, evidence and payload purging; physical deletion is asynchronous. A separate minimal idempotency and quota receipt retains no XML, RFC or text.
Current validation plans may apply. The dashboard checks access and scope for each project. Pilots require administrative review; a pending request grants no permission and starts no charge.
Request pilot access
Register a CFDI Guard request for your account. This does not create a subscription, activate permissions or execute a payment.