Skip to content

Troubleshooting

Both plugins

The plugin isn't listed under Settings → Plugins. pretix only reads installed plugins at startup — restart it (web server and Celery workers) after pip install. Make sure you installed into the same Python environment pretix runs from.

euPago

Payments stay pending forever. Payments are only confirmed by euPago's webhook. Check that:

  • the webhook URL https://<your-pretix-domain>/eupago/webhook/ is set in euPago's Backoffice for every channel you use (Webhooks);
  • your pretix instance is reachable from the internet at that address;
  • the Webhook key is set under Settings → euPago — without it, v2.0 payment notifications are refused;
  • the pretix log shows euPago webhook lines when a payment is made — if there are none, euPago isn't reaching you.

The webhook answers webhook key not configured. A v2.0 payment or refund notification arrived for an event with no Webhook key set. Copy the channel's webhook key from Backoffice into Settings → euPago. euPago retries failed notifications for a while, so recent payments usually confirm by themselves once it's set; confirm older ones by hand.

A v1.0 notification is ignored (chave_api mismatch in the log). The notification carried an API key that doesn't match the one configured in pretix. Copy the API key for that channel again from Backoffice → Channels → Channel Listing.

The webhook answers invalid signature. A v2.0 notification's signature doesn't match the Webhook key. Copy the key again from the channel's webhook settings in Backoffice.

The webhook answers invalid credentials (encrypted webhooks). The notification was encrypted with another event's webhook key, not the key of the event the payment belongs to. Check each event has its own channel's key.

Notifications arrive, but nothing happens (encrypted webhooks). With euPago's "encrypt" option turned on, the pretix log shows could not decrypt payload with any configured webhook secret. The notification is acknowledged but ignored, so euPago won't resend it. Set the channel's key as the Webhook key in pretix, then confirm the affected payments by hand.

Multibanco and MB WAY aren't offered at checkout. They're hidden when the event's currency isn't the euro, or when Sandbox mode is on but the event isn't in test mode. The Settings → euPago page shows a warning for either case.

Checkout says "Could not reach the payment provider" or "The payment provider returned an error". The request to euPago failed. Usually a wrong API key, or Sandbox mode not matching the key: sandbox and production keys are different.

Checkout says "We couldn't send the MB WAY request to this number". euPago refused the MB WAY request — usually the number isn't registered with MB WAY. The buyer can try another number or payment method. The euPago response is in the pretix log.

"euPago sandbox mode is active" is shown at checkout. Turn off Sandbox mode before selling for real — no real payment is taken in sandbox.

The buyer didn't approve MB WAY in time. The request expires after 5 minutes. The buyer can pay again from their order page.

A payment was made, but the order is still expired (quota is exceeded in the log). The buyer paid after the order expired and its tickets were sold. The payment is recorded on the order; refund it or free up a ticket by hand.

A refund made in euPago doesn't show up in pretix. It's recorded when euPago sends a Refund notification — check the webhook is working. Refunds can't be started from pretix.

PT invoicing

Most problems show up in the Invoicing (PT) dashboard or the order's Invoicing (PT) panel, with the provider's message. Once the cause is fixed, press Retry.

A paid order has no invoice, and no row in the dashboard. Issuance is skipped silently when:

  • no Invoicing provider is selected, on the event or on its organizer, or the provider card was picked but never saved (the settings page then shows Not in use yet);
  • Issue documents automatically is off;
  • the plugin isn't enabled for the event (the organizer's settings alone don't enable it), or the order isn't paid;
  • the order is free: a total of 0.00 is never invoiced.

Fix the settings, then use Issue invoice now on the order page. Orders paid before the plugin was set up need this too; for many of them, see Bulk issuance.

Not issued: Fact.pt is not fully configured, or its connection has expired. The provider is selected but can't issue: Fact.pt has no API token, a required Moloni setting is empty, or the Moloni connection expired. The row is kept so the order isn't forgotten. Fix the settings, then press Retry.

A row stays in "Processing". The task was queued but never ran: pretix's Celery workers aren't running, or aren't picking up tasks. Check them. After ten minutes the row is no longer considered in progress and Retry appears.

… — retrying automatically in a few minutes / … — gave up after several attempts A network failure with the provider. The first message means the task will try again by itself (three times, a couple of minutes apart); the second that every retry failed. Press Retry once the provider is reachable. Retrying never issues twice: Fact.pt rejects duplicates, and the plugin asks Moloni for an existing document before every attempt. If the failed call did create the document, the retry finds it and links it to the order.

… — the document may or may not have been created. Check in … before retrying Only shown for a provider that can neither reject a duplicate nor be asked for an existing document. Neither bundled provider is one since 0.9; rows that failed on an older version may still carry the message. Pressing Retry on them is safe now, for the reason above.

VAT mismatch: pretix charged X% on this order but the configured Fact.pt rate is Y% pretix and Fact.pt disagree on the VAT rate, and the invoice would be for the wrong amount. Either fix the event's tax rule in pretix, or pick the matching VAT rate in the plugin settings. See Fact.pt.

VAT rate N does not exist in this Fact.pt account. The configured rate was deleted in Fact.pt, or the token belongs to another account (or the other environment — check Use sandbox environment). Pick a rate again.

Multiple clients with same tin. Specify an ID. Fact.pt has several clients with the buyer's NIF, and the plugin won't guess which one to invoice. Merge or delete the duplicates in Fact.pt's Backoffice, then retry.

Could not reach Fact.pt: … / Could not reach Moloni: … The provider was down or unreachable. See the retry messages above: the task retries by itself.

price: Trying to use an item having more than 2 decimal digits, in an incompatible series. The series tied to the Fact.pt API key has 2 decimal places. The plugin needs an 8-decimal series; assign one to the key in Fact.pt's Backoffice. See Setting up Fact.pt.

Invalid response from Fact.pt (HTTP …) Often a production token used against the sandbox, or the other way round. Check Use sandbox environment.

Moloni rejected the request. followed by a list of fields Moloni's validation errors, one per field. document_set_id or document_set_wsat_id must be valid means the chosen series doesn't fit: not of the right document type (credit notes need their own series), or not from the selected company. Pick the series again in the settings and retry.

Moloni has N customers with tax number X. Merge them in Moloni, then retry. Several Moloni customers share the buyer's NIF, and the plugin won't guess which one to invoice. Merge them in Moloni, then press Retry.

Moloni refused the credentials. Check the developer ID, client secret, username and password. They're checked live when you fill them in: errors show under the Moloni settings.

Not connected to Moloni, or the connection has expired. The Moloni connection is missing or expired, and no username/password is set to fall back on. Press Connect to Moloni (or Reconnect) in the settings, then retry. The plugin refreshes the connection daily, so this usually means Moloni revoked it. If the event's page reads The organizer's connection to Moloni has expired, reconnect on the organizer's Settings → Invoicing (PT) instead; that restores it for every event using it. See The connection.

The reference “…” of “…” has N characters; Moloni allows 30. Prefix and product reference together exceed Moloni's limit. Nothing was created. Shorten the product's reference on its page, or the Product reference prefix in the settings, then retry. See Products.

An event ignores a change made in the organizer's invoicing settings. The event has saved its own value for that setting, which keeps applying. Open the event's Settings → Invoicing (PT) and either set the value there, or press Use the organizer's settings to drop everything the event stored itself. See Organizer-wide settings.

VAT mismatch: pretix charged X% on this order but the configured Moloni rate is Y% Same as for Fact.pt: fix the event's tax rule, or pick the matching VAT rate. Nothing was created in Moloni. See Taxes.

This order has 0% VAT lines, which Moloni only accepts with an exemption reason. Set an Exemption reason (e.g. M07) in the Moloni settings, then retry.

The VAT rate / company / document set dropdowns don't appear. They're filled from your provider account once the credentials are valid. If they stay plain number fields, the line under the provider's settings shows why (bad token, provider unreachable).

The invoice was made out to a final consumer, but the buyer gave a NIF. pretix only asks business customers for a VAT ID. Collect it from everyone with a custom invoice-address field; see Tax numbers (NIF). NIFs that fail the Portuguese check digit are ignored (spaces, dots and a PT prefix are fine).

Portuguese business buyers can't complete checkout. pretix's Require VAT ID is on while the custom field holds the NIF, which hides pretix's VAT ID field for Portuguese addresses. Turn the requirement off.

"Please enter your tax number (NIF) in the invoice address." at checkout. Require the tax number at checkout is on, and the buyer has a Portuguese address without a NIF: a business always has to give one, an individual when pretix's Require invoice address is on. If that isn't what you want, turn the option off. See Requiring the NIF.

"The buyer changed their billing details after invoice … was issued." Not an error: the buyer edited their invoice address after being invoiced, and the event's contact address got the same message by e-mail. An issued document can't be changed. To accept the new data, press Issue credit note, then Issue invoice now; to keep the document as is, ignore it. See Billing changes after invoicing.

The Moloni PDF shows a unit price of 34,99999 instead of 35,00. Moloni stores unit prices to 5 decimals, and a tax-inclusive price divided by 1.23 never ends. The incidence, VAT and total are correct. See Taxes.

An order was refunded, but no credit note was issued. One is only issued automatically when:

  • the refund is marked done in pretix;
  • refunds add up to the full amount paid — a partial refund issues nothing;
  • the order's invoice was issued successfully.

Otherwise, use Issue credit note on the order page. See Credit notes.

The buyer didn't receive the document by e-mail. Both e-mails are off by default — turn them on under E-mail. A failed e-mail doesn't mark the issuance as failed; check the pretix log.

The PDF download returns "not found". The document was issued by a different provider than the one currently selected, and the old provider's credentials aren't kept. Download it from that provider's back office. On the buyer's side, the download also disappears when Show the invoice on the buyer's order page is off or the plugin is disabled for the event.