Terms

The honest, short version.

Use the site, buy the book, build payment systems. Last updated May 2026.

Who we are

Payments Playbook is run by Sean Nieuwoudt and Beverley Merriman, the authors of the Payments Playbook. "We" and "us" in this document means the two of us.

Using the site

You're welcome to read, link to, and share anything on payments-playbook.com, including the free sample chapter. Don't try to break, scrape, or overload the site. Don't impersonate us. Don't pass off our content as your own.

Buying the book

When you buy the Payments Playbook, you receive a personal, non-transferable licence to read it, run the example code, and use what you learn in your own work. You may print one copy for your own use.

You may not redistribute, resell, sublicense, or post the book or its chapters publicly. If your team wants copies, get in touch about team licences.

Code examples

The Python examples in the book and at github.com (when published) are released under the MIT licence. You can copy them into your own projects, commercial or otherwise, with attribution appreciated but not required.

Updates

We ship updates to the book when we have something worth adding. Anyone who has bought the book gets every future update at no extra cost, delivered to the email address on the order.

Refunds

We offer a 30-day, no-questions-asked refund. Full details: the refund policy.

Warranties (or rather, the lack of them)

The book and the example code are provided "as is." We've shipped this stuff for ten years and we believe what's in here is correct, but payments standards, regulations, and processor APIs change. You are responsible for verifying that anything you implement actually works for your business and complies with your obligations.

Liability

To the extent allowed by law, we are not liable for indirect, incidental, or consequential losses arising from your use of the book or the site. If we are liable for something, our total liability is capped at the amount you paid us (so, $99 or whatever the price was on the day of purchase).

Privacy

How we handle your data is covered separately in the privacy policy.

Changes

We may update these terms from time to time. The date at the top tells you when they were last touched. If a change materially affects people who have already bought the book, we'll email them about it.

Governing law

These terms are governed by the laws of the country we are resident in at the time of purchase. If you have a dispute we can't resolve by email, the courts of that jurisdiction have exclusive authority. If you'd like specifics before purchasing, just ask.

Contact

Questions about these terms: hello@payments-playbook.com.

Questions

Anything on this page, email hello@payments-playbook.com. A person answers.

The book itself is 42 chapters on building payment systems that survive real customers.