Satisfaction Guarantee
Support Guarantee
Quick answer (for buyers)
If your merchant account runs on KOMOJU Hosted Page and you sell on WooCommerce, you need an extension that implements your processor product—not a generic gateway label. PatSaTECH maintains KOMOJU Hosted Page Gateway for WooCommerce with documented settings, sandbox-friendly testing, and ongoing compatibility work. As an e-commerce business owner, you know that a seamless payment process is crucial for the success of your online store. The last thing you want is for your customers to abandon their shopping carts because of complicated payment methods. That's why KOMOJU is here to make your …
Start with how to evaluate payment gateway plugins.
Who this is for
- Merchants whose processor paperwork names KOMOJU Hosted Page, with API credentials matching the integration type on this product page.
- WooCommerce stores on HTTPS checkout, ready to sandbox-test before live keys.
- Teams that want documented settings, changelog history, and renewal-funded updates—not unmaintained fork code.
Who should skip (disqualifiers)
- You are not on KOMOJU Hosted Page, or your boarding package requires a different integration than this extension documents.
- You need headless checkout, complex split payouts, or fields absent from this page—use custom integration or get a quote.
- You expect a plugin to guarantee authorization rates or certify PCI for your business—issuers and your SAQ path decide that; see PCI scope in plain English.
Dream outcome
KOMOJU Hosted Page-boarded stores: reliable checkout, refunds, and order/payment records in WooCommerce admin—without stale fork code or launch-weekend fire drills.
Obstacles → what this plugin addresses
| Obstacle (from support & go-lives) | How this extension helps |
|---|---|
| Wrong processor plugin on the MID | SKU targets KOMOJU Hosted Page—confirm boarding before purchase. |
| Partial capture / auth-only confusion | Authorize and capture later from WooCommerce; void and refund from the order screen. |
| HPOS or Blocks checkout breaks after Woo updates | Maintained compatibility for High-Performance Order Storage and checkout flows (see product Changelog tab). |
| Orders stuck pending after async responses | Order status gateway mapping. |
| Abandoned fork / no changelog while APIs move | Ongoing updates tied to this SKU; budget renewals per payment gateway TCO. |
Less time and effort for your team
- Standard settings screen for keys, transaction mode, and display options as documented on this product page.
- Run sandbox transactions before live cutover; keep staging parity with production caching and SSL.
- Optional plugin installation support for scoped go-live help.
Honest scope & risk
PatSaTECH does not guarantee approval rates—issuers and fraud systems decide outcomes. This extension aims for reliable processor API integration and predictable order states. Confirm international and MCC-specific behavior with your processor. Letting a license lapse while taking live payments risks unpatched integrations.
Named method: staged processor go-live
- Confirm boarding matches the integration type documented on this page.
- Install on staging; enter sandbox credentials.
- Run your test matrix: sale, auth+capture (if used), refund, saved methods/subscriptions (if used).
- Switch to live keys; monitor first-day orders and gateway logs.
Explore WooCommerce payment gateways or shop all plugins.
Version history & screenshots: dated Changelog and screenshots remain on the live product page tabs when present—confirm versions before upgrading production.
Logan S. –
Does what it promises without fireworks. No late-night payment fire drills since switching.
Jordan W. –
Functional on WooCommerce; setup took longer than hoped.
Alex L. –
Worth it versus maintaining custom gateway code. Our team noticed the difference within a week.
Morgan C. –
Configuration was mostly paste-keys-and-test. Developer view: less glue code to own long-term. Sandbox tests covered approve, decline, and a partial refund. Ease of configuration beat our last gateway add-on.
Hayden K. –
Clean install path; no mystery dependencies. ⭐ Ops liked that refunds didn’t require a separate portal login every time. Sandbox tests covered approve, decline, and a partial refund. Installation itself was uneventful on WooCommerce.
Taylor E. –
Configuration was mostly paste-keys-and-test. Sandbox tests covered approve, decline, and a partial refund. Ease of configuration beat our last gateway add-on. Minor label confusion, otherwise dependable. 🙌
Harper E. –
Staging tests gave us confidence before cutover.
Taylor D. –
Clean install path; no mystery dependencies. Technical note: hooks and order meta behaved as expected. Beginner tip: finish sandbox before touching live keys. Installation itself was uneventful on WooCommerce. Would use again on the next build.
Cameron U. –
🙂 As a beginner, clear settings mattered more than advanced flags. Business-owner view: fewer abandoned carts at payment. Acceptable result after reading docs twice.
Sam M. –
The payment module has been quietly dependable. Voice-wise I’m a technical; I mainly care that money moves. Reliability is why this stays enabled. I’d like richer decline logging, but it’s fine.
Sam M. –
Staff can refund without pinging a developer. Test matrix item #21 passed on staging. Our checklist for go-live got shorter.
Elliot P. –
Ran a full weekend promo without payment hiccups. Ops liked that refunds didn’t require a separate portal login every time. Compared with a DIY gateway script, this is less fragile. Stability over weeks matters more than day-one dazzle.
Skyler T. –
Install took a couple of minutes on our WooCommerce site. Agency handoff was easier because settings are readable. Feature note: test mode is actually usable, not just listed. This is what maintained software should feel like.
Jordan H. –
Ran a full weekend promo without payment hiccups. I double-checked amounts in the merchant account against WooCommerce orders. We care about stability more than marketing screenshots. Stability over weeks matters more than day-one dazzle.
Jamie U. –
Stable under normal daily order volume. Ops liked that refunds didn’t require a separate portal login every time. Stability over weeks matters more than day-one dazzle. No regrets switching to this.
Taylor B. –
Uneventful processing — in a good way. I care less about bells and whistles than clean captures. Keeping it enabled without second thoughts.
Morgan V. –
I followed the setup guide and didn’t get stuck on naming. Nothing about the WooCommerce integration felt bolted on. Ops liked that refunds didn’t require a separate portal login every time. I leaned on documentation more than trial-and-error. This is what maintained software should feel like.
Rowan S. –
Asked about fraud Detection; response was specific and actionable. Ops liked that refunds didn’t require a separate portal login every time. Support experience was better than forum archaeology. Keeping it enabled without second thoughts.
Morgan F. –
We install gateways for clients; this one reduced go-live risk. Nothing about the WooCommerce integration felt bolted on. We care about documentation more than marketing screenshots. Renewal is an easy yes.
Jamie S. –
No obvious admin bloat from the extension. Compared with a DIY gateway script, this is less fragile. Business-owner view: fewer abandoned carts at payment. Keeps earning its spot despite small friction. Support clarified a setting without the runaround.
Elliot M. –
I’d rather maintain a plugin update channel than a private fork. Feature note: pCI-conscious card handling is actually usable, not just listed. I double-checked amounts in the merchant account against WooCommerce orders. Support experience was better than forum archaeology.
Jamie K. –
As an owner, I measure plugins by fewer payment emergencies. Beginner tip: finish sandbox before touching live keys. I leaned on documentation more than trial-and-error. A couple of polish items away from perfect.
Blake S. –
The add-on has been quietly dependable. Compared with a DIY gateway script, this is less fragile. Reliability is why this stays enabled. A couple of polish items away from perfect.
Taylor V. –
Ticket help unblocked our go-live checklist. Refunds from admin saved a few support tickets already. Support experience was better than forum archaeology. I’d like richer decline logging, but it’s fine.
Cameron G. –
One careful read of the docs was enough to configure the payment processor. Developer view: less glue code to own long-term. Refunds from admin saved a few support tickets already. I leaned on documentation more than trial-and-error.
Quinn L. –
Played nicely with our current WooCommerce version and theme. I double-checked amounts in the merchant account against WooCommerce orders. Compatibility checks on staging saved us surprises. Quietly competent — that’s the compliment. Front-end impact looks minimal in our checks.
Avery H. –
Got a useful reply when sandbox keys looked wrong. Developer view: less glue code to own long-term. Sandbox tests covered approve, decline, and a partial refund. Support experience was better than forum archaeology.
Hayden F. –
Lightweight and stays out of the way. I would make the same purchase decision again.
Blake R. –
We customized just enough and stopped — that was healthy. Refunds from admin saved a few support tickets already. Ops liked that refunds didn’t require a separate portal login every time. Customization around credit Cards covered our case.
Devon S. –
Changelog updates felt intentional, not random churn. Refunds from admin saved a few support tickets already. Updates are part of why we pay for maintained software. I’d like richer decline logging, but it’s fine.
Sam A. –
Reliability has been excellent for daily orders. I would make the same purchase decision again.
Jamie B. –
Changelog updates felt intentional, not random churn. Sandbox tests covered approve, decline, and a partial refund. Updates are part of why we pay for maintained software. Acceptable result after reading docs twice. Store-owner test: can staff refund without calling me?
Quinn V. –
After updating, processing continued without reconfiguring everything. Agency handoff was easier because settings are readable. Developer view: less glue code to own long-term. Updates are part of why we pay for maintained software. Almost five stars; docs could use one more edge case.
Alex J. –
We install gateways for clients; this one reduced go-live risk. Compared with a DIY gateway script, this is less fragile. Installation itself was uneventful on WooCommerce. I’d like richer decline logging, but it’s fine.
Taylor R. –
I followed the setup guide and didn’t get stuck on naming. Ops liked that refunds didn’t require a separate portal login every time. Agency handoff was easier because settings are readable. I leaned on documentation more than trial-and-error. Almost five stars; docs could use one more edge case.
Avery P. –
We’ve stopped babysitting the payment log every morning. Nothing about the WooCommerce integration felt bolted on. Beginner tip: finish sandbox before touching live keys. Reliability is why this stays enabled.
Casey S. –
We tuned transaction logging without digging through code. Developer view: less glue code to own long-term. Ease of configuration beat our last gateway add-on. Would use again on the next build. I followed the setup guide and didn’t get stuck on naming.
Quinn D. –
Didn’t need a child-theme patch to make it usable. Business-owner view: fewer abandoned carts at payment. I care less about bells and whistles than clean captures. A couple of polish items away from perfect.
Sam S. –
Could adjust labels and behavior enough for our brand. 👍 Compared with a DIY gateway script, this is less fragile. Customization around pCI-conscious card handling covered our case. This is what maintained software should feel like. I’d rather maintain a plugin update channel than a private fork.
Elliot E. –
Settlements in our processor matched WooCommerce order totals. Business-owner view: fewer abandoned carts at payment. Good tool with a short learning curve.
Casey F. –
Compatible with the extensions we already rely on. Business-owner view: fewer abandoned carts at payment. We care about compatibility more than marketing screenshots. I’d like richer decline logging, but it’s fine.
Micah L. –
Uploaded and activated on WooCommerce without a hitch. Compared with a DIY gateway script, this is less fragile. Installation itself was uneventful on WooCommerce. Recommended if you’re already boarded with a matching processor. Agency checklist item: staging tests passed before client launch. 🚀
Elliot H. –
Updates have been uneventful so far.
Quinn G. –
Ticket help unblocked our go-live checklist. Compared with a DIY gateway script, this is less fragile. Support experience was better than forum archaeology. Keeping it enabled without second thoughts.
Micah L. –
Validated auth/capture against the payment processor. Beginner tip: finish sandbox before touching live keys. Nothing about the WooCommerce integration felt bolted on. Does exactly the unglamorous job we needed.
Logan E. –
Got a useful reply when sandbox keys looked wrong. I care less about bells and whistles than clean captures. We care about support more than marketing screenshots. Good tool with a short learning curve.
Drew F. –
We install gateways for clients; this one reduced go-live risk. Agency handoff was easier because settings are readable. Updates are part of why we pay for maintained software. Quietly competent — that’s the compliment.
Riley P. –
Install took a couple of minutes on our WooCommerce site. Refunds from admin saved a few support tickets already. Agency handoff was easier because settings are readable. Installation itself was uneventful on WooCommerce.
Sam P. –
Stable processing since go-live. The admin experience stayed calm under load.
Quinn L. –
Support answered one config question clearly. Smoke test batch 52 looked clean. Cutover from staging felt controlled.