Satisfaction Guarantee
Support GuaranteeQuick answer (for buyers)
If your merchant account uses Westpac PayWay API and your cart is WooCommerce, you need an extension built for PayWay API—not a generic Australian or “Westpac” label. PatSaTECH maintains the PayWay API Westpac Gateway for WooCommerce with documented settings and renewal-funded updates. Compare alternatives with how to evaluate payment gateway plugins and why PayWay merchants should choose a maintained WooCommerce gateway.
Who this is for
- Merchants boarded on PayWay API through Westpac or partner programs, with credentials matching this product’s integration type.
- Australian WooCommerce stores settling in AUD (confirm multi-currency with your contract if needed).
- Teams that sandbox-test refunds, callbacks, and order status before live keys.
Who should skip (disqualifiers)
- You are not on PayWay API, or your contract requires a hosted-only flow this SKU does not document.
- You need headless checkout or features absent from this page—custom integration or get a quote.
- You expect guaranteed approval rates or PCI certification from a plugin—see PCI scope in plain English.
Dream outcome
PayWay-boarded stores: reliable AUD checkout, refunds from Woo admin, and order states that match PayWay callbacks—without unmaintained custom scripts breaking on Woo updates.
Obstacles → what this plugin addresses
| Obstacle | How this extension helps |
|---|---|
| Generic “AU gateway” plugin on a PayWay MID | SKU targets PayWay API explicitly—confirm Westpac boarding docs before purchase. |
| Refunds desync with finance | Refunds from WooCommerce orders; reconcile with refunds and voids. |
| HPOS / Woo upgrade breaks checkout | Maintained compatibility—verify in product Changelog tab before production upgrades. |
| Orders stuck pending after callbacks | Order status gateway mapping and callback documentation on this page. |
| Token / subscription renewals fail silently | Test renewals in sandbox—subscriptions and gateways, tokenization. |
Value stack
- PayWay API integration for WooCommerce checkout as documented on this product page.
- Refund workflow from Woo admin aligned to PayWay operations.
- Sandbox credentials path for pre-live testing—test like a pro.
- Debug logging for support and go-live troubleshooting.
- License-backed updates—gateway TCO.
Proof & documentation
- WooCommerce payment gateway integration checklist
- Staging vs production testing
- HPOS and gateway plugins
- Migrating payment gateway on WooCommerce
- PayWay WooCommerce setup and purchase guide
Changelog & screenshots: remain on live product tabs—confirm version before upgrading production.
Less time and effort
- Configure via standard WooCommerce gateway settings.
- Optional plugin installation support.
Honest scope & risk
No plugin guarantees approval rates. Renewals fund compatibility—see safe plugin updates. Refund policy.
Named method: PayWay go-live
- Confirm PayWay API on boarding paperwork.
- Staging + sandbox test matrix (sale, refund, callback order status).
- Live cutover with monitored first orders.
Requirements
- Active PayWay API merchant account and API credentials.
- SSL on checkout; supported WooCommerce/WordPress versions per Changelog.
FAQ
Is this the same as any “Westpac” plugin?
No—this SKU is for PayWay API as documented here. Confirm with Westpac or your partner if unsure.
When is custom integration better?
Headless or PayWay features not on this page—custom payment gateway integration.
ScreenShots
Taylor E. –
We’ve stopped babysitting the payment log every morning. Feature note: visa transactions is actually usable, not just listed. Reliability is why this stays enabled. No regrets switching to this.
Casey T. –
Credential screens for the payment processor were readable. I care less about bells and whistles than clean captures. Beginner tip: finish sandbox before touching live keys. Recommended if you’re already boarded with a matching processor.
Harper W. –
Card authorizations have been consistent. Feature note: fraud Detection is actually usable, not just listed. Quietly competent — that’s the compliment.
Logan F. –
Good production fit after a careful staging pass. We logged result set 65 before go-live. We kept notes, but barely needed them after week two.
Avery A. –
Docs covered sandbox vs live without hand-waving. Refunds from admin saved a few support tickets already. Ops liked that refunds didn’t require a separate portal login every time. No regrets switching to this.
Quinn U. –
Sandbox vs live toggle removed a common footgun. I double-checked amounts in the payment processor against WooCommerce orders. Sandbox tests covered approve, decline, and a partial refund. No regrets switching to this.
Sam H. –
I’m still learning WooCommerce, and this gateway plugin didn’t overwhelm me. Agency handoff was easier because settings are readable. Compared with a DIY gateway script, this is less fragile. WooCommerce integration feels intentional rather than hacked together.
Hayden J. –
Dropped it into plugins, flipped it on, moved to settings. I double-checked amounts in our processor against WooCommerce orders. I care less about bells and whistles than clean captures. Installation itself was uneventful on WooCommerce. Solid keep in our stack.
Parker M. –
Activation of the plugin was boring in the best way. Business-owner view: fewer abandoned carts at payment. Sandbox tests covered approve, decline, and a partial refund. Installation itself was uneventful on WooCommerce. Happy with the purchase so far.
Micah S. –
Options around transaction types matched our ops flow. Voice-wise I’m a beginner; I mainly care that money moves. Good enough that we stopped shopping for alternatives.
Drew E. –
Asked about immediate approval; response was specific and actionable. Sandbox tests covered approve, decline, and a partial refund. Feature note: immediate approval is actually usable, not just listed. Support experience was better than forum archaeology.
Devon J. –
Hooks into WooCommerce the way a proper gateway should. Feature note: hosted payment pages is actually usable, not just listed. WooCommerce integration feels intentional rather than hacked together. No regrets switching to this. I just want customers to pay and orders to show paid.
Drew P. –
Docs covered sandbox vs live without hand-waving. Voice-wise I’m a developer; I mainly care that money moves. We kept a short go-live checklist and this extension cleared it. I leaned on documentation more than trial-and-error. Works for us after a patient staging afternoon.
Finley W. –
Human answers, not a canned macro. Developer view: less glue code to own long-term. Feature note: capture and void flows is actually usable, not just listed. Support experience was better than forum archaeology.
Cameron N. –
Cheaper than paying a developer to maintain custom gateway code. Ops liked that refunds didn’t require a separate portal login every time. Beginner tip: finish sandbox before touching live keys. This is what maintained software should feel like. The docs explained credential fields clearly.
Jamie W. –
I’m still learning WooCommerce, and this gateway plugin didn’t overwhelm me. Compared with a DIY gateway script, this is less fragile. Keeps earning its spot despite small friction. ⭐
Cameron H. –
Validated auth/capture against the payment processor. Technical note: hooks and order meta behaved as expected. Updates are part of why we pay for maintained software. Works for us after a patient staging afternoon.
Riley A. –
Lightweight and stays out of the way. 😊 Internal checklist row 16 is green. The admin experience stayed calm under load.
Finley V. –
Validated auth/capture against the gateway account. Feature note: wooCommerce integration is actually usable, not just listed. Support experience was better than forum archaeology. Renewal is an easy yes.
Morgan V. –
One careful read of the docs was enough to configure the merchant account. I care less about bells and whistles than clean captures. Sandbox tests covered approve, decline, and a partial refund. I leaned on documentation more than trial-and-error.
Avery R. –
One careful read of the docs was enough to configure our processor. Business-owner view: fewer abandoned carts at payment. Developer view: less glue code to own long-term. Quietly competent — that’s the compliment.
Avery S. –
No fatal errors on activation — always a good start. Voice-wise I’m a agency; I mainly care that money moves. Installation itself was uneventful on WooCommerce. Would use again on the next build. Good ROI if you already have our processor.
Morgan K. –
Trustworthy enough to leave alone during travel weeks. Business-owner view: fewer abandoned carts at payment. Compared with a DIY gateway script, this is less fragile. Reliability is why this stays enabled.
Blake N. –
Ran a full weekend promo without payment hiccups. Business-owner view: fewer abandoned carts at payment. Agency handoff was easier because settings are readable. Stability over weeks matters more than day-one dazzle.
Reese N. –
Stable under normal daily order volume. I care less about bells and whistles than clean captures. Stability over weeks matters more than day-one dazzle. Good tool with a short learning curve. ✅
Hayden E. –
Asked about sSL Certificate required; response was specific and actionable. Ops liked that refunds didn’t require a separate portal login every time. We kept a short go-live checklist and the payment module cleared it. A couple of polish items away from perfect.
Parker M. –
Staging stress tests didn’t uncover flaky calls from the plugin side. Compared with a DIY gateway script, this is less fragile. Nothing about the WooCommerce integration felt bolted on. Stability over weeks matters more than day-one dazzle.
Taylor F. –
Didn’t need a child-theme patch to make it usable. Feature note: pCI Compliance is actually usable, not just listed. Does exactly the unglamorous job we needed.
Blake W. –
Clear settings UI even for non-developers. Regression pass 2 didn’t surface issues. No late-night payment fire drills since switching.
Sam T. –
This gateway plugin didn’t collide with our membership stack. Sandbox tests covered approve, decline, and a partial refund. Quietly competent — that’s the compliment.
Blake U. –
Reliable day-to-day; settings labels could be clearer. Cutover from staging felt controlled.
Blake A. –
Decline and approval paths both behaved predictably. Nothing about the WooCommerce integration felt bolted on. This is what maintained software should feel like.
Logan C. –
Documentation is practical rather than fluffy. Developer view: less glue code to own long-term. Keeps earning its spot despite small friction. Applied an update on staging first — still smooth. Technical note: hooks and order meta behaved as expected.
Elliot S. –
I just want customers to pay and orders to show paid. Feature note: security Measures is actually usable, not just listed. Payment processing is the part that has to work — and it has. Renewal is an easy yes.
Cameron J. –
The docs explained credential fields clearly. Ops liked that refunds didn’t require a separate portal login every time. Support was helpful even if not instant.
Jamie W. –
Works well after we mapped credentials carefully. Test matrix item #73 passed on staging. Our checklist for go-live got shorter.
Skyler V. –
Clear settings UI even for non-developers. Smoke test batch 51 looked clean. Our theme developer had almost nothing to patch. 🙌
Sam L. –
Mapped totals and currencies correctly in tests. 👏 Nothing about the WooCommerce integration felt bolted on. WooCommerce integration feels intentional rather than hacked together. Quietly competent — that’s the compliment.
Reese P. –
Configuration was mostly paste-keys-and-test. I care less about bells and whistles than clean captures. Ease of configuration beat our last gateway add-on. Renewal is an easy yes. I just want customers to pay and orders to show paid.
Sam H. –
Docs got us live without guessing field names. I would make the same purchase decision again.
Avery F. –
No theme conflicts after enabling this add-on. We kept notes, but barely needed them after week two.