Changelog
This is the official PaySlate changelog. Track every release of PaySlate, the WordPress invoicing plugin that collects card payments through the Stripe and Square payment gateways.
New here? Start with how PaySlate works or the download page.

PaySlate is free in the WordPress.org plugin directory. Release notes below follow the same version numbers you see in your WordPress dashboard.
26.08.25.01
Unattended updates that can roll themselves back
PaySlate can now keep itself up to date without anyone clicking Update. It takes a snapshot first, installs the release, then asks the site whether it still works and puts the previous version back if the answer is no. The payment ledger finishes its migration in the background, and the plugin listing now describes PaySlate as billing software rather than an invoice generator.
Improvements (6)
- Let a site ask PaySlate to keep itself up to date, and install the release rather than only offering it
- Take a snapshot before an unattended update, so there is always something to go back to
- Check the site still responds after an update, and restore the previous version if it does not
- Keep the paid add-on current from the free side
- Report a payment to both stores while the ledger finishes reconciling
- Make the update packages describe themselves honestly
Fixes (6)
- Keep answering at the webhook address sites were already given
- Restore the plugin directory itself rather than its scattered contents
- Prepare the filesystem before copying a plugin aside
- Move the snapshot back into place instead of copying over it
- Do not roll a release back because the health probe was refused
- Hold the probe token where the probe request can actually see it
Patches (2)
- Declared compatibility with WordPress 7.1
- Rewrote the directory listing around billing, and swapped an unused tag for billing
26.08.07.11
The payment ledger, and settings you can navigate
Moves every payment onto a single ledger and carries the existing records across on its own, with no command to run. Settings becomes a set of real tabs with room to work, and PaySlate now tells you when payment confirmations are being blocked instead of failing quietly.
Improvements (7)
- Moved payments onto a single ledger, with existing records migrated automatically
- Rebuilt Settings as real tabs that use the full width of the screen
- Added the exports screen and a late fee section to Settings
- Added the License screen
- Added the recurring billing settings screen
- Told the administrator when payment confirmations are being blocked
- Added Settings and Docs links on the Plugins screen
Fixes (2)
- Fixed an invoice issue date that could be stored as zero
- Covered the Square webhook path that could leave a payment unconfirmed
Patches (1)
- Removed the legacy payment engine now that the ledger is authoritative
26.07.31.01
Payment reliability and settings hardening
Improves how Stripe and Square payments and their webhooks are handled, hardens settings saves against partial writes, and makes sure a copied invoice link still works for your client even when the email failed to deliver.
Improvements (3)
- Improved Stripe and Square payment reliability and webhook handling
- Added Ledger and Notifications settings controls
- Improved invoice email failure guidance with a manual sharing option
Fixes (2)
- Prevented partial settings saves when validation fails
- Fixed copied invoice links so customers can still pay after an email delivery failure
Patches (0)
26.07.30.10
Initial release on WordPress.org
PaySlate is live in the WordPress.org plugin directory: create professional invoices and get paid by card through Stripe or Square, right on your own site.
Improvements (6)
- Professional invoices with line items, tax, discounts, due dates, and notes
- Stripe and Square payment gateways: clients pay by card on your site
- Deposits, full payments, or custom partial amounts
- Invoice tracking at a glance: sent, viewed, partial, paid, or overdue
- Automatic receipts and gentle overdue reminders
- Client-facing invoice pages with no account required