In order to test the EAN Gateway use the following test numbers:  

• 3017600920604 (Valid, 1 punits)
• 0710535576603 (Valid, 1 punits)
• 4040404040406 (Valid, 19 punits)

If you want to read more about how EAN-13 numbers are verified please visit this Wiki which explains the details of the calculations

Version 5.0.4 – 2023-01-31

• Bugfix: Allow e-mails to be sent for order status “Pending payment” (wc-pending)

Version 5.0.3 – 2023-01-30

• New: WooCommerce 7.3.0 compatibility flag.
• Bugfix: Use the defined text for receipt pages.
• New: Introduced the filter ‘filter_yanco_ean_woocommerce_thankyou_order_received_text’ to allow for further customization of the displayed text.

Version 5.0.2 – 2023-01-10

• New: WooCommerce 7.2.2 compatibility flag.
• New: Deprecated descriptions in translations as these should come from options and not translations.
• Tweak: Use WooCommerce translations for order statuses.

Version 5.0.1 – 2022-08-02

• Fix: Added an error message to display a more correct message when an error occured with EAN API

Version 5.0.0 – 2022-03-24

• New: Introduced usage of wc_get_order_statuses to control which statuses are available under the settings.
• New: Introduced the filter ‘yanco_ean_payment_gateway_remove_non_actionable_statuses’ that filters out ‘non-actionable’ statuses (wc-cancelled, wc-refunded, wc-failed).
• New: Upgraded to sweetalert2
• New: Updated WooCommerce supported version
• New: Replaced use of cURL and file_get_contents in favor of wp_remote_post
• New: Security audit of the plugin
• Fix: Save the CVR number to the meta_key vat_number

Version 4.2.0 – 2021-04-04

• New: Updated software updater to the latest version
• New: Updated WooCommerce supported version

Version 4.1.0 – 2020-11-13

• New: Added option to control the subscription status when the customer changes payment method to EAN Payment Gateway
• New: Added option to enter EAN information when changing to EAN Payment Gateway from the Admin Subscription view
• New: Removed Meta boxes on Subscription view in favor of being able to change Payment Method
• Tweak: Display the EAN API information on the Subscription view based on the selected payment method

Version 4.0.3 – 2020-11-11

• Fix: Called the wrong HelperClass

Version 4.0.2 – 2020-11-11

• New: Enhanced the support for WooCommerce Subscriptions

Version 4.0.0 – 2020-11-08

• New: Upgraded to EAN API version 4 (https://eanapi.dk)
• New: Refactored the entire codebase
• New: Option to enable customers to choose a Production Unit during checkout
• New: Option to set default order status for WooCommerce Subscriptions orders (separate status from the regular orders)
• New: Option to set default order status for WooCommerce Subscriptions renewal/resubscribe/switch orders
• New: EAN API Information is now per default collapsed in the WooCommerce order overview to save space and to have a better overview for users
• New: EAN API Information can now be clicked on to display it in the WooCommerce order overview
• New: Added sweetalert.js to handle dialogues for a more pleasant user experience
• New: Show EAN Subscription Renewal description in Order overview
• Tweak: Changed translation texts for clarification purposes
• Tweak: Changed default order status to Pending Payment
• Tweak: Changed the default e-mail text and message on the order receipt page slightly to give customer a better indication on of the order process.
• Tweak: Only allow logged in users to save the EAN Payment Info as we can’t save details to non-logged in users
• Tweak: Updated translations
• Fix: Include e-mail instructions in order e-mail
• Fix: When enabling reference person required and having the reference/requisition fields disabled, resulted in an error during checkout
• Fix: When enabling requisition number required and having the reference/requisition fields disabled, resulted in an error during checkout
• Remove: Option “Error message” as it was not needed (You can change the error message using language files)

Version 3.4.1 – 2019-12-12

• Tweak: Added VAT number to the information on the order

Version 3.4.0 – 2019-12-11

• New: Added option to prevent EAN-orders changing to order status cancelled.
• Tweak: Updated Danish translation

Version 3.3.0 – 2019-07-30

• New: Check if cURL or allow_url_fopen and display a notice if none of them are available
• New: Detect if cURL is available and if true, use it to communicate with EAN API
• New: If cURL isn’t available, but allow_url_fopen is, then fallback to use file_get_contents for communicating with EAN API
• Tweak: Updated Danish translation

Version 3.2.0 – 2019-07-09

• New: Setting to allow customers to save the EAN Payment Information on their user profile
• New: Customers can now choose to save the EAN Payment Information on their user profile if enabled in the settings
• Tweak: Small change to the thank you page displaying the information properly under billing information

Version 3.1.2 – 2019-05-16

• Tweak: Added support for checking if WooCommerce is active on multisite
• Fix: Proper validation for reference person and requisition number

Version 3.1.1 – 2019-04-24

• Tweak: Changed default order status from “On Hold” to “Pending”
• Fix: Added support for checking if WooCommerce is active on multisite
• Fix: Bug fix for orders that are updated manually changing to EAN Orders

Version 3.1.0 – 2019-04-14

• New: Added integration with WooCommerce Subscriptions
• New: Added option to create manual EAN Orders
• New: Added option to create manual EAN Subscriptions if you’re using WooCommerce Subscriptions
• New: Added CVR information to the EAN Data
• Tweak: Refeactored the code to prepare for the new EAN data
• Tweak: Moved EAN information to billing column in orders

Version 3.0.0 – 2019-01-31

• !! IMPORTANT !! If you are upgrading from version 2.X to version 3.X you will need to deactivate the plugin and reactivate the plugin again, then enter your API key. We’ve made several improvements to the API licensing server to ensure future feature and compatibility. We are sorry for the inconvenience about this. If your license key reports an invalid key, please visit https://plugins.yanco.dk/my-account and login to make sure your license key has not changed.
• Refactored the License API
• Refactored the Main plugin code
• Made option to select required / optional for requisition number
• Made option to select required / optional for reference person

Version 2.2.0 – 2018-04-14

• Added an option to decline an order where the EAN number isn’t found in Nemhandelsregisteret

Version 2.1.0 – 2018-02-14

• Changes to be compatible with WooCommerce 3.3+ on the Orders Screen and Order Preview

Version 2.0.2 – 2018-02-14

• Bumped the version number as it was stuck with release of 2.0.1 – Sorry! :-)

Version 2.0.1 – 2018-02-10

• Major feature: Added API integration to get EAN data from Nemhandelsregisteret

Version 1.2.1 – 2017-12-23

• Added option to control order status

Version 1.2.0 – 2017-12-02

• Added option to show requisition number field
• Added option to show reference person field
• The information for requisition number and reference person are shown on orders in the administration area
• Added EAN Information to “View Order” in the customers’ “My Account”

Version 1.1.8 – 2017-08-28

• WooCommerce 3.0+ Compatibility. Removed PHP Notices for WooCommerce “Order properties should not be accessed directly.”

Version 1.1.7 – 2017-01-05

• Moved EAN number on the customers page to “Customer Details” section
• Moved EAN number in the emails to “Customer Details” section
• Added EAN number to the shipping column in the administration if an order was placed, using the EAN Payment Gateway

Version 1.1.6 – 2016-09-02

• Added EAN data to e-mails being sent to customer and to order details

Version 1.1.5 – 2016-04-04

• Refactored required plugins check for multi-site
• Fix: Removed string translations from defaults in options

Version 1.1.4

• Added a test EAN number to the readme
• Added PO files
• Added Danish Translation

Version 1.1.3

• Refactored some methods

Version 1.1.2

• Fixed authenticaion with API Manager, refactored plugin

Version 1.1.1

• Fixed an error with API Manager

Version 1.1.0

• Added API Manager

Version 1.0.0

• Initial version