Title: Japanized for WooCommerce Author: shohei.tanaka Published: 22 June 2014 Last modified: 13 October 2026 --- Search plugins ![](https://ps.w.org/woocommerce-for-japan/assets/banner-772x250.png?rev=3242427) ![](https://ps.w.org/woocommerce-for-japan/assets/icon.svg?rev=3242427) # Japanized for WooCommerce By [shohei.tanaka](https://profiles.wordpress.org/shoheitanaka/) [Download](https://downloads.wordpress.org/plugin/woocommerce-for-japan.2.9.17.zip) * [Details](https://en-gb.wordpress.org/plugins/woocommerce-for-japan/#description) * [Reviews](https://en-gb.wordpress.org/plugins/woocommerce-for-japan/#reviews) * [Installation](https://en-gb.wordpress.org/plugins/woocommerce-for-japan/#installation) * [Development](https://en-gb.wordpress.org/plugins/woocommerce-for-japan/#developers) [Support](https://wordpress.org/support/plugin/woocommerce-for-japan/) ## Description Japanized for WooCommerce is the essential toolkit for running a WooCommerce store in Japan. This plugin bridges the gap between WooCommerce’s global features and Japan’s unique e-commerce requirements. **Why You Need This Plugin** Running an online store in Japan requires specific features that standard WooCommerce doesn’t provide out of the box: * Japanese address formats with proper field ordering( postal code, prefecture, city, address lines) * Name reading fields (Yomigana/Furigana) for accurate customer identification * Delivery date and time selection that customers expect * Popular Japanese payment methods like bank transfer and COD * Legal compliance with Japan’s Specified Commercial Transaction Act (特定商取引法) **Who Should Use This** This plugin is designed for: * Japanese e-commerce businesses using WooCommerce* International stores shipping to Japanese customers * Anyone who needs Japanese address handling and payment methods * Stores requiring delivery date/time selection functionality **Seamless Integration** Works smoothly with WooCommerce core features and popular extensions. Fully compatible with the new WooCommerce Blocks checkout experience. All features are optional – enable only what you need for your store. #### Key Features **Address & Name Management** * Name reading (Yomigana/Furigana) input fields for billing and shipping addresses * Honorific title (様/sama) automatically added after customer names * Japanese-style address format with proper field ordering * Auto- fill address from postal code using Yahoo! API integration * Company name field support **Shipping & Delivery** * Delivery date and time selection at checkout * Delivery time slot management * Holiday and non-delivery day settings * Weekend and specific date exclusions * Delivery-related fields hidden when free shipping is applied **Payment Methods** * Bank Transfer (Japanese banks) * Japan Post Bank Transfer* Cash on Delivery (COD) with fee calculation * COD subscription support * Pay at Store (over-the-counter payment) * Paidy (Buy Now, Pay Later) – Official Japanese payment gateway **Legal & Compliance** * Specified Commercial Transaction Act (特定商取引法) page creator * Shortcode support for legal information display * Customizable legal notice templates **Additional Features** * Email template optimization for Japanese format * Address validation for Japanese postal codes * Affiliate integration (A8.net, Access Trade, Value Commerce) * WooCommerce Blocks compatibility Note: Paidy Checkout is also available as a standalone payment plugin. #### External Services This plugin connects to the following third-party services: * **Yahoo! Japan Web API** (yahoo.co.jp) — used by the postal-code auto-fill feature to look up a Japanese address from a postal code entered at checkout. The postal code is sent to Yahoo! Japan’s address lookup API whenever a customer uses this feature; it uses a merchant-configured Application ID (Japan Settings Address Form) if one is set, and a bundled shared ID otherwise, so it is active whenever the postal-code auto-fill feature itself is used, not only once an ID is configured. See Yahoo! Japan’s own site for their terms of service and privacy policy. * **Paidy payment API** (api.paidy.com) — used by the Paidy (Buy Now, Pay Later) payment gateway to process and verify payments. Only active when the Paidy gateway is enabled. See Paidy’s own site for their terms of service and privacy policy. * **Artisan Workshop Paidy onboarding intermediary** (paidy.artws.info) — used only while applying for a Paidy merchant account through this plugin’s setup wizard (available even before the gateway is enabled, since onboarding is how it becomes eligible to be enabled). Submitting the application form sends the store’s site name and URL, the merchant’s contact details (email, phone), the representative’s name and date of birth, the submitted screening survey answers, and a site-specific verification hash, to this Artisan Workshop-operated intermediary, which relays the application to Paidy and later delivers the issued API credentials back to the site. * **Artisan Workshop promotion service** (wc.artws.info) — the plugin’s own first- party service. It is contacted automatically (no setting to disable it) to fetch promotional notice content shown in the WordPress admin dashboard to users who can manage WooCommerce, on stores with at least one order placed in the last 5 days. No order, customer, or site-configuration data is sent or received beyond the request itself. ## Screenshots [⌊General Settings - Configure name reading (Yomigana) fields, address display options, and honorific titles.⌉⌊General Settings - Configure name reading (Yomigana) fields, address display options, and honorific titles.⌉[ General Settings – Configure name reading (Yomigana) fields, address display options, and honorific titles. [⌊Shipment Settings - Set up delivery date designation, delivery time zones, holidays, and shipping notification options.⌉⌊Shipment Settings - Set up delivery date designation, delivery time zones, holidays, and shipping notification options.⌉[ Shipment Settings – Set up delivery date designation, delivery time zones, holidays, and shipping notification options. [⌊Payment Settings - Enable and configure Japanese payment methods including bank transfer, postal transfer, pay at store, and extra charge settings.⌉⌊Payment Settings- Enable and configure Japanese payment methods including bank transfer, postal transfer, pay at store, and extra charge settings.⌉[ Payment Settings – Enable and configure Japanese payment methods including bank transfer, postal transfer, pay at store, and extra charge settings. [⌊Law Settings - Configure Specified Commercial Transaction Law (特定商取引法) information including shop name, company details, owner information, and legal notices.⌉⌊Law Settings - Configure Specified Commercial Transaction Law (特定商取引法) information including shop name, company details, owner information, and legal notices.⌉[ Law Settings – Configure Specified Commercial Transaction Law (特定商取引法) information including shop name, company details, owner information, and legal notices. [⌊Affiliate Settings - Set up affiliate tracking for Japanese affiliate networks including A8.net, Felmat (ValueCommerce), and Access Trade.⌉⌊Affiliate Settings - Set up affiliate tracking for Japanese affiliate networks including A8.net, Felmat( ValueCommerce), and Access Trade.⌉[ Affiliate Settings – Set up affiliate tracking for Japanese affiliate networks including A8.net, Felmat (ValueCommerce), and Access Trade. [⌊Checkout Block - WooCommerce Blocks checkout page displaying Japanese address format, name reading fields, and delivery date/time selection.⌉⌊Checkout Block - WooCommerce Blocks checkout page displaying Japanese address format, name reading fields, and delivery date/time selection.⌉[ Checkout Block – WooCommerce Blocks checkout page displaying Japanese address format, name reading fields, and delivery date/time selection. [⌊Classic Checkout - Traditional WooCommerce checkout page with Japanese localization features including address fields and delivery options.⌉⌊Classic Checkout - Traditional WooCommerce checkout page with Japanese localization features including address fields and delivery options.⌉[ Classic Checkout – Traditional WooCommerce checkout page with Japanese localization features including address fields and delivery options. ## Installation #### Minimum Requirements * WordPress 6.0 or greater * WooCommerce 8.0 or greater * PHP version 8.3 or greater * MySQL version 5.6 or greater * WP Memory limit of 64 MB or greater (128 MB or higher is preferred) #### Automatic installation Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of Japanized For WooCommerce, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New. In the search field type “Japanized For WooCommerce” and click Search Plugins. Once you’ve found our eCommerce plugin you can view details about it such as the the point release, rating and description. Most importantly of course, you can install it by simply clicking “Install Now”. #### Manual installation The manual installation method involves downloading and uploading our plugin to your webserver via your favorite FTP application. ## FAQ ### Do I need this plugin to use WooCommerce in Japan? While WooCommerce can work in Japan without this plugin, Japanized for WooCommerce provides essential features that Japanese customers expect, such as delivery date selection, name reading fields (Yomigana), and local payment methods. It significantly improves the user experience for Japanese e-commerce. ### Does this plugin work with WooCommerce Blocks? Yes! Version 2.8.0 and later fully supports the new WooCommerce Blocks checkout experience, including delivery date selection and custom address fields. ### How do I enable the postal code auto-fill feature? You need to obtain a free Yahoo! Japan Application ID from the Yahoo! Developer Network. Once you have the ID, enter it in the WooCommerce Settings Japan Settings Address Form section.(Classic Checkout only) ### Which payment methods are included? The plugin includes: Bank Transfer (Japanese banks), Japan Post Bank Transfer, Cash on Delivery (COD) with fee calculation, Pay at Store, and Paidy (Buy Now, Pay Later). Paidy is also available as a standalone plugin. ### Can I use only specific features and disable others? Yes, absolutely! All features are modular and can be enabled or disabled individually from the plugin settings. You only need to activate the features your store requires. ### Is the plugin compatible with multilingual sites? Yes, the plugin is compatible with WPML and other multilingual plugins. It automatically detects the language and adjusts features accordingly. Japanese-specific features are only applied when the site language is set to Japanese. ### How do I set up delivery date and time selection? Go to WooCommerce Settings Japan Settings Delivery Date. You can configure available delivery times, set holidays, exclude specific days of the week, and customize the delivery date display format. ### Does this plugin modify WooCommerce core files? No, the plugin uses WordPress and WooCommerce hooks and filters. It doesn’t modify any core files, making it safe to use and easy to update. ### Where can I get support? For support, please visit the [plugin support forum](https://wordpress.org/support/plugin/woocommerce-for-japan/) on WordPress.org or check the [official documentation](https://wc.artws.info/). ### Is this plugin free? Yes, Japanized for WooCommerce is completely free and open source under the GPLv3 license. ## Reviews ![](https://secure.gravatar.com/avatar/45e81fce153b2db8ebaac33f8bcc8c565ee454c9961f28fd59f53904c0a73c3f? s=60&d=retro&r=g) ### 󠀁[Used to like it but not anymore](https://wordpress.org/support/topic/an-essential-plugin-for-any-woocommerce-site-targeting-japan/)󠁿 [ostonegi](https://profiles.wordpress.org/ostonegi/) 14 March 2025 This plugin used to be good but now they are pushing a "paid security package" and fear mongering. They have added a pretty useless "malware" scan that marks a lot of normal php files used by other known and popular plugins as "suspicious". I understand trying to leverage the financial potential but this way is just lame.Thank you but no thank you. ![](https://secure.gravatar.com/avatar/ea4e6a0ac9028812d8d379a8215b586eec2030c86fdcd45920d5354a0383c33c? s=60&d=retro&r=g) ### 󠀁[2.6.27 『このサイトで重大なエラー』](https://wordpress.org/support/topic/2-6-27-%e3%80%8e%e3%81%93%e3%81%ae%e3%82%b5%e3%82%a4%e3%83%88%e3%81%a7%e9%87%8d%e5%a4%a7%e3%81%aa%e3%82%a8%e3%83%a9%e3%83%bc%e3%80%8f/)󠁿 [yuyu009](https://profiles.wordpress.org/yuyu009/) 3 March 2025 Japanized for WooCommerce最近、更新間隔が短いので注意していたのですが無効化してから 更新しても 『このサイトで重大なエラー』 発生しました。 復旧作業疲れました。 ![](https://secure.gravatar.com/avatar/a9d2818e54af13629feed6882e56fb0d99e59ae4ba608975e21e53d0977398a4? s=60&d=retro&r=g) ### 󠀁[Fatal error: Uncaught Error: Call to undefined function get_current_screen()](https://wordpress.org/support/topic/fatal-error-uncaught-error-call-to-undefined-function-get_current_screen-2/)󠁿 [3488521](https://profiles.wordpress.org/4273a551/) 16 July 2024 2 replies Version2.6.15にアップデートしたらエラーになりました。 wp-content/plugins/woocommerce- for-japan/woocommerce-for-japan.php on line 159表示されます。 ![](https://secure.gravatar.com/avatar/7c85ca646f66baf2ddb6eef6939b723f37f6237b34e143c41906cd08310336c0? s=60&d=retro&r=g) ### 󠀁[休日設定をしても配達希望日として設定できてしまう](https://wordpress.org/support/topic/%e4%bc%91%e6%97%a5%e8%a8%ad%e5%ae%9a%e3%82%92%e3%81%97%e3%81%a6%e3%82%82%e9%85%8d%e9%81%94%e5%b8%8c%e6%9c%9b%e6%97%a5%e3%81%a8%e3%81%97%e3%81%a6%e8%a8%ad%e5%ae%9a%e3%81%a7%e3%81%8d%e3%81%a6%e3%81%97/)󠁿 [bocchimktg](https://profiles.wordpress.org/bocchimktg/) 11 April 2023 食料品には対応してない印象を受けます。生鮮食品関係のECで無料版を利用していますが、 いくら休日期間を設定してもお客側からは配達希望日を設定できてしまいます。商品の消費 期限が短く出荷調整などがあるため、こちらで休日とした日はお客側には配達希望日として 表示しないようにして頂けると助かります。3年前のフォーラムでも似たような質問（配送 に関する新機能希望2020年3月25日）が出ていて機能追加される旨が書いてありましたがプロ 版では対応されていますか？ ![](https://secure.gravatar.com/avatar/80e532cc1c91d71329a9ae3eeff434029f9691987c78cce18f3481796da4c8bb? s=60&d=retro&r=g) ### 󠀁[レスポンスも更新もありません 追記：いただけました](https://wordpress.org/support/topic/%e3%83%ac%e3%82%b9%e3%83%9d%e3%83%b3%e3%82%b9%e3%82%82%e6%9b%b4%e6%96%b0%e3%82%82%e3%81%82%e3%82%8a%e3%81%be%e3%81%9b%e3%82%93/)󠁿 [Takahashi Ei](https://profiles.wordpress.org/enjoybeerlife/) 10 June 2022 3 replies 非常に意義のあるプラグインだと思いますが、更新が継続されていないようで残念です。— 追記： 更新再開していただけました。感謝いたします。 いささか身勝手な書き方になって しまって、お詫び申し上げます。 今後とも応援させていただきます。 ![](https://secure.gravatar.com/avatar/13f7f455b0e5efb64918fd4bc46f81ae8232f37679b7b638f53ac198086d1422? s=60&d=retro&r=g) ### 󠀁[良いですね。ありがとうございます。](https://wordpress.org/support/topic/%e8%89%af%e3%81%84%e3%81%a7%e3%81%99%e3%81%ad%e3%80%82%e3%81%82%e3%82%8a%e3%81%8c%e3%81%a8%e3%81%86%e3%81%94%e3%81%96%e3%81%84%e3%81%be%e3%81%99%e3%80%82/)󠁿 [souichiroukikuchi](https://profiles.wordpress.org/souichiroukikuchi/) 7 March 2021 昨日にインストールして色々と設定を行っています。 WooCommerceを日本の商習慣にロー カライズするプラグインで使いやすいです。 ありがとうございます。 １点、不具合（な のかな？） 配達予約可能開始日で当日配送ができる場合は0を入力してください、とあっ たので0を入力すると、なぜか2で表示されます。 2を入力した時も２で表示されるので見た目 からは違いが分かりませんでした。 バージョンは2.2.12 WPのバージョンは5.6.2 です。 [ Read all 21 reviews ](https://wordpress.org/support/plugin/woocommerce-for-japan/reviews/) ## Contributors and Developers “Japanized for WooCommerce” is open source software. The following people have contributed to this plugin. Contributors * [ shohei.tanaka ](https://profiles.wordpress.org/shoheitanaka/) * [ Artisan-Workshop ](https://profiles.wordpress.org/artisan-workshop-1/) * [ Soft Steps EC ](https://profiles.wordpress.org/ssec4dev/) “Japanized for WooCommerce” has been translated into 1 locale. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/woocommerce-for-japan/contributors) for their contributions. [Translate “Japanized for WooCommerce” into your language.](https://translate.wordpress.org/projects/wp-plugins/woocommerce-for-japan) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/woocommerce-for-japan/), check out the [SVN repository](https://plugins.svn.wordpress.org/woocommerce-for-japan/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/woocommerce-for-japan/) by [RSS](https://plugins.trac.wordpress.org/log/woocommerce-for-japan/?limit=100&mode=stop_on_copy&format=rss). ## Change Log #### 2.9.17 – 2026-10-13 * **Added** – A “Morning” (午前中) option can be shown as the first delivery time zone: enable it under Delivery settings Delivery time settings (off by default) and customise its label; it is offered on both the classic and the block checkout and works even when no hourly time zone is registered (which previously caused a TypeError on the classic checkout); the Yamato B2 export of Japanized for WooCommerce Pro does not support it yet, so keep it off if you use that export until a Pro update adds it * **Fixed** – Paidy payments whose payment ID contains a hyphen (`-`) were rejected by the payment ID format check and never marked as paid, leaving the order pending until the stock hold cancelled it even though the customer had paid; the check now accepts the base64url alphabet Paidy actually uses (`pay_[A-Za-z0-9_-]+`) while keeping the URL injection protection (#223) * **Fixed** – In the Checkout block the Cash on Delivery fee could get out of step with the selected payment method on slower servers (a fee left behind after switching to another method, or missing after switching to COD); the fee is now calculated from WooCommerce’s own `chosen_payment_method` and from the payment method submitted with the order (#215) * **Fixed** – Saving any tab of the Japanized for WooCommerce settings screen wiped a Cash on Delivery fee that had been configured on the COD gateway’s own settings page; the settings screen now reports the values actually in force so they are preserved (#218) * **Fixed** – The delivery date, delivery time zone and shipping date entered on the classic checkout were stored HTML-encoded (`&`, `'`, `"`), so a time zone label containing `&`, `'` or `"` was saved differently from the block checkout and showed up encoded in plain-text order emails; the values are now stored as entered, like the block checkout and the admin meta box, and escaped only where they are displayed (#224) * **Fixed** – Paidy Checkout failed to open on the payment page (a JavaScript syntax error) for orders with a zero-discount coupon such as a free-shipping coupon, a line item whose product had been deleted, or a fee whose name contains a line break or backslash, so the customer could not pay with Paidy and the order was left pending; the order items are now passed to Paidy as JSON, which also stops`&` and similar characters in product and coupon names from showing up as `&` on the Paidy screen (#232) * **Fixed** – A connection error or timeout on a Paidy cancel, capture or refund request caused a fatal error (“Cannot use object of type WP_Error as array”), which for a refund left behind a WooCommerce refund that Paidy never made, and a refund answered without a status (for example a 502 error page) was also recorded as refunded; these requests now count as successful only when Paidy returns the payment as closed, and otherwise fail with an order note that includes the HTTP status (#231) * **Fixed** – Applying for Paidy again through the onboarding wizard after a cancelled review or a plugin reinstall sent the application without the site hash that encrypts the delivered API keys and signs the key-delivery callback (and logged a PHP “Undefined variable” warning), so the API keys could not be delivered automatically; the application now always sends the hash the site has stored, creating and storing one when none is saved (#234) * **Fixed** – Changing a Paidy order from Processing to Cancelled sent the cancel( close) request to Paidy up to three times, so the requests after the first one failed with HTTP 409 and left “cancellation not completed” order notes on an order that Paidy had in fact cancelled; a failed capture or refund was likewise sent and reported more than once. The capture, cancel and refund callbacks now run once per order status change, and the bundled Japanese translation of that order note, which said the opposite of the original, has been corrected (#241) * **Fixed** – A second partial refund of a Paidy order failed (“An error occurred while attempting to create the refund using the payment gateway API.”), and changing a partly refunded Paidy order from Completed to Cancelled did not refund the rest, because only the first refund of an order was ever sent to Paidy; every refund is now sent, and the automatic refund on cancellation refunds only the remaining amount and is recorded as a WooCommerce refund, so the customer also receives the “refunded” e-mail for it (the order stays Cancelled) (#243) * **Security** – A Checkout block draft order could be paid by Cash on Delivery through the Store API pay-for-order route or the classic order-pay page without the COD fee being applied; both paths now refuse COD/COD2 for draft orders and direct the customer to the checkout page * **Security** – The order’s transaction ID is now validated against the Paidy payment ID format and `rawurlencode()`-escaped before it is put into the cancel, capture and refund API URLs, as the payment lookup has been since 2.9.14; for an ID that does not match, no request is sent to Paidy and an order note is added( a capture also e-mails the shop’s notice address) (#233) * **Removed** – The usage tracking feature has been removed in preparation for a new feature that will replace it; no usage data is sent from this version on, and its setting, scheduled event and stored options are cleaned up on update (# 239) * **Changed** – The notification e-mail sent when a required delivery date or time zone is missing now goes only to the shop’s notification address (#239) * **Changed** – Tested up to WordPress 7.1 and WooCommerce 11.2.1 #### 2.9.16 – 2026-09-07 * **Added** – Paidy onboarding callbacks can now be authenticated via an HMAC-SHA256 signature shared at application time, in addition to the one-time state token; this restores automatic API key delivery for merchants whose token had already expired or was never issued * **Added** – A “Back to Paidy settings” link on the onboarding “under review” screen so merchants who received their Paidy API keys separately can enter them manually without waiting for automatic delivery * **Security** – Fixed a replay/idempotency gap where two concurrent Paidy onboarding callbacks authorized by the same state token (without an accompanying signature) could both be processed, duplicating the credential/status update * **Security** – Paidy onboarding callbacks are now authenticated strictly from the signed request body; a query-string parameter could previously override a value that was actually covered by the signature * **Security** – Paidy onboarding callbacks for an application that is no longer the current one on record are now rejected, preventing a delayed or resent callback from overwriting a newer application’s credentials * **Security** – The Cash on Delivery / COD2 surcharge configured for Block Checkout could be bypassed by sending an invalid payment gateway ID to the cart-update endpoint while still completing the order via COD; the gateway ID is now validated against the site’s registered gateways * **Security** – Decrypted Paidy API secret keys are no longer duplicated in plaintext in the diagnostic `paidy_received_data` option; they remain stored (as before) in the gateway’s own settings * **Fixed** – `wizard=false` now correctly shows the Paidy gateway’s manual configuration fields * **Fixed** – Uninstalling the plugin now also removes the signature- and event- claim option rows created by the onboarding receiver’s replay guards * **Fixed** – A `wp_remote_post()` failure during Paidy onboarding submission no longer also falls through to the HTTP-response-code error branch, avoiding duplicate log entries * **Changed** – The admin promotion notice and its “has recent orders” check are now cached for a short period instead of making an uncached remote request and database query on every wp-admin page load * **Changed** – Tested up to WordPress 7.1 and WooCommerce 11.1.0 #### 2.9.15 – 2026-07-08 * **Added** – COD fee feature for the “Cash on Delivery for Subscriptions” (COD2) gateway: fee name, amount, maximum cart amount, tax settings, and a PRO tiered- fee table can now be configured on the gateway settings page * **Added** – Toggleable debug logging for COD2 fee calculation; enable “Debug mode” on the gateway settings page to log calculation details (start values, max-amount check, filter results, applied fee) to WooCommerce Status Logs ( source: `jp4wc-cod2-fee`) * **Added** – Tax label (e.g. `(incl. tax)`) after the COD fee amount in cart/checkout totals on the classic checkout, following the same display logic as WooCommerce core subtotal/shipping rows; applied only to the JP4WC gateway fee * **Fixed** – Deleting all rows of the COD2 tiered-fee table and saving restored the previous data; an empty table is now saved correctly (early return happens only on nonce failure) * **Fixed** – Duplicated place-order row (privacy text, terms checkbox, order button) accumulating on every classic-checkout update when the admin-edited Paidy description contained unbalanced HTML; the description is now balanced with `force_balance_tags()` on output and validated on save * **Fixed** – `403 paidy_invalid_state` error on Paidy Instant Onboarding key delivery when the merchant review took longer than 2 days; the one-time state token is now stored as a non-autoloaded option with an application-level expiry instead of a transient, so it survives until the callback arrives * **Fixed** – Paidy settings wizard redirect no longer injects or rewrites the ` pk_test_` prefix into the saved test API public key; key management is left entirely to the user * **Fixed** – Yomigana (reading) fields duplicated on the My Account order details page (`view-order`); the duplicate additional-field rows are now suppressed there as well as on the order received page * **Fixed** – Yomigana displayed twice (and editable twice) on the admin order edit screen for orders placed via the block checkout; the Additional Checkout Fields API entries injected by WooCommerce core are now removed from the billing/ shipping field lists since JP4WC already embeds yomigana in the formatted address #### 2.9.14 – 2026-06-22 * **Fixed** – Paidy payment verification was always failing (HTTP 404) because the gateway incorrectly used POST for `GET /payments/{id}`; switched to `wp_safe_remote_get()` so payment status checks now succeed and order completion is unblocked * **Security** – `payment_id` parameter is now validated against the Paidy format(` pay_[A-Za-z0-9_]+`) and `rawurlencode()`-escaped before being interpolated into the API URL, preventing path/query injection from buyer-controllable transaction IDs * **Fixed** – Paidy payment_id regex was too strict (rejected underscores); updated to `pay_[A-Za-z0-9_]+` to match actual Paidy IDs such as `pay_aii8_kYAAEYA2BDW` #### 2.9.13 – 2026-05-27 * **Security** – Fixed Broken Access Control (CVSS 6.5) in Paidy payment gateway REST endpoints: `paidy-receiver/v1/receive` now enforces a one-time per-session state token (stored as a per-token transient keyed by the 32-char value itself so parallel sessions cannot clobber each other); `paidy/v1/order` and `paidy/ v1/check` now require either HMAC signature verification or an IP allowlist — the previous unconditional `return true` fallback has been removed * **Security** – State token parameter is validated for type and format (32-char alphanumeric) before use as a transient key suffix to prevent non-string or oversized inputs on the unauthenticated receiver endpoint * **Security** – State transient is consumed only after the handler completes successfully so transient DB / decryption failures do not permanently prevent retrying the onboarding callback; orphaned transients are cleaned up when `wp_remote_post()` fails * **Fixed** – WP_Error messages for base64 and AES-256-CBC decryption failures in the Paidy receiver are now translatable via `__()` / `sprintf()` with a `% s` field-name placeholder * **Fixed** – Missing Paidy API key fields (absent from the intermediary POST) are now merged into `$filtered_params` as empty strings so downstream code can access all four key fields unconditionally without undefined-index notices #### 2.9.12 – 2026-05-21 * **Fixed** – Yomigana (reading) fields duplicated on My Account address edit form when block checkout is active; `woocommerce_address_to_edit` filter now removes` _wc_{type}/jp4wc/yomigana_*` duplicates when traditional `{type}_yomigana_*` fields are already present (classic checkout), and suppresses traditional fields when only WC Additional Fields API keys are registered (block checkout) * **Fixed** – Yomigana rows duplicated on My Account Addresses view page (`/my- account/?edit-address`) for both classic and block checkout; WC Additional Fields API `render_address_fields` callback is now removed before it fires when JP4WC yomigana is enabled, eliminating the extra “Last Name ( Yomigana )” label rows * **Fixed** – My Account Addresses view page did not display yomigana for block checkout users whose data is stored only in `_wc_billing/jp4wc/yomigana_*` meta keys; `formatted_address()` now reads both classic (`{type}_yomigana_*`) and block (`_wc_{type}/jp4wc/yomigana_*`) meta keys, selecting the set that matches the active checkout type * **Fixed** – `{last_name}`, `{first_name}`, and `{yomigana_*}` placeholders appeared as literal text in the Block Checkout address summary; address format filter now correctly handles block checkout context * **Changed** – Removed unused PayPal Express Checkout (`ppec_paypal`) compatibility code that referenced a decommissioned gateway #### 2.9.11 – 2026-05-11 * **Fixed** – Fatal error in `jp4wc_delivery_check_data()` on Classic Checkout with Square / Amazon Pay; `woocommerce_payment_successful_result` was registered with 1 argument so `$result['order_id']` was undefined when gateways omit it —` wc_get_order(null)` returned false, causing a PHP Fatal Error on `$order->get_meta()` and corrupting the AJAX redirect to the Thank You page; filter now accepts 2 arguments and `$order_id` arrives as the second parameter; added early-return guard when `wc_get_order()` returns false (Closes #166) * **Fixed** – Yomigana (reading) fields no longer appeared in order emails after 2.9.10; restored accidentally removed `woocommerce_localisation_address_formats` filter registration that injects `{yomigana_last_name}` / `{yomigana_first_name}` placeholders into the JP address format template * **Changed** – “NOT registered” delivery log messages changed from `log_info` to `log_debug` (WP_DEBUG only) to stop a 2 MB/day log flood on sites with delivery date disabled * **Changed** – Removed unused `display_admin_order_meta()` method in `JP4WC_Delivery` that was never registered to any hook (dead code since introduction) #### 2.9.10 – 2026-04-27 * **Security** – `jp4wc_hide_notices()` now requires `manage_woocommerce` capability before processing notice-dismissal requests * **Fixed** – Admin order edit page displayed 名|姓 instead of 姓|名; CSS overrides now swap float directions for first/last name fields to restore the correct Japanese display order * **Fixed** – Admin order address field CSS was not applied on HPOS screens; enqueue now covers all screen ID variants including `admin_page_wc-orders` and uses a` $_GET['page']` fallback for early-init cases * **Fixed** – JP4WC admin CSS was overridden by WooCommerce’s cascade; inline styles are now attached directly after `woocommerce_admin_styles` at `admin_enqueue_scripts` priority 20 to guarantee the overrides take effect * **Improved** – Admin address field ordering rewritten with an order-list approach that preserves fields injected by third-party plugins and guards against yomigana field duplication * **Improved** – Admin settings panel: Classic Checkout settings (Company name, Zip auto-entry, Free shipping display) grouped under a dedicated section; added PRO notice for Block Checkout zip auto-entry * **Changed** – Removed unused `woocommerce_billing_fields`/`woocommerce_shipping_fields` filter and streamlined yomigana field handling in address replacements #### 2.9.9 – 2026-04-23 * **Fixed** – COD fee not applied in Classic Checkout (Shortcode) or Block Checkout because `jp4wc_calculate_order_totals` read from `woocommerce_cod_settings` while the JP4WC admin UI saves to `wc4jp-extra_charge_*` options; settings are now merged at runtime with JP4WC values taking precedence * **Fixed** – `extra_charge_calc_taxes` mismatch: React admin UI stored `yes`/` no` but PHP expected `no-tax`/`tax-excl`/`tax-incl`; legacy values are now normalised on read and the admin UI updated to a 3-way select * **Fixed** – Stale `jp4wc_gateway_id` session value could cause COD fee to be silently skipped in Classic Checkout (double session-check removed; gateway ID resolved once and passed through the entire calculation) * **Improved** – Block Checkout fee script now uses exponential back-off retry ( 100 ms 10 s) instead of fixed 1500 ms / 3000 ms timeouts to wait for `wc/store/ payment` store readiness * **Added** – PRO-ready filter hooks for COD fee: `jp4wc_cod_fee_settings`, `jp4wc_cod_fee_name`,` jp4wc_cod_fee_amount`, `jp4wc_cod_fee_is_applicable`, `jp4wc_cod_fee_tax_class`( all `@since 2.9.8`) * **Changed** – Minimum required PHP version raised from 8.1 to 8.3 #### 2.9.6 – 2026-04-22 * **Fixed** – Paidy webhook permission check rejected all notifications from Paidy( no `x-paidy-signature` header) causing orders to remain “pending” and be auto- cancelled * **Fixed** – Paidy webhook signature verification used wrong option name `secret_key`( non-existent); corrected to `api_secret_key` / `test_api_secret_key` based on test mode * **Fixed** – Bank transfer (`bankjp`) account skip condition `! isset( $account_names[ $i] )` was always false; replaced with `empty( $bank_names[$i] ) && empty( $name)` to properly skip blank rows * **Added** – Deduplication of bank transfer account entries on save and load to prevent double display caused by corrupted option data * **Fixed** – Yomigana (読み仮名) fields not displayed in HTML emails when using Block Checkout; corrected meta key fallback from `_wc_other/` to `_wc_billing/` and `_wc_shipping/` prefixes * **Fixed** – Yomigana displayed twice on order received (thank-you) page when using Block Checkout * **Fixed** – Yomigana appearing as a separate bold `` list below the formatted address in emails and thank-you page; now suppressed via `show_in_order_confirmation: false` and block render filter * **Fixed** – “(よみがなを確認するには「編集」をクリックしてください。)” message incorrectly appearing in new order emails * **Fixed** – Customer email salutation showing first name only instead of full name (姓名); email context detection now uses `WC_Email::$sending` flag for reliability with WC 10.7+ BlockEmailRenderer * **Added** – Country is hidden from formatted address in emails and thank-you page when the store sells to only one country #### 2.9.5 – 2026-04-20 * **Fixed** – White screen on frontend caused by fatal error in Paidy blocks support when gateway is not registered * **Fixed** – `WC_Gateway_Paidy not found` fatal error on admin pages when WooCommerce is installed with a non-standard path (e.g. wp-env) * **Fixed** – `jp4wc_has_orders_in_last_5_days` undefined function error caused by `is_woocommerce_active()` returning false in non-standard install paths * **Fixed** – Google Calendar consultation button not displaying on some hosting environments (Xserver) due to CSP/WAF blocking external script injection; replaced with a plain link * **Added** – `jp4wc_allowed_setting_keys` filter to allow add-on plugins to register their own setting keys with the REST API * **Added** – `jp4wc_setting_option_map` filter to allow add-on plugins to map REST keys to their existing WordPress option names * **Added** – `jp4wc.settings.tabs` and `jp4wc.settings.tabContent` JS filters via `@wordpress/hooks` to allow add-on plugins to inject tabs into the React settings UI #### 2.9.0 & 2.9.4 – 2026-03-19 * **Fixed** – COD fee not calculating in Classic Checkout due to `is_admin()` returning true for admin-ajax.php requests * **Fixed** – COD fee showing for non-COD payment methods in Classic Checkout ( stale session value) * **Fixed** – COD fee incorrectly displayed on cart page (now checkout-only) * **Fixed** – Delivery date/time fields not appearing in Checkout Block (changed` class_exists` to `interface_exists` for IntegrationInterface) * **Fixed** – Delivery select placeholder showing WooCommerce auto-generated text instead of admin-configured label * **Fixed** – Paidy order completion hook firing multiple times (added `paidy_capture_id` guard) * **Fixed** – `_load_textdomain_just_in_time` warning in WordPress 6.7+ by deferring translations to after `init` * **Fixed** – `JP4WC_Framework` config strings now lazy-loaded at `init` priority 2 to prevent early textdomain calls * **Fixed** – `WC_Paidy_Endpoint` instantiation deferred to `init` priority 11 to prevent early `WC_Gateway_Paidy` construction * **Removed** – PayPal settings removed from admin settings UI and API #### Earlier versions [View complete changelog](https://wc.artws.info/doc/detail-woocommerce-for-japan/wc4jp-change-log/) ## Meta * Version **2.9.17** * Last updated **4 days ago** * Active installations **10,000+** * WordPress version ** 6.7 or higher ** * Tested up to **7.1.3** * PHP version ** 8.3 or higher ** * Languages * [English (US)](https://wordpress.org/plugins/woocommerce-for-japan/) and [Japanese](https://ja.wordpress.org/plugins/woocommerce-for-japan/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/woocommerce-for-japan) * Tags * [e-commerce](https://en-gb.wordpress.org/plugins/tags/e-commerce/)[ecommerce](https://en-gb.wordpress.org/plugins/tags/ecommerce/) [Japanese](https://en-gb.wordpress.org/plugins/tags/japanese/)[woocommerce](https://en-gb.wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://en-gb.wordpress.org/plugins/woocommerce-for-japan/advanced/) ## Ratings 3.3 out of 5 stars. * [ 9 5-star reviews ](https://wordpress.org/support/plugin/woocommerce-for-japan/reviews/?filter=5) * [ 2 4-star reviews ](https://wordpress.org/support/plugin/woocommerce-for-japan/reviews/?filter=4) * [ 1 3-star review ](https://wordpress.org/support/plugin/woocommerce-for-japan/reviews/?filter=3) * [ 5 2-star reviews ](https://wordpress.org/support/plugin/woocommerce-for-japan/reviews/?filter=2) * [ 4 1-star reviews ](https://wordpress.org/support/plugin/woocommerce-for-japan/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/woocommerce-for-japan/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/woocommerce-for-japan/reviews/) ## Contributors * [ shohei.tanaka ](https://profiles.wordpress.org/shoheitanaka/) * [ Artisan-Workshop ](https://profiles.wordpress.org/artisan-workshop-1/) * [ Soft Steps EC ](https://profiles.wordpress.org/ssec4dev/) ## Support Issues resolved in last two months: 0 out of 1 [View support forum](https://wordpress.org/support/plugin/woocommerce-for-japan/) ## Donate Would you like to support the advancement of this plugin? [ Donate to this plugin ](https://www.paypal.com/cgi-bin/webscr?cmd=_xclick&business=info@artws.info&item_name=Donation+for+Artisan¤cy_code=JPY)