Integrate with Brazil's SEFAZ web services to issue and manage NF-e (Nota Fiscal Eletrônica)
domain: nfe.fazenda.gov.br · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a valid ICP-Brasil digital certificate (e-CNPJ/e-CPF) required to authenticate and digitally sign NF-e XML documents
Determine the correct regional SEFAZ virtual environment (e.g., SVAN, SVRS, or the issuing state's own SEFAZ) to which the business's NF-e submissions route
Build and digitally sign the NF-e XML per the current national layout manual and submit it to the appropriate SEFAZ web service for authorization
Handle the SEFAZ authorization response (Protocolo de Autorização); for accepted documents, generate the DANFE for accompanying the goods, and for rejections, correct and resubmit
Implement contingency handling (e.g., SVC failover) for periods when the primary SEFAZ web service is unavailable, per the issuing state's contingency rules
Known gotchas
NF-e technical layouts and business rules can differ by Brazilian state, so an integration validated against one state's SEFAZ may fail against another's without state-specific configuration
Digital certificates typically expire annually and expiry silently breaks signing — expired-certificate failures are one of the most common production incidents
Contingency/offline issuance modes exist because SEFAZ web services have real, documented downtime; a production integration without a contingency path risks blocking sales during an outage
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?