Question 1

How do I use Not Paid on a WordPress site?

Accepted Answer

Use the community-created WordPress plugin mentioned in the README, which simplifies integration by handling the script loading automatically within the CMS.

Question 2

Is Not Paid better than legal action for non-payment?

Accepted Answer

Not Paid is a visual deterrent meant for gentle pressure, not a replacement for legal recourse. It's best used as a preliminary step while pursuing formal payment methods.

Question 3

Can I customize Not Paid to fade specific elements instead of the whole body?

Accepted Answer

No, the script only targets the body tag's opacity as per the default code. For element-specific fading, you'd need to modify the source JavaScript directly, which isn't supported due to the no-PR policy.

Question 4

How does Not Paid compare to server-side payment locks?

Accepted Answer

Not Paid is client-side and visual, making it less secure but more subtle than server-side locks that can completely block access. It's better for maintaining relationships but worse for enforcement.

Question 5

What happens if a client pays after the fade starts?

Accepted Answer

You would need to manually remove or disable the script, as there's no automated payment detection or reset feature built into the tool.

Question 6

Is Not Paid compatible with single-page applications like React or Angular?

Accepted Answer

Yes, via community versions for Angular or by embedding the JS file, but it may require testing since SPAs dynamically update the DOM, potentially interfering with opacity changes.

not-paid.js

What is not-paid.js?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions