v4.3

last updated: Oct 15, 2020

✨ Highlights

• Introducing Konbini payment method. (PR #149)

🚀 Enhancements

• PayNow, adding a link to the QR code url at the order-confirmation email. (PR #185)

v4.2

last updated: Sep 15, 2020

🚀 Enhancements

• Removing Gruntfile and package.json as no longer needed grunt-wp-i18n library. (PR #187)

👾 Bug Fixes

• Updating deprecated functions in WooCommerce v3. (PR #189)
• Adding permission to callback which helps to removes a warning message on Wordpress 5.5. (PR #188)

v4.1

Merge pull request #186 from omise/release-4-1

✨ Releasing Omise-WooCommerce v4.1

v4.0

Merge pull request #181 from omise/release-4-0

✨ Releasing Omise-WooCommerce v4.0

v3.11

last updated: Mar 23, 2020

✨ Highlights

PR #152: Introducing PayNow payment method (only available in Singapore)
As Omise has been providing a support for PayNow payment method.
This pull request is to integrate the new PayNow payment to WooCommerce plugin.

🚀 Enhancements

• PR #153: (proposal) Code cleaning for payment method classes.
• PR #151: Payment Setting: properly display payment methods based on a given Omise Account (for admin)

v3.10

last updated: Jan 17, 2020

✨ Highlights

PR #146: Credit Card payment, automatically detect if a particular charge is processing using 3-D Secure feature.

A mistake has been happened repeatedly when it comes to enable 3-D Secure feature on Omise plugin. As the current flow of enabling 3-D Secure on Omise-WooCommerce is as the following:

1. Contact Omise support to enable the feature (or Omise support team may be the one who initiate a contact to merchant first, vice versa)
2. Omise enables the 3-D Secure feature, then inform back to merchant.
3. Merchant needs to go back to Omise-WooCommerce setting page, then enable 3-D Secure feature at the Credit Card Payment Setting page.

However, the third step is where thing gets complicated and mistake occurs. Either "enable 3-D Secure on the plugin but not on Omise account" or "enable 3-D Secure on Omise account but not on Omise plugin".

This pull request is to reduce the amount of this issue by programmatically detect if a particular charge is likely to be processed with 3-D Secure feature, then automatically redirect buyers out without having to alter any setting.

🚀 Enhancements

• PR #147: Code refactoring for a better i18n for strings that were in JS files.
• PR #143: Refactoring offsite payment methods (introducing abstract offsite class).

📝 Documents

• PR #145: README, polishing and updating all missing contents.

v3.9

last updated: Oct 31, 2019

✨ Highlights

• PR #139: Introducing TrueMoney payment (only available in Thailand).

🚀 Enhancements

• PR #142: Bill Payment, correcting order status after a new order is placed (on-hold instead of pending-payment).
• PR #140: Adding ability to sync payment status to Bill Payment and TrueMoney Payment.

v3.8

last updated: Sep 17, 2019

👾 Bug Fixes

• PR #137: Billpayment - check if an order is made by Bill Payment before display a barcode.

v3.7

last updated: Sep 13, 2019

✨ Highlights

• PR #122: Introducing Bill Payment.
  Including: #125, #126, #128, #129.

👾 Bug Fixes

• PR #131: Event "charge.complete", making sure that event's charge id is identical with order transaction id.
• PR #130: Fixing calling Omise_Money's non-static method statically.

📝 Documents

• PR #127: Updating README.md, adding 2 missing payment methods at 'Enable Payment Method' section.

v3.6

last updated: Aug 1, 2019

✨ Highlights

• PR #118: Better way to handle amount subunit, adding support for more currencies.

🚀 Enhancements

• PR #124: Updating npm vulnerable dependencies.