Hey there! We just wrapped up another big release cycle, and honestly, v9.3 has a lot under the hood. There are improvements that actually matter for performance, a major step toward AI-powered payments, and quite a few quality-of-life fixes for both admins and customers. Let us break it down.
AI-Powered Payment Abilities: Getting Ready for the Future
This is easily the biggest headline in this release. WordPress 6.9 introduced the Abilities API, and Knit Pay now registers two core payment abilities on top of it:
- knit-pay/create-payment – creates a new payment request and returns a payment link.
- knit-pay/get-payment – retrieves the current status and details of a payment by its ID.
What does that mean in plain English? Any AI agent, automation tool, or future assistant that understands the WordPress Abilities API can now discover Knit Pay, create a payment on your behalf, and check whether it is completed, failed, or still pending. This is early days, but by building on the Abilities API now, we are making sure Knit Pay stays relevant as AI workflows become part of everyday site management.
For admins, the immediate benefit is that you will be able to build workflows or use tools that can check payment status automatically, without you logging into the dashboard every time.
A Leaner, Faster Plugin Under the Hood
We restructured how Knit Pay loads its code. The entire plugin now uses a PSR4 autoloader, which means your server loads only the specific code it needs at the exact moment it needs it. We also moved a bunch of lesser-used Composer packages into a separate secondary-packages directory.
If you are on shared hosting or a budget server, this matters:
- Less memory usage because unused code paths are not loaded into memory.
- A snappier admin dashboard, especially on high-traffic sites.
- Faster checkout processing because the plugin resolves files more efficiently.
We also replaced some older string-matching logic with PHP 8’s native str_starts_with function across the codebase. It is a small change, but it adds up when the plugin processes a large volume of payments.
Razorpay Now Supports Apple Pay
Knit Pay 9.3 adds Apple Pay as a payment method through Razorpay. If your international customers use iPhones or Macs, they can now complete payments using Face ID or Touch ID authentication instead of manually entering card numbers.
According to Razorpay’s own documentation, Apple Pay offers:
- Up to 58% improvement in checkout conversion rates for international customers.
- A 45% reduction in checkout time for Apple device users.
These numbers come straight from Razorpay’s official Apple Pay documentation. If you enable Razorpay through Knit Pay, Apple Pay will now appear for eligible customers on supported devices.
Cashfree Upgraded to API Version 2026-01-01
We migrated the Cashfree integration to their latest API version. Along with that, we improved how payment statuses are tracked internally.
For admins, the benefit is simple: fewer payments stuck in limbo. The status logic is now more reliable, so when Cashfree reports a payment as successful, failed, or pending, Knit Pay reflects that accurately without you needing to cross-check manually.
Vipps is Now Available in Knit Pay Pro
For merchants serving customers in Norway and Scandinavia, we have added support for Vipps through Knit Pay Pro. Vipps is the dominant mobile wallet in Norway, used by millions daily.
If your store serves that region, your customers can now pay with an app they already trust. No extra setup on their end, and no need for them to pull out a credit card.
LatePoint v5 Support — and the Integration is Now Free
LatePoint released a major v5 update with architectural changes that broke backward compatibility. We rebuilt our integration from the ground up to support it.
Here is the bigger news: the LatePoint integration is now completely free. Previously it was available as a premium add-on, but we realized that salons, clinics, consultants, and studios are a natural fit for Knit Pay. Paywalling the booking integration was just adding friction for businesses that should be accepting online payments right away.
The checkout experience has also been polished to match LatePoint’s official gateway styling, so your customers will not notice anything different.
Contact Form 7: Per-Form Payment Status Pages
If you use Contact Form 7 to collect payments, you already know Knit Pay can redirect customers to a status page after payment. But until now, you only had global default pages configured inside Knit Pay settings. Every form shared the same pages.
Starting with 9.3, each individual Contact Form 7 form can have its own custom payment status pages. You can set different pages for:
- Completed payments
- Cancelled payments
- Expired payments
- Error / failed payments
- Unknown / pending status
If you leave a page as “— Select —” for a particular form, it falls back to the global default like before. But if you run multiple forms (say, one for event registrations and another for donations), you can now send each one to a completely different thank-you or error page. No more one-size-fits-all redirects.
Bookly Pro: Payment Step Now Appears Reliably
We fixed a bug in Bookly Pro where the payment step would not show up if Knit Pay was the only payment gateway enabled. Bookly’s internal logic was not recognizing third-party gateways as active, so it simply skipped the payment step.
In 9.3, we hooked into Bookly’s configuration checks in a way that lets it see Knit Pay as a valid active gateway. Now, when someone books an appointment and Knit Pay is their only option, the payment step appears reliably every time. If you run a booking-based business, this removes a frustrating edge case that could silently cost you appointments.
Paid Memberships Pro: Billing Fields Hidden by Default
For Paid Memberships Pro users, we have hidden the billing address fields during checkout by default. Most membership sites do not actually need a physical billing address, and every extra field on a checkout page is another chance for a customer to abandon.
The setting is configurable, so if your use case genuinely needs billing details, you can re-enable them. But for the majority of membership businesses, the checkout is now leaner and faster.
Auto-Generated Configuration Titles
Small thing, but it saves real time. If you create a new gateway configuration and forget to give it a title, Knit Pay will now auto-generate one for you — something like “Razorpay #123” instead of leaving it blank or showing “Auto Draft.”
This matters when you have multiple configs and need to know which one is production versus testing. No more guessing.
Massive Code Quality Pass Across the Board
We ran a comprehensive pass of code standardization and cleanup across a long list of gateways:
- Razorpay
- CCAvenue
- Cashfree
- Instamojo
- iPay88
- Coinbase
- UPI QR
- Easebuzz
- Elavon Converge
- Thawani
- CMI
- CBK
- PhonePe
- Fiserv
- Sodexo
- PayU
We also cleaned up extensions including:
- Vik WP
- WP Adverts
- Contact Form 7
- Paid Memberships Pro
A lot of this cleanup was assisted by AI agents — Claude, GLM, DeepSeek, Kimi, and Kilo all helped catch deprecated patterns and edge cases.
What does this mean for you? Better compatibility with PHP 8.2 and newer WordPress versions, fewer unexpected warnings after updates, and a more stable foundation for whatever we build next. We are investing in code health because we want Knit Pay to keep running smoothly for years.
PayU UPI Preselection Fixed
PayU updated their documentation to specify lowercase “upi” instead of uppercase “UPI” for the UPI payment method identifier. That tiny casing difference was causing UPI to not get preselected properly for some merchant accounts at checkout.
We updated it to match PayU’s current spec. UPI now auto-selects correctly across all PayU configurations.
Time to Update!
Version 9.3 is about getting Knit Pay ready for what is coming next — AI agents, newer PHP versions, and evolving payment APIs — while keeping everyday tasks smooth for admins and customers.
If you have not updated yet, head to your WordPress dashboard and hit update. As always, back up first, and reach out if anything feels off after the update.
Happy accepting payments!