## TL;DR

For "ModuleNotFoundError: No module named 'paddle_billing.Resources.IPAddresses'": importing Secret and Verifier from paddle\_billing.Notifications to verify webhooks failed on version 0.3.0 with: `` ModuleNotFoundError: No module named 'paddle\_billing.Resources.IPAddresses' ` The 0.3.0 release shipped with a broken internal import.

```text
ModuleNotFoundError: No module named 'paddle_billing.Resources.IPAddresses'
```

## Steps

1. Importing `Secret` and `Verifier` from `paddle_billing.Notifications` to verify
webhooks failed on version 0.3.0 with:

```
ModuleNotFoundError: No module named 'paddle_billing.Resources.IPAddresses'
```

2. The 0.3.0 release shipped with a broken internal import. The import chain broke
at `Client.py`, so any import of the package failed, not just the Notifications
import.

```
pip install -U 'paddle-billing>=0.3.1'
```

3. Fixed in 0.3.1; the reporter confirmed the fix within hours of the 0.3.1
release.

## When to use

You are seeing this: The import chain broke at Client.py`, so any import of the package failed, not just the Notifications import. Use this skill when you run into "ModuleNotFoundError paddle_billing.Resources.IPAddresses on 0.3.0 (fixed in 0.3.1)".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: 0.3.0, paddle-billing 0.3.1. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.