Conversation
SEFAZ drops only non-significant zeros. Removing every zero turned id 100 into 1, so the QR hash was for the wrong token.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The NFC-e QR builder removed every
0from the CSC id. SEFAZ only drops zeros that are not significant (the ones on the left). Id000100was sent as1, and the SHA-1 was taken over that wrong id, so the receipt QR does not match the token registered for that taxpayer.000001still becomes1.Test plan
tests/test_nfce_qrcode_csc.py: before this change the id came back as1. After it, the parameter is100and the hash matches SHA-1 of that parameter plus the CSC.000001still becomes1.Made with Cursor