Activating native SDI sending (SDI via POP)

Integrationswordpresssdi-via-pop2026-09-01

Goal

Activate SDI via POP, the native channel that sends electronic invoices to the Sistema di Interscambio (SDI, Italy’s Exchange System) directly from the WordPress site through the POP plugin, without going through Fatture in Cloud, Aruba, or a PEC mailbox.

Prerequisites

No minimum plan: activation is available on every plan, including Free. Sending uses the credits available on your account.
Only one invoice-sending channel can be active at a time: if Fatture in Cloud, Aruba, or SDI via PEC is already active, deactivate it before activating SDI via POP.

Steps

You can activate SDI via POP in two equivalent ways.

From the account panel (popapi.io)

After creating the account, go to My Account > Integrations, open the SDI via POP tab and enable “Activate SDI via POP”; you can also optionally enable digital signature and legal storage (conservazione sostitutiva).

From the WordPress plugin

If you’ve already completed the guided account setup:

Go to POP > General and refresh the license information to sync the connection.
Go to POP > Integrations and activate SDI via POP by clicking its card.

If instead you’re setting up the account for the first time, you can activate it directly from the company data section of the guided setup wizard: activation happens automatically when it’s completed.

Automatic and manual sending

Manual sending — the “Send Invoice” button in the invoices table; then use the “Notifications” button to manually check the outcome.
Automatic sending — the POP > Advanced > Automatic invoice sending tab: enable sending via WP-Cron in the background instead of synchronously on order status change.

Verify

After sending, check the outcome via the “Notifications” button on the invoice: it must show the status received from the SDI (delivered, rejected, etc.).

Common errors

Can’t activate SDI via POP while another channel is active — sending channels are mutually exclusive: first deactivate Fatture in Cloud, Aruba, or SDI via PEC from the same Integrations screen.
Sending returns a generic error — the most common causes reported by the system are: the channel doesn’t match the active one, the integration isn’t configured, an invalid action, or a document with an identifier that already exists. Verify that SDI via POP is actually the active channel and retry.

For the data contract (payload, field mapping), see api/sdi. To understand an SDI rejection, see sdi-invoice-rejected. For the alternative via a PEC mailbox, see sdi-via-pec.