Satisfaction Guarantee
Support Guarantee
Quick answer (for buyers)
If your merchant account runs on PSiGate Direct and you sell on Gravity Forms, you need an extension that implements your processor product—not a generic gateway label. PatSaTECH maintains PSiGate Direct Payment Gateway for Gravity Forms with documented settings, sandbox-friendly testing, and ongoing compatibility work. PSiGate Payment Gateway : Secure & Reliable eCommerce Solution The PSiGate Payment Gateway is a trusted payment processing solution that allows businesses to seamlessly accept Canadian and U.S. dollar transactions. Catering to retailers across North America, PSiGate ensures smoot…
Start with how to evaluate payment gateway plugins.
Who this is for
- Merchants whose processor paperwork names PSiGate Direct, 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 PSiGate Direct, 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
PSiGate Direct-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 PSiGate Direct 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.
Micah M. –
The docs explained credential fields clearly. Agency handoff was easier because settings are readable. Acceptable result after reading docs twice. 👌
Blake L. –
Credential mapping finally made sense after the docs. 💯 It stays out of the way until you need refunds.
Blake C. –
Documentation is practical rather than fluffy. Feature note: admin refunds is actually usable, not just listed. I leaned on documentation more than trial-and-error. Would use again on the next build. We’ve had clean captures during peak evening traffic.
Skyler B. –
I followed the setup guide and didn’t get stuck on naming. Compared with a DIY gateway script, this is less fragile. We kept a short go-live checklist and this gateway plugin cleared it. I leaned on documentation more than trial-and-error. Four stars for reliability with small UX nits.
Riley S. –
Asked about test mode; response was specific and actionable. Developer view: less glue code to own long-term. Support experience was better than forum archaeology. Recommended if you’re already boarded with a matching processor.
Finley F. –
Works well after we mapped credentials carefully. Test matrix item #27 passed on staging. The learning curve flattened after one staging session.
Micah J. –
Validated auth/capture against the merchant account. Voice-wise I’m a technical; I mainly care that money moves. Reliability is why this stays enabled. Keeping it enabled without second thoughts.
Parker V. –
Updates have been uneventful so far. Regression pass 19 didn’t surface issues. That alone justified keeping the license active.
Rowan V. –
No mysterious pending orders blamed on this plugin. Feature note: test mode is actually usable, not just listed. Stability over weeks matters more than day-one dazzle. Quietly competent — that’s the compliment.
Casey W. –
Clean Gravity Forms integration overall. No late-night payment fire drills since switching.
Casey R. –
Hooks into Gravity Forms the way a proper gateway should. Agency handoff was easier because settings are readable. Minor label confusion, otherwise dependable.
Parker B. –
This add-on has been quietly dependable. Nothing about the Gravity Forms integration felt bolted on. Voice-wise I’m a agency; I mainly care that money moves. Reliability is why this stays enabled. Happy with the purchase so far.
Micah N. –
Plugin updates haven’t knocked form payment offline for us. Compared with a DIY gateway script, this is less fragile. Updates are part of why we pay for maintained software. Functional outcome; setup experience held the score down.
Parker W. –
Support clarified a setting without the runaround. Beginner tip: finish sandbox before touching live keys. Compared with a DIY gateway script, this is less fragile. Renewal is an easy yes.
Riley V. –
Validated auth/capture against the payment processor. Voice-wise I’m a technical; I mainly care that money moves. Stability over weeks matters more than day-one dazzle. A couple of polish items away from perfect.
Alex N. –
Played nicely with our current Gravity Forms version and theme. Refunds from admin saved a few support tickets already. I care less about bells and whistles than clean captures. Compatibility checks on staging saved us surprises. This is what maintained software should feel like.
Rowan E. –
No mysterious pending orders blamed on the add-on. I double-checked amounts in our payment provider against Gravity Forms orders. Stability over weeks matters more than day-one dazzle. Four stars for reliability with small UX nits. Paying for maintained software beat babysitting a fork. 🙌
Riley E. –
Could adjust labels and behavior enough for our brand. We care about customization more than marketing screenshots. Agency handoff was easier because settings are readable. Happy with the purchase so far.
Riley N. –
Plugin updates haven’t knocked form payment offline for us. Beginner tip: finish sandbox before touching live keys. Refunds from admin saved a few support tickets already. Updates are part of why we pay for maintained software. Keeping it enabled without second thoughts.
Harper H. –
Sandbox vs live toggle removed a common footgun. Nothing about the Gravity Forms integration felt bolted on. Ease of configuration beat our last gateway add-on. Fine once configured; onboarding was the slow part.
Riley K. –
Admin refunds work as expected for our team. We kept notes, but barely needed them after week two.
Hayden T. –
Theme styling around the form payment still looked coherent. Feature note: pCI-conscious card handling is actually usable, not just listed. Agency handoff was easier because settings are readable. Compatibility checks on staging saved us surprises.
Parker S. –
Staff can refund without pinging a developer. Cutover from staging felt controlled.
Rowan K. –
👍 Uneventful processing — in a good way. Compared with a DIY gateway script, this is less fragile. We kept a short go-live checklist and this plugin cleared it. Reliability is why this stays enabled. Minor label confusion, otherwise dependable.
Devon H. –
Could adjust labels and behavior enough for our brand. Voice-wise I’m a business; I mainly care that money moves. Nothing about the Gravity Forms integration felt bolted on. Customization around credential settings covered our case. Keeps earning its spot despite small friction.
Reese S. –
Install took a couple of minutes on our Gravity Forms site. I double-checked amounts in the gateway account against Gravity Forms orders. Compared with a DIY gateway script, this is less fragile. Recommended if you’re already boarded with a matching processor. From a code-review mindset, the integration is tidy enough.
Hayden D. –
I’m still learning Gravity Forms, and this plugin didn’t overwhelm me. Voice-wise I’m a beginner; I mainly care that money moves. Performance stayed in an acceptable band for form payment. Quietly competent — that’s the compliment. Weeks later, form payment still behaves the same.
Reese P. –
No mysterious pending orders blamed on the extension. Technical note: hooks and order meta behaved as expected. Beginner tip: finish sandbox before touching live keys. Keeping it enabled without second thoughts.
Rowan W. –
Reliability has been the main reason we kept it. We kept a short go-live checklist and the extension cleared it. Renewal is an easy yes.
Cameron F. –
Ran a full weekend promo without payment hiccups. Agency handoff was easier because settings are readable. Sandbox tests covered approve, decline, and a partial refund. Stability over weeks matters more than day-one dazzle.
Reese A. –
As a beginner, clear settings mattered more than advanced flags. Feature note: user Experience is actually usable, not just listed. We care about stability more than marketing screenshots. Stability over weeks matters more than day-one dazzle.
Jamie H. –
No theme conflicts after enabling the add-on. Smoke test batch 26 looked clean. Our theme developer had almost nothing to patch.
Logan H. –
Enough knobs around user Experience without becoming a control panel maze. Technical note: hooks and order meta behaved as expected. Agency handoff was easier because settings are readable. Customization around user Experience covered our case.
Devon P. –
Validated auth/capture against the gateway account. Technical note: hooks and order meta behaved as expected. Almost five stars; docs could use one more edge case.
Reese P. –
Even a non-dev teammate could finish basic setup. Agency handoff was easier because settings are readable. I care less about bells and whistles than clean captures. Support was helpful even if not instant.
Avery A. –
The connection feels native inside Gravity Forms. 🙌 Compared with a DIY gateway script, this is less fragile. Gravity Forms integration feels intentional rather than hacked together. This is what maintained software should feel like. Dropped it into plugins, flipped it on, moved to settings.
Blake M. –
Help pages matched what we saw in the admin UI. Feature note: trustworthy eCommerce is actually usable, not just listed. Compared with a DIY gateway script, this is less fragile. I leaned on documentation more than trial-and-error.
Avery W. –
The docs explained credential fields clearly. Nothing about the Gravity Forms integration felt bolted on. Compared with a DIY gateway script, this is less fragile. I leaned on documentation more than trial-and-error.
Micah U. –
I’m still learning Gravity Forms, and this extension didn’t overwhelm me. Compared with a DIY gateway script, this is less fragile. Stability over weeks matters more than day-one dazzle. Quietly competent — that’s the compliment.
Elliot T. –
Four stars — support helpful, not instant. We kept notes, but barely needed them after week two.
Harper N. –
Stable processing since go-live. Test matrix item #88 passed on staging. The learning curve flattened after one staging session.
Cameron J. –
Staging stress tests didn’t uncover flaky calls from the plugin side. Sandbox tests covered approve, decline, and a partial refund. Would use again on the next build.
Jordan M. –
One careful read of the docs was enough to configure the payment processor. Sandbox tests covered approve, decline, and a partial refund. Ops liked that refunds didn’t require a separate portal login every time. I leaned on documentation more than trial-and-error.
Morgan E. –
Sandbox and live modes worked after a short configuration pass. It stays out of the way until you need refunds.
Avery W. –
Help pages matched what we saw in the admin UI. We care about documentation more than marketing screenshots. I leaned on documentation more than trial-and-error. Does exactly the unglamorous job we needed.
Casey V. –
I’m still learning Gravity Forms, and the payment module didn’t overwhelm me. Beginner tip: finish sandbox before touching live keys. I leaned on documentation more than trial-and-error. Recommended if you’re already boarded with a matching processor.
Riley N. –
From a code-review mindset, the integration is tidy enough. Ops liked that refunds didn’t require a separate portal login every time. Quietly competent — that’s the compliment.
Morgan G. –
The payment module does the job without admin clutter. 👍 We logged result set 41 before go-live. I would make the same purchase decision again.
Drew G. –
Revenue continuity beats fancy admin screens. Nothing about the Gravity Forms integration felt bolted on. Voice-wise I’m a business; I mainly care that money moves. Payment processing is the part that has to work — and it has.
Avery B. –
The docs explained credential fields clearly. Sandbox tests covered approve, decline, and a partial refund. Overall positive, with setup friction as the main ding.
Elliot T. –
Even a non-dev teammate could finish basic setup. I double-checked amounts in our processor against Gravity Forms orders. Ease of configuration beat our last gateway add-on. Quietly competent — that’s the compliment.
Blake A. –
I’d rather maintain a plugin update channel than a private fork. We care about compatibility more than marketing screenshots. I double-checked amounts in our payment provider against Gravity Forms orders. Compatibility checks on staging saved us surprises.
Jamie J. –
👍 We’ve had clean captures during peak evening traffic. Developer view: less glue code to own long-term. Payment processing is the part that has to work — and it has. Keeps earning its spot despite small friction.
Avery H. –
We install gateways for clients; this one reduced go-live risk. Nothing about the Gravity Forms integration felt bolted on. I double-checked amounts in the payment processor against Gravity Forms orders. Support was helpful even if not instant.
Finley B. –
Didn’t make form payment feel heavier after install. Technical note: hooks and order meta behaved as expected. Good tool with a short learning curve.