Satisfaction Guarantee
Support Guarantee
Quick answer (for buyers)
If your merchant account runs on PayWay API (Westpac) and you sell on Gravity Forms, you need an extension that implements your processor product—not a generic gateway label. PatSaTECH maintains PayWay API (Westpac) Gateway for Gravity Forms with documented settings, sandbox-friendly testing, and ongoing compatibility work. PayWay API Gateway for Gravity Forms Enhance your WordPress forms with the PayWay API Gateway for Gravity Forms , a cutting-edge credit card processing solution developed by Westpac, a leading financial services provider. Seamlessly integrate secure and efficient payment processi…
Start with how to evaluate payment gateway plugins.
Who this is for
- Merchants whose processor paperwork names PayWay API (Westpac), with API credentials matching the integration type on this product page.
- Gravity Forms 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 PayWay API (Westpac), 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
PayWay API (Westpac)-boarded stores: reliable checkout, refunds, and order/payment records in Gravity Forms admin—without stale fork code or launch-weekend fire drills.
Obstacles → what this plugin addresses
| Obstacle (from support & go-lives) | How this extension helps |
|---|---|
| Custom snippet breaks after PHP or GF updates | Maintained add-on with entry transaction IDs and refund paths finance understands. |
| Wrong NMI/processor integration type | Confirm your ISO paperwork matches PayWay API (Westpac) on this product page. |
| Sandbox vs live key mix-ups | Documented settings screen; test matrix before live cutover. |
Proof & documentation
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.
Browse Gravity Forms payment add-ons.
Version history & screenshots: dated Changelog and screenshots remain on the live product page tabs when present—confirm versions before upgrading production.
Skyler S. –
We customized just enough and stopped — that was healthy. Developer view: less glue code to own long-term. Feature note: credential settings is actually usable, not just listed. Customization around credential settings covered our case.
Jamie T. –
Activation of the payment module was boring in the best way. Nothing about the Gravity Forms integration felt bolted on. Developer view: less glue code to own long-term. Installation itself was uneventful on Gravity Forms.
Taylor L. –
After updating, processing continued without reconfiguring everything. We kept a short go-live checklist and the payment module cleared it. Updates are part of why we pay for maintained software. A couple of polish items away from perfect.
Micah C. –
Validated auth/capture against the payment processor. Agency handoff was easier because settings are readable. Customization around secure Storage covered our case. Good tool with a short learning curve.
Avery E. –
The docs explained credential fields clearly. Voice-wise I’m a technical; I mainly care that money moves. I leaned on documentation more than trial-and-error. Solid keep in our stack.
Sam P. –
Four stars — support helpful, not instant. Internal checklist row 64 is green. It stays out of the way until you need refunds.
Parker B. –
Theme styling around the form payment still looked coherent. I double-checked amounts in our processor against Gravity Forms orders. Voice-wise I’m a business; I mainly care that money moves. Compatibility checks on staging saved us surprises. Constructive note: clearer validation on bad keys would help.
Micah J. –
Works well after we mapped credentials carefully. The learning curve flattened after one staging session.
Jordan S. –
Weeks later, form payment still behaves the same. Developer view: less glue code to own long-term. I care less about bells and whistles than clean captures. Stability over weeks matters more than day-one dazzle.
Micah G. –
Dropped it into plugins, flipped it on, moved to settings. Refunds from admin saved a few support tickets already. Recommended if you’re already boarded with a matching processor.
Reese T. –
I’m still learning Gravity Forms, and this plugin didn’t overwhelm me. Feature note: wordPress Plugin is actually usable, not just listed. Nothing about the Gravity Forms integration felt bolted on. Recommended if you’re already boarded with a matching processor. As a beginner, clear settings mattered more than advanced flags.
Skyler E. –
Stable under normal daily order volume. Sandbox tests covered approve, decline, and a partial refund. Stability over weeks matters more than day-one dazzle. Almost five stars; docs could use one more edge case.
Rowan K. –
Ran a full weekend promo without payment hiccups. I care less about bells and whistles than clean captures. Voice-wise I’m a beginner; I mainly care that money moves. Stability over weeks matters more than day-one dazzle.
Casey U. –
Happy overall after sorting sandbox vs live keys. We logged result set 65 before go-live. Customers stopped asking if the card form was broken.
Quinn F. –
Day-to-day reliability is what sold me. We kept a short go-live checklist and this plugin cleared it. Reliability is why this stays enabled. Solid keep in our stack. 🙌
Reese D. –
Live traffic week one was uneventful — in a good way. Internal checklist row 8 is green. The admin experience stayed calm under load.
Skyler V. –
Clean install path; no mystery dependencies. Voice-wise I’m a developer; I mainly care that money moves. This is what maintained software should feel like.
Alex N. –
Asked about sandbox and live modes; response was specific and actionable. We care about support more than marketing screenshots. Support experience was better than forum archaeology. Happy with the purchase so far.
Micah M. –
Human answers, not a canned macro. Compared with a DIY gateway script, this is less fragile. Business-owner view: fewer abandoned carts at payment. Does exactly the unglamorous job we needed.
Cameron T. –
Options around transaction types matched our ops flow. Business-owner view: fewer abandoned carts at payment. Gets there, but the first hour asks for patience.
Finley C. –
Consistent results across desktop and phone orders. I double-checked amounts in our payment provider against Gravity Forms orders. Would use again on the next build.
Devon E. –
Live traffic week one was uneventful — in a good way. Our checklist for go-live got shorter.
Devon C. –
Acceptable once configured; onboarding was the ding. 🙂
Blake S. –
We’ve had clean captures during peak evening traffic. Technical note: hooks and order meta behaved as expected. I care less about bells and whistles than clean captures. Payment processing is the part that has to work — and it has.
Rowan L. –
😊 Credential screens for our processor were readable. We kept a short go-live checklist and the plugin cleared it. I care less about bells and whistles than clean captures. Ease of configuration beat our last gateway add-on. This is what maintained software should feel like.
Parker H. –
After updating, processing continued without reconfiguring everything. We care about updates more than marketing screenshots. Updates are part of why we pay for maintained software. Good enough that we stopped shopping for alternatives. No fatal errors on activation — always a good start.
Harper T. –
Settlements in the payment processor matched Gravity Forms order totals. Sandbox tests covered approve, decline, and a partial refund. Payment processing is the part that has to work — and it has. Renewal is an easy yes.
Blake K. –
Changelog updates felt intentional, not random churn. We care about updates more than marketing screenshots. Refunds from admin saved a few support tickets already. Updates are part of why we pay for maintained software. Four stars for reliability with small UX nits.
Reese T. –
Settlements in our processor matched Gravity Forms order totals. Technical note: hooks and order meta behaved as expected. We kept a short go-live checklist and the extension cleared it. Renewal is an easy yes.
Harper P. –
As an owner, I measure plugins by fewer payment emergencies. Developer view: less glue code to own long-term. Payment processing is the part that has to work — and it has. No regrets switching to this. Revenue continuity beats fancy admin screens.
Finley D. –
We install gateways for clients; this one reduced go-live risk. Feature note: capture and void flows is actually usable, not just listed. Compatibility checks on staging saved us surprises. Solid keep in our stack.
Logan L. –
Staff can refund without pinging a developer. Our theme developer had almost nothing to patch.
Jordan D. –
Configuration was mostly paste-keys-and-test. Ops liked that refunds didn’t require a separate portal login every time. Good enough that we stopped shopping for alternatives. Front-end impact looks minimal in our checks. Business-owner view: fewer abandoned carts at payment.
Morgan R. –
This add-on didn’t collide with our membership stack. Sandbox tests covered approve, decline, and a partial refund. Compatibility checks on staging saved us surprises. Good tool with a short learning curve.
Casey N. –
Store-owner test: can staff refund without calling me? Technical note: hooks and order meta behaved as expected. Installation itself was uneventful on Gravity Forms. Keeping it enabled without second thoughts. 🚀
Taylor A. –
I just want customers to pay and orders to show paid. Nothing about the Gravity Forms integration felt bolted on. Refunds from admin saved a few support tickets already. Installation itself was uneventful on Gravity Forms.