It's been over a year since we got support for OmniKassa 2.0 have added to the Pronamic Pay plugin. On December 13, 2017, we launched version 1.0.0 of the OmniKassa 2.0 library for Pronamic Pay. Since then, we have continued to improve support for OmniKassa 2.0. In addition, we have also been able to solve a number of problems within OmniKassa 2.0 in collaboration with Rabobank.
Postpay item name
Since December 17, 2018, we also support the AfterPay payment method via OmniKassa 2.0. Support for AfterPay requires that more details about the payment be sent to the payment provider. For example, in addition to customer data, AfterPay also wants information about what needs to be paid for. For a WooCommerce order, AfterPay also wants to know which items have been ordered. To make this possible we have modified the Pronamic Pay plugin.
Due to this adjustment, information about the ordered items is now also forwarded to Rabobank for WooCommerce orders. You should think of the name of the ordered item, the price, VAT and the number of items. According to the documentation, OmniKassa 2.0 has a name limit of 50 characters. This while the name of a WooCommerce product can consist of thousands of characters. To handle this properly, we automatically truncate the name to a maximum of 50 characters.
Despite the fact that we automatically truncate the number of characters, reports were still received by our support department about the following OmniKassa 2.0 error:
the item name is too long, maximum length is 
After a long search, we found out that Rabobank did not handle special HTML characters such as
< and the
&-sign. In addition, Rabobank did not handle multibyte characters properly (such as the Russian and Chinese characters). After reporting this problem, Rabobank resolved this problem after more than 20 days. More information about this issue can be found at GitHub wp-pay-gateways/omnikassa-2/issues/1.
Rabobank blocks WordPress
At the beginning of August 2018, our support department received many messages that OmniKassa 2.0 payments could no longer be started. Again after a long search, we found out that all requests from WordPress websites were blocked by the OmniKassa 2.0 servers. Rabobank was able to do this because WordPress indicates by default via the User-Agent header that the request originates from WordPress. This problem was probably caused by a server migration and an overly configured firewall on the new OmniKassa 2.0 servers. Fortunately, Rabobank was able to solve this problem within 2 days. More information about this issue can also be found at GitHub wp-pay-gateways/omnikassa-2/issues/2.
Quality Rabobank OmniKassa 2.0
If we look back at the problems we encountered in the Rabobank OmniKassa 2.0 solution, you can start to doubt the quality of this solution. Our support department is also quite busy dealing with OmniKassa 2.0 problems. In particular, the payment status feedback via the webhook appears to be an error-prone system. Many other payment providers have a simpler system for this. In that respect, it is a pity that Rabobank did not take a close look at the competition. Fortunately, the Rabobank OmniKassa 2.0 solution is becoming more and more stable. Hopefully, Rabobank will continue to invest in the further improvement of OmniKassa 2.0 in the coming years. And don't they suddenly introduce OmniKassa 3.0 with new problems and a mandatory switch.
OmniKassa 2.0 for WordPress
Thanks to good contact with Rabobank, we were able to achieve a very good integration with OmniKassa 2.0 for WordPress. In addition to support for the popular webshop plugin WooCommerce, we also support many other plugins. You can think of the powerful forms plugin Gravity Forms. But also other forms plugins such as Formidable Forms and Ninja Forms. In addition, we also support membership plugins such as
s2Member, membership and MemberPress. We can also add Event Espresso, Give, Charitable, Restrict Content Pro and Easy Digital Downloads to this list.
We continue to improve the Pronamic Pay plugin and OmniKassa 2.0 integration. We try to keep the quality of our software as high as possible with the help of so-called code quality tools. For example, the OmniKassa 2.0 library complies with the WordPress Coding Standards. In addition, we also use tools such as Scrutinizer, PHPStan and Psalm to detect and resolve issues. Furthermore, we are of course always open to suggestions and are happy to help you connect your WordPress website or webshop to Rabobank OmniKassa 2.0. Feel free to do this Contact with us.