Troubleshooting
“Test connection” fails
Section titled ““Test connection” fails”- Check the mode: test credentials only work in test mode and live credentials only in live mode.
- Facturama: the user and password of the portal (not an API key). Facturapi: the secret key (
sk_test_in test mode,sk_live_in live mode) in the password field. - Check for spaces before or after the values.
- The Log tab shows the PAC’s answer (masked). 401 means wrong credentials; 403 a plan without API access.
- Your server must be able to reach the PAC over HTTPS (outgoing port 443) and have a current CA bundle.
The document shows an error before anything was sent
Section titled “The document shows an error before anything was sent”The reason is shown in the order tab:
- “Complete the issuer data on the Connection page”: RFC, legal name, tax regime and expedition postal code are required.
- “Fiscal data of the customer incomplete”: RFC (SAT format), legal name, 5-digit postal code, tax regime and CFDI use are all required for an individual CFDI.
- “The CFDI does not pass the SAT schema”: the message names the attribute. Usually a tax regime, use or key outside the catalogue.
- “Add the currency MXN …”: the store has no MXN currency to calculate the exchange rate of a foreign currency order.
- “IVA exento / IEPS … not supported”: the chosen PAC driver cannot send that tax; use Facturama or change the product’s tax setting.
The PAC rejects the CFDI
Section titled “The PAC rejects the CFDI”The status is “Rejected by the PAC” with the PAC’s message (for example an unknown ClaveProdServ, a postal code that does not match the RFC in the SAT lists, or a regime that does not fit the CFDI use). Correct the data and press Issue again.
Nothing happens after an order changes status
Section titled “Nothing happens after an order changes status”- Check Settings > General > Enable and the order status settings. Only orders that carry an RFC get an individual CFDI at the issue status.
- Check the license status bar on the add-on pages.
- Open Jobs: queued jobs wait for cron. If the counts never change, the cron job is not running; run the command from the settings page by hand once.
A job is “Waiting to retry” or “Gave up”
Section titled “A job is “Waiting to retry” or “Gave up””The last error is shown in the list. Fix the cause (credentials, data, PAC outage) and press Retry. Jobs are retried automatically after 5 minutes, 15 minutes, 1 hour, 3 hours and 12 hours before they give up.
No global invoice was created
Section titled “No global invoice was created”The period must be closed; orders need the chosen status, a date inside the period, no individual CFDI and no customer RFC; the cron job must run; the add-on must be enabled and licensed. A period is invoiced once: after cancelling a global invoice create the replacement by hand on the CFDI 4.0 page.
The cron address answers “Forbidden”
Section titled “The cron address answers “Forbidden””The key in the address is wrong. Copy the address again from the settings page.
Still stuck
Section titled “Still stuck”Contact us through https://cs-cart.kaviolabs.com with the add-on version, the CS-Cart version and the relevant log lines (secrets are masked automatically).