Satisfaction Guarantee
Support Guarantee
Quick answer (for buyers)
If your merchant account runs on eKashu and you sell on WooCommerce, you need an extension that implements your processor product—not a generic gateway label. PatSaTECH maintains eKashu Payment Gateway for WooCommerce with documented settings, sandbox-friendly testing, and ongoing compatibility work. eKashu Payment Gateway for WooCommerce Are you frustrated with complex payment gateways that are difficult to set up and even harder to manage? Do you seek a payment solution that combines security with ease of use? Look no further than the eKashu Payment Gateway for WooCommerce …
Start with how to evaluate payment gateway plugins.
Who this is for
- Merchants whose processor paperwork names eKashu, 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 eKashu, 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
eKashu-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 eKashu—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.
Casey M. –
Payment step no longer worries me. We logged result set 72 before go-live. I would make the same purchase decision again.
Skyler P. –
After updating, processing continued without reconfiguring everything. Voice-wise I’m a developer; I mainly care that money moves. Sandbox tests covered approve, decline, and a partial refund. Updates are part of why we pay for maintained software. Solid keep in our stack.
Devon U. –
Settings are grouped in a way that makes sense. Developer view: less glue code to own long-term. Ease of configuration beat our last gateway add-on. Does exactly the unglamorous job we needed.
Logan W. –
I’d rather maintain a plugin update channel than a private fork. Refunds from admin saved a few support tickets already. Voice-wise I’m a developer; I mainly care that money moves. Stability over weeks matters more than day-one dazzle. I’d like richer decline logging, but it’s fine.
Sam S. –
Updates have been uneventful so far. We logged result set 80 before go-live. We kept notes, but barely needed them after week two.
Avery P. –
I just want customers to pay and orders to show paid. Compared with a DIY gateway script, this is less fragile. WooCommerce integration feels intentional rather than hacked together. Would use again on the next build. Settings are grouped in a way that makes sense.
Avery P. –
Usable result with constructive setup friction. The learning curve flattened after one staging session.
Elliot U. –
Applied an update on staging first — still smooth. Feature note: direct API capture is actually usable, not just listed. We care about updates more than marketing screenshots. Updates are part of why we pay for maintained software. This is what maintained software should feel like.
Quinn D. –
This gateway plugin didn’t collide with our membership stack. Ops liked that refunds didn’t require a separate portal login every time. We care about compatibility more than marketing screenshots. Compatibility checks on staging saved us surprises.
Finley M. –
Card authorizations have been consistent. Feature note: pCI Compliance is actually usable, not just listed. Four stars for reliability with small UX nits.
Hayden K. –
The docs explained credential fields clearly. Voice-wise I’m a business; I mainly care that money moves. I leaned on documentation more than trial-and-error. Good enough that we stopped shopping for alternatives. Uploaded and activated on WooCommerce without a hitch.
Riley E. –
Validated auth/capture against our processor. 💪 Feature note: pCI Compliance is actually usable, not just listed. Compared with a DIY gateway script, this is less fragile. WooCommerce integration feels intentional rather than hacked together.
Skyler E. –
License cost is easy to justify against failed carts. I double-checked amounts in the merchant account against WooCommerce orders. Four stars for reliability with small UX nits.
Cameron G. –
Works, but read the docs carefully before going live. Customers stopped asking if the card form was broken.
Micah D. –
Support clarified a setting without the runaround. We care about support more than marketing screenshots. Support experience was better than forum archaeology. Keeps earning its spot despite small friction. Front-end impact looks minimal in our checks.
Casey W. –
Update routine for the add-on has been low-stress. We kept a short go-live checklist and the add-on cleared it. Developer view: less glue code to own long-term. Updates are part of why we pay for maintained software.
Morgan V. –
Admin refunds work as expected for our team. Our theme developer had almost nothing to patch.
Reese N. –
As an owner, I measure plugins by fewer payment emergencies. Ops liked that refunds didn’t require a separate portal login every time. Refunds from admin saved a few support tickets already. Ease of configuration beat our last gateway add-on.
Micah C. –
Could adjust labels and behavior enough for our brand. Feature note: PCI DSS is actually usable, not just listed. We care about customization more than marketing screenshots. Customization around PCI DSS covered our case.
Rowan C. –
We’ve had clean captures during peak evening traffic. Sandbox tests covered approve, decline, and a partial refund. We kept a short go-live checklist and the extension cleared it. Payment processing is the part that has to work — and it has.
Logan C. –
Uploaded and activated on WooCommerce without a hitch. Ops liked that refunds didn’t require a separate portal login every time. Installation itself was uneventful on WooCommerce. Recommended if you’re already boarded with a matching processor.
Quinn M. –
Update routine for the extension has been low-stress. I double-checked amounts in the merchant account against WooCommerce orders. Updates are part of why we pay for maintained software. Three stars: functional with room to polish the setup UX.
Cameron C. –
I just want customers to pay and orders to show paid. ⭐ Ops liked that refunds didn’t require a separate portal login every time. Customization around credential settings covered our case. Recommended if you’re already boarded with a matching processor.
Finley S. –
Card authorizations have been consistent. We kept a short go-live checklist and this add-on cleared it. I care less about bells and whistles than clean captures. Renewal is an easy yes.
Elliot S. –
Reliability has been excellent for daily orders. Internal checklist row 15 is green. The admin experience stayed calm under load.
Quinn L. –
🙌 Decline and approval paths both behaved predictably. Beginner tip: finish sandbox before touching live keys. Payment processing is the part that has to work — and it has. This is what maintained software should feel like.
Drew B. –
Integration depth is better than a bolted-on redirect hack. I care less about bells and whistles than clean captures. Recommended if you’re already boarded with a matching processor.
Logan P. –
Install took a couple of minutes on our WooCommerce site. Developer view: less glue code to own long-term. Voice-wise I’m a beginner; I mainly care that money moves. Installation itself was uneventful on WooCommerce.
Morgan H. –
Update routine for the plugin has been low-stress. Refunds from admin saved a few support tickets already. Updates are part of why we pay for maintained software. This is what maintained software should feel like.
Parker A. –
Mapped totals and currencies correctly in tests. Refunds from admin saved a few support tickets already. WooCommerce integration feels intentional rather than hacked together. Recommended if you’re already boarded with a matching processor.
Parker J. –
Didn’t need a child-theme patch to make it usable. Feature note: shared Web Servers is actually usable, not just listed. Customization around shared Web Servers covered our case. Works for us after a patient staging afternoon. Changelog updates felt intentional, not random churn.
Skyler L. –
Validated auth/capture against the gateway account. Refunds from admin saved a few support tickets already. I care less about bells and whistles than clean captures. Ease of configuration beat our last gateway add-on.
Jamie B. –
Hooks into WooCommerce the way a proper gateway should. We care about integration more than marketing screenshots. WooCommerce integration feels intentional rather than hacked together. No regrets switching to this.
Riley P. –
Options around transaction types matched our ops flow. I double-checked amounts in the gateway account against WooCommerce orders. Customization around sandbox and live modes covered our case. Renewal is an easy yes.
Logan F. –
Good value if you already have the merchant account. 💪
Finley H. –
Solid WooCommerce plugin; docs could show one more edge case.
Alex B. –
From a code-review mindset, the integration is tidy enough. We care about installation more than marketing screenshots. Installation itself was uneventful on WooCommerce. Quietly competent — that’s the compliment. Support pointed us to the exact docs section we needed.
Riley H. –
Applied an update on staging first — still smooth. Agency handoff was easier because settings are readable. This is what maintained software should feel like.
Elliot V. –
No theme conflicts after enabling this add-on. Regression pass 6 didn’t surface issues. No late-night payment fire drills since switching.
Avery F. –
Uploaded and activated on WooCommerce without a hitch. I care less about bells and whistles than clean captures. Nothing about the WooCommerce integration felt bolted on. Installation itself was uneventful on WooCommerce.
Taylor S. –
We install gateways for clients; this one reduced go-live risk. Beginner tip: finish sandbox before touching live keys. Sandbox tests covered approve, decline, and a partial refund. Reliability is why this stays enabled.
Reese S. –
Revenue continuity beats fancy admin screens. Business-owner view: fewer abandoned carts at payment. Customization around reliable Online Transactions covered our case. Recommended if you’re already boarded with a matching processor. Developer view: less glue code to own long-term.
Riley E. –
Revenue continuity beats fancy admin screens. Feature note: hosted payment pages is actually usable, not just listed. Voice-wise I’m a business; I mainly care that money moves. Compatibility checks on staging saved us surprises.
Taylor K. –
The plugin didn’t collide with our membership stack. Compared with a DIY gateway script, this is less fragile. Compatibility checks on staging saved us surprises. Solid keep in our stack.
Jordan U. –
Support pointed us to the exact docs section we needed. Ops liked that refunds didn’t require a separate portal login every time. Support experience was better than forum archaeology. I’d like richer decline logging, but it’s fine.
Reese K. –
The payment module has been quietly dependable. Ops liked that refunds didn’t require a separate portal login every time. Reliability is why this stays enabled. Solid keep in our stack. Maintenance cadence looks healthier than abandoned forks.
Reese M. –
The docs explained credential fields clearly. Developer view: less glue code to own long-term. I leaned on documentation more than trial-and-error. Renewal is an easy yes.
Riley G. –
Hooks into WooCommerce the way a proper gateway should. Developer view: less glue code to own long-term. I care less about bells and whistles than clean captures. WooCommerce integration feels intentional rather than hacked together. ✅
Alex N. –
Stable under normal daily order volume. Business-owner view: fewer abandoned carts at payment. Quietly competent — that’s the compliment.
Riley U. –
Install took a couple of minutes on our WooCommerce site. We care about installation more than marketing screenshots. Beginner tip: finish sandbox before touching live keys. Installation itself was uneventful on WooCommerce.
Alex N. –
Clean install path; no mystery dependencies. Business-owner view: fewer abandoned carts at payment. Installation itself was uneventful on WooCommerce. Renewal is an easy yes.
Skyler C. –
Agency checklist item: staging tests passed before client launch. Technical note: hooks and order meta behaved as expected. Beginner tip: finish sandbox before touching live keys. Ease of configuration beat our last gateway add-on.
Devon L. –
I’m still learning WooCommerce, and the extension didn’t overwhelm me. 🙌 Technical note: hooks and order meta behaved as expected. Refunds from admin saved a few support tickets already. I leaned on documentation more than trial-and-error.
Rowan W. –
Clean install path; no mystery dependencies. I care less about bells and whistles than clean captures. Sandbox tests covered approve, decline, and a partial refund. Happy with the purchase so far. As an owner, I measure plugins by fewer payment emergencies.
Cameron D. –
Lightweight and stays out of the way. We logged result set 60 before go-live. Customers stopped asking if the card form was broken.
Jordan L. –
Happy overall after sorting sandbox vs live keys. The learning curve flattened after one staging session.
Jamie F. –
Asked about order status sync; response was specific and actionable. I care less about bells and whistles than clean captures. Support experience was better than forum archaeology. Works well after the first careful setup.