NFe
Ready NF-e workflow
XML signing with `Id` reference, fiscal policy, and signed response ready for submission.
- Enveloped signature
- Sync/async support
- Per-request traceability
Fiscal XML Solution
Sign NFe, NFSe and CTe with one integration and per-document policies
4signer unifies fiscal XML flow for software houses, ERPs and issuing platforms. Choose the certificate method per request and keep full traceability in production.
NFe
Modelo 55
NFSe
Multiple providers
CTe
Modelo 57
Connector JS | Fiscal XML signing
const connector = createSignerConnector({
apiBaseUrl: 'https://4signer.com/api',
bearerToken: 'TOKEN_DA_ACCOUNT'
})
const result = await connector.sign({
documentId: 'nfe-1001',
documentType: 'xml',
certificateMode: 'local',
documentContentBase64: nfeXmlBase64,
xmlProfile: 'fiscal',
xmlPolicy: 'nfe-4.00',
xmlPolicyParameters: {
signed_element_local_name: 'infNFe',
id_attribute: 'Id'
}
})
console.log(result.status)const connector = createSignerConnector({
apiBaseUrl: 'https://4signer.com/api',
bearerToken: 'TOKEN_DA_ACCOUNT'
})
const result = await connector.sign({
documentId: 'nfse-1001',
documentType: 'xml',
certificateMode: 'cloud',
documentContentBase64: nfseXmlBase64,
xmlProfile: 'fiscal',
xmlPolicy: 'nfse-abrasf-2.04',
xmlPolicyParameters: {
signed_element_local_name: 'InfDeclaracaoPrestacaoServico', // ajuste conforme provedor
id_attribute: 'Id'
}
})
console.log(result.status)const connector = createSignerConnector({
apiBaseUrl: 'https://4signer.com/api',
bearerToken: 'TOKEN_DA_ACCOUNT'
})
const result = await connector.sign({
documentId: 'cte-1001',
documentType: 'xml',
certificateMode: 'local',
documentContentBase64: cteXmlBase64,
xmlProfile: 'fiscal',
xmlPolicy: 'cte-4.00',
xmlPolicyParameters: {
signed_element_local_name: 'infCte',
id_attribute: 'Id'
}
})
console.log(result.status)
The signed tag is defined in `xmlPolicyParameters.signed_element_local_name`.
Fiscal products in the same integration pattern
NFSe
Standardization for NFS-e
Adapt policy by provider/city without changing your core integration architecture.
- Configurable policies
- Batching for high volume
- Compliance logs
CTe
Scalable CT-e operation
Same XML endpoint with transport-specific policy and end-to-end visibility.
- Synchronous and asynchronous flow
- Webhook for final status
- Production-ready
Production fiscal workflow
One workflow for your technical team and fiscal operations, regardless of document type.
1. Issuing system
Sends XML for signing
Sets `signature_profile=fiscal` and the policy.
→
2. Signing method
Local A3, A1, or cloud
`agent_local`, `local_pfx`, `stored_a1` ou `remote_provider`.
→
3. Processing
Fiscal engine applies policy
Signing and validation according to document policy.
→
4. Result
Signed and traceable XML
Response ready for fiscal submission, archiving and auditing.
Ready to evolve your fiscal XML operation?
Integrate once and scale NFe, NFSe, and CTe signing with technical predictability and operational governance.