Title: GlobePay for WooCommerce Author: globepay Published: August 31, 2026 Last modified: August 31, 2026 --- Search plugins ![](https://s.w.org/plugins/geopattern-icon/globepay-for-woocommerce.svg) # GlobePay for WooCommerce By [globepay](https://profiles.wordpress.org/globepay/) [Download](https://downloads.wordpress.org/plugin/globepay-for-woocommerce.0.1.24.zip) * [Details](https://wordpress.org/plugins/globepay-for-woocommerce/#description) * [Reviews](https://wordpress.org/plugins/globepay-for-woocommerce/#reviews) * [Installation](https://wordpress.org/plugins/globepay-for-woocommerce/#installation) * [Development](https://wordpress.org/plugins/globepay-for-woocommerce/#developers) [Support](https://wordpress.org/support/plugin/globepay-for-woocommerce/) ## Description GlobePay for WooCommerce connects a WooCommerce store to GlobePay Hosted Checkout. Customers are redirected to GlobePay to complete payment; the plugin does not collect or store full card numbers, CVV, PINs, or track data. The plugin currently supports the documented production Common Cashier API flow for JPY. GlobePay’s Common Cashier presents the payment methods enabled for the merchant account in its hosted cashier. The plugin supports Classic Checkout, signed server-to-server payment notifications, payment query/reconciliation services, and WooCommerce full or partial refunds where the merchant account and GlobePay API permissions support them. WooCommerce HPOS compatibility is declared through the WooCommerce compatibility API. Payment confirmation is based on a verified GlobePay notification or a server-side payment query. A browser return is not treated as payment confirmation. An active GlobePay merchant account and valid Partner Code/Credential Code are required. Checkout Blocks and a confirmed GlobePay Sandbox endpoint are not claimed by this release. ### External services This plugin connects to GlobePay services operated by Japan GlobePay Co., Ltd. (` https://pay.globepay.co.jp`) to create hosted checkout sessions, query payment status, and submit/query refunds. Hosted checkout redirects are accepted only for the documented GlobePay API host and the GlobePay-operated cashier host `https://jp.globalfreepay. com`. For a payment creation request, the plugin sends the unique WooCommerce payment- attempt identifier, order description, integer JPY amount, the store’s notification URL, the WooCommerce order-received URL, and the configured operator value. Requests also contain the configured Partner Code and a generated request timestamp/nonce/ signature as required by the GlobePay API. The store return URL is sent as `redirect`; the production Common Cashier response returns the hosted cashier URL as `pay_url`, and the browser redirect adds a fresh signed `redirect`, `time`, `nonce_str`, and` sign` query set. Payment query and refund requests send the payment-attempt identifier and, for refunds, the refund identifier and integer API refund amount. GlobePay sends signed payment notifications to the configured WordPress REST callback URL. The plugin validates these callback fields: `time`, `nonce_str`, `sign`, `partner_order_id`,` order_id`, `total_fee`, `real_fee`, and `currency`. Notifications must be within the documented five-minute time window, are protected against cross-order replay, and are confirmed with a server-side Payment Query before the WooCommerce order is completed. The data is sent to create and process payments, query transaction status, and process refunds. Refunds should be initiated from the WooCommerce order; refunds made directly in the GlobePay merchant console are not automatically imported into WooCommerce because the documented notification API covers payment-success notifications only. GlobePay’s Privacy Policy is available at https://file.globepay.co.jp/open/globepay_privacy_use_policy. html. GlobePay’s Terms and Conditions are available at https://www.globepay.co.jp/? regulations/. ### Privacy The plugin stores WooCommerce order-related GlobePay metadata locally, including the Partner Order ID, integer amount, currency, GlobePay transaction ID, and webhook idempotency key. Merchant credentials are stored in WooCommerce payment settings, are never rendered with their saved value in the admin HTML, and are not rendered in customer-facing pages. Payment processing sends the order and transaction data described in the External services section to GlobePay. The plugin does not include telemetry, advertising tracking, remote executable-code loading, or a card-input form. ## Installation 1. Install and activate WooCommerce. 2. Upload the `globepay-for-woocommerce` directory to `/wp-content/plugins/`, or install the release ZIP from the WordPress admin. 3. Activate GlobePay for WooCommerce. 4. Go to WooCommerce > Settings > Payments > GlobePay. 5. Enter the Partner Code and Credential Code supplied by Japan GlobePay. 6. Enable the gateway and save the settings. ## FAQ ### Does the plugin handle card numbers? No. The customer is redirected to GlobePay Hosted Checkout. The plugin sends the order data required to create the checkout and receives signed payment notifications. ### Is a browser redirect enough to mark an order paid? No. The browser return is for user experience only. The plugin requires a verified GlobePay notification or server-side query before calling WooCommerce payment completion. ### Does this release support Checkout Blocks? No. This release supports Classic Checkout. Checkout Blocks support will be documented separately after it has been implemented and tested. ### Does this release include a Sandbox environment? This release uses the confirmed Production endpoint only. Sandbox is not offered until Japan GlobePay publishes a confirmed Sandbox endpoint in the approved API documentation. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “GlobePay for WooCommerce” is open source software. The following people have contributed to this plugin. Contributors * [ globepay ](https://profiles.wordpress.org/globepay/) [Translate “GlobePay for WooCommerce” into your language.](https://translate.wordpress.org/projects/wp-plugins/globepay-for-woocommerce) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/globepay-for-woocommerce/), check out the [SVN repository](https://plugins.svn.wordpress.org/globepay-for-woocommerce/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/globepay-for-woocommerce/) by [RSS](https://plugins.trac.wordpress.org/log/globepay-for-woocommerce/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.1.24 * Added a standard PHP URL-parser fallback for isolated service tests without changing WordPress URL validation behavior. #### 0.1.23 * Removed the unnecessary manual translation-loading hook; WordPress.org loads plugin translations automatically. #### 0.1.22 * Fixed cumulative refund validation so each refund is limited by the order amount remaining after previous WooCommerce refunds. #### 0.1.21 * Kept accepted asynchronous refunds in a pending state and added scheduled refund- status reconciliation to prevent duplicate refund submissions. * Added order notes for refund submission, confirmation, and provider-side failure or manual intervention. #### 0.1.20 * Aligned refunds with the current official API: `SUCCESS` means submission accepted; WooCommerce is marked refunded only after `FINISHED` is confirmed by the refund- status API. #### 0.1.19 * Added scheduled payment-query reconciliation for pending GlobePay attempts. * Added safe API response summaries to debug logs without logging credentials or signatures. * Addressed WordPress Plugin Check escaping and WordPress URL parsing findings. #### 0.1.18 * Accepted the documented GlobePay refund `FINISHED` status when funds have been returned, while continuing to reject pending, failed, and manual-operation statuses. * Updated the tested compatibility declaration to WordPress 7.1 based on real acceptance testing. * Removed the obsolete runtime Translator class and regenerated translation sources without deleted settings fields. #### 0.1.17 * Aligned Common Cashier payment creation with the documented JSON Schema by removing the unsupported `preauth` field. #### 0.1.16 * Fixed refunds to use the saved GlobePay Partner Order ID for the payment attempt instead of the WooCommerce order number. #### 0.1.15 * Restored the documented signed `redirect`, `time`, `nonce_str`, and `sign` parameters on the Common Cashier `pay_url` before browser navigation. #### 0.1.14 * Fixed Common Cashier response handling to use the production `pay_url` field for the hosted cashier address. * Added safe diagnostic logging when the cashier URL is missing or fails redirect validation. #### 0.1.13 * Switched payment creation to GlobePay Common Cashier so GlobePay can present multiple merchant-enabled payment methods in the hosted cashier. * Restricted the Common Cashier flow to the documented JPY currency until GlobePay confirms CNY support for this API. #### 0.1.12 * Added the required signed Hosted Checkout redirect parameters (`time`, `nonce_str`,` sign`, and `redirect`). * Added the WooCommerce order-received URL so customers return to the store after payment. #### 0.1.11 * Added a merchant-selectable Hosted Checkout channel with `AlipayOnline` as the default; `Alipay+` and `UnionPay` remain available when enabled for the merchant account. * Accepted the GlobePay-operated `jp.globalfreepay.com` hosted cashier domain in the redirect allowlist. * Created a unique GlobePay partner order ID for every payment attempt so failed or closed attempts can be retried from the same WooCommerce order. #### 0.1.10 * Migrated legacy webhook replay records into the cleanup index during upgrade and removed expired entries. * Added compiled Chinese and Japanese MO files to the release package. #### 0.1.9 * Reject refund responses unless GlobePay returns the documented successful result state. * Compare notification amounts with the current WooCommerce order total, including after an order edit. * Hide the gateway for currencies other than JPY and CNY. * Added cleanup scheduling for expired webhook replay records and declared Checkout Blocks incompatibility. * Replaced custom translation markers with WordPress gettext markers and added Chinese and Japanese PO translations. #### 0.1.8 * Replaced the hard-coded runtime translation catalog with standard WordPress gettext loading. * Corrected the documented company names: Japan GlobePay Co., Ltd. / 日本環球支付 株式会社 / 日本环球支付株式会社. * Updated the compatibility declaration to WordPress 7.0 after testing on WordPress 7.0.4. #### 0.1.7 * Fixed the settings-save regression that cleared a stored Credential Code when the masked field was left blank. * Added regression coverage for credential preservation. #### 0.1.6 * Prevented saved Credential Codes from being cleared or rendered in admin page source. * Removed the single-option Environment selector while retaining Production-only runtime behavior. * Added active runtime requirement checks, translation loading, and functional WooCommerce API/debug logging. * Generated distinct refund request IDs for separate same-amount refunds. * Avoided emitting an undocumented callback error enum; failed notifications return a non-success HTTP response so GlobePay can retry. #### 0.1.5 * Fixed payment notification order lookup for both legacy WooCommerce storage and HPOS. * Added notification freshness and cross-order signature replay protection. * Required server-side Payment Query confirmation of `PAY_SUCCESS`, transaction ID, amount, and currency before payment completion. #### 0.1.4 * Fixed CNY amount handling to support amounts with up to two decimal places. * Unified CNY minor-unit conversion for payment creation, webhook comparison, and refunds. * Preserved JPY integer validation and added regression coverage for both currencies. #### 0.1.3 * Removed the obsolete environment-selection instruction from installation. * Added exact integer base-unit conversion for payment and refund amounts. * Added JPY/CNY amount regression coverage. #### 0.1.2 * Added the confirmed GlobePay Privacy Policy URL. * Removed the unconfirmed Sandbox option from new settings. * Confirmed the success-only notification semantics documented by GlobePay without inventing a callback status field. * Corrected the Hosted Checkout channel value to the documented `UnionPay` value. #### 0.1.1 * Prepared a WordPress.org Release Candidate with production-only packaging requirements. * Added accurate External Services and Privacy disclosures. * Hardened non-2xx API response handling and hosted-checkout redirect validation. * Added an explicit signature-based REST permission check for GlobePay notifications. * Updated plugin ownership metadata and release documentation. #### 0.1.0 * Initial GlobePay for WooCommerce payment gateway foundation. ## Meta * Version **0.1.24** * Last updated **2 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.5 or higher ** * Tested up to **7.1** * PHP version ** 8.1 or higher ** * Tags * [Hosted Checkout](https://wordpress.org/plugins/tags/hosted-checkout/)[payments](https://wordpress.org/plugins/tags/payments/) [woocommerce](https://wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://wordpress.org/plugins/globepay-for-woocommerce/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/globepay-for-woocommerce/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/globepay-for-woocommerce/reviews/) ## Contributors * [ globepay ](https://profiles.wordpress.org/globepay/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/globepay-for-woocommerce/)