Skip to main content
Several fields in the Facturama API travel Base64-encoded: the auth token, the CSD files, the XML being stamped, and the files you download. Use the tabs below to build and decode those strings.

​
What each tab does

Everything runs in your browser. Files, passwords, and text are processed on your device using native browser APIs. Facturama receives no copy and stores nothing you convert.
Base64 encrypts nothing, it only changes the format. Your PrivateKey string and your password are the credentials that seal your CFDI: anyone who obtains them can issue invoices in your name. Do not paste them into support tickets, chats, or repositories, and do not use this tool on a shared computer.

​
Known limits

The tool copies the password into the request body, but it does not check that the password is the right one for the .key. Verifying that requires decrypting the private key, and SAT keys ship as encrypted PKCS#8, often with 3DES, which the browser’s cryptography API does not support.If the API rejects your request when loading credentials, a wrong password is one possible cause and this tool cannot rule it out.
When you upload the .cer, its keyUsage extension is read to warn you if it is actually a FIEL rather than a CSD, and the RFC is extracted to prefill the Rfc field of the request body. To inspect the certificate in depth, use the CSD inspector.
The type is inferred from the file’s first bytes: PDF, ZIP, PNG, JPEG, XML, HTML, DER certificate, or plain text. It is a heuristic; if the content matches no known signature it downloads as plain text. You can type whatever name and extension you want.

​
Next steps

Authentication

How to use the header you just built in your requests.

CSD inspector

Inspect the certificate in depth before loading it into the API.