Satisfaction Guarantee
Support Guarantee
Quick answer (for buyers)
If your merchant account runs on 2Checkout (now Verifone) and you sell on Gravity Forms, you need an extension that implements your processor product—not a generic gateway label. PatSaTECH maintains 2Checkout (now Verifone) Gateway for Gravity Forms with documented settings, sandbox-friendly testing, and ongoing compatibility work. 2Checkout (now Verifone) Payment Gateway Introducing 2Checkout (now Verifone) , a leading payment gateway designed to offer businesses a seamless and secure checkout experience worldwide. Supporting over 15 languages and 26 currencies, 2Checkout enables smooth global transactions…
Start with how to evaluate payment gateway plugins.
Who this is for
- Merchants whose processor paperwork names 2Checkout (now Verifone), 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 2Checkout (now Verifone), 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
2Checkout (now Verifone)-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 2Checkout (now Verifone) 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.
Blake F. –
I’m still learning Gravity Forms, and the payment module didn’t overwhelm me. Ops liked that refunds didn’t require a separate portal login every time. Developer view: less glue code to own long-term. No regrets switching to this.
Alex F. –
Payment step still snappy on mobile. Feature note: payment Security is actually usable, not just listed. Quietly competent — that’s the compliment.
Rowan W. –
I’m still learning Gravity Forms, and the add-on didn’t overwhelm me. 🙌 Ops liked that refunds didn’t require a separate portal login every time. Recommended if you’re already boarded with a matching processor. As a beginner, clear settings mattered more than advanced flags. Business-owner view: fewer abandoned carts at payment.
Hayden P. –
👍 Front-end impact looks minimal in our checks. We care about performance more than marketing screenshots. Performance stayed in an acceptable band for form payment. Solid keep in our stack. Uneventful processing — in a good way.
Avery S. –
Keeps earning its spot despite small friction. Regression pass 55 didn’t surface issues. That alone justified keeping the license active.
Sam P. –
Sandbox vs live toggle removed a common footgun. Beginner tip: finish sandbox before touching live keys. Ease of configuration beat our last gateway add-on. Support was helpful even if not instant.
Harper C. –
Ran a full weekend promo without payment hiccups. Voice-wise I’m a technical; I mainly care that money moves. Stability over weeks matters more than day-one dazzle. Would use again on the next build.
Finley B. –
Stable under normal daily order volume. Feature note: test mode is actually usable, not just listed. Keeping it enabled without second thoughts. License cost is easy to justify against failed carts. Beginner tip: finish sandbox before touching live keys.
Skyler H. –
No mysterious pending orders blamed on the payment module. Beginner tip: finish sandbox before touching live keys. Voice-wise I’m a store owner; I mainly care that money moves. Works for us after a patient staging afternoon.
Drew U. –
No fatal errors on activation — always a good start. Nothing about the Gravity Forms integration felt bolted on. Installation itself was uneventful on Gravity Forms. Support was helpful even if not instant.
Harper T. –
Lightweight and stays out of the way. Our theme developer had almost nothing to patch.
Elliot R. –
Didn’t make form payment feel heavier after install. Voice-wise I’m a agency; I mainly care that money moves. No regrets switching to this. Decline and approval paths both behaved predictably. Beginner tip: finish sandbox before touching live keys.
Jordan D. –
We tuned gravity Forms without digging through code. Business-owner view: fewer abandoned carts at payment. Ease of configuration beat our last gateway add-on. Keeping it enabled without second thoughts.
Jamie W. –
We customized just enough and stopped — that was healthy. Feature note: transaction logging is actually usable, not just listed. Business-owner view: fewer abandoned carts at payment. Customization around transaction logging covered our case.
Taylor E. –
Front-end impact looks minimal in our checks. Technical note: hooks and order meta behaved as expected. Performance stayed in an acceptable band for form payment. Minor label confusion, otherwise dependable. Uneventful processing — in a good way.
Sam F. –
Paying for maintained software beat babysitting a fork. Developer view: less glue code to own long-term. Beginner tip: finish sandbox before touching live keys. This is what maintained software should feel like.
Sam M. –
Compatible after a tiny CSS tweak near buttons. The admin experience stayed calm under load.
Finley R. –
We’ve stopped babysitting the payment log every morning. Compared with a DIY gateway script, this is less fragile. Beginner tip: finish sandbox before touching live keys. Reliability is why this stays enabled.
Devon M. –
Good production fit after a careful staging pass. It stays out of the way until you need refunds.
Jordan D. –
Update routine for the add-on has been low-stress. Sandbox tests covered approve, decline, and a partial refund. Good tool with a short learning curve.
Sam G. –
Help pages matched what we saw in the admin UI. 📝 Nothing about the Gravity Forms integration felt bolted on. I leaned on documentation more than trial-and-error. Gets there, but the first hour asks for patience. As a beginner, clear settings mattered more than advanced flags.
Elliot P. –
I’m still learning Gravity Forms, and this extension didn’t overwhelm me. Refunds from admin saved a few support tickets already. Performance stayed in an acceptable band for form payment. This is what maintained software should feel like.
Rowan L. –
Didn’t need a child-theme patch to make it usable. Ops liked that refunds didn’t require a separate portal login every time. We kept a short go-live checklist and this extension cleared it. Customization around payment Security covered our case.
Reese B. –
Clean install path; no mystery dependencies. We care about installation more than marketing screenshots. Installation itself was uneventful on Gravity Forms. Happy with the purchase so far.
Parker M. –
Activation of this extension was boring in the best way. I care less about bells and whistles than clean captures. I’d like richer decline logging, but it’s fine.
Casey N. –
Cheaper than paying a developer to maintain custom gateway code. Sandbox tests covered approve, decline, and a partial refund. We kept a short go-live checklist and this extension cleared it. Solid keep in our stack.
Taylor D. –
This extension does the job without admin clutter.
Reese C. –
Asked about payment Security; response was specific and actionable. Sandbox tests covered approve, decline, and a partial refund. We kept a short go-live checklist and this plugin cleared it. Support experience was better than forum archaeology.
Riley R. –
Asked about credential settings; response was specific and actionable. Ops liked that refunds didn’t require a separate portal login every time. Agency handoff was easier because settings are readable. Support experience was better than forum archaeology.
Quinn F. –
Mobile form payment completions look healthier now. Test matrix item #29 passed on staging. The learning curve flattened after one staging session.
Reese R. –
Credential screens for the gateway account were readable. Business-owner view: fewer abandoned carts at payment. Ease of configuration beat our last gateway add-on. Solid keep in our stack.
Taylor B. –
😊 Live traffic week one was uneventful — in a good way. That alone justified keeping the license active.
Avery M. –
Asked about capture and void flows; response was specific and actionable. I care less about bells and whistles than clean captures. Four stars for reliability with small UX nits. Store-owner test: can staff refund without calling me? Business-owner view: fewer abandoned carts at payment.
Jamie P. –
Weeks later, form payment still behaves the same. Compared with a DIY gateway script, this is less fragile. Sandbox tests covered approve, decline, and a partial refund. Would use again on the next build.
Jordan W. –
I just want customers to pay and orders to show paid. We care about customization more than marketing screenshots. Business-owner view: fewer abandoned carts at payment. Customization around sandbox and live modes covered our case. Does exactly the unglamorous job we needed.
Parker E. –
Settlements in our payment provider matched Gravity Forms order totals. We care about payment processing more than marketing screenshots. Sandbox tests covered approve, decline, and a partial refund. Payment processing is the part that has to work — and it has.
Jordan D. –
Could adjust labels and behavior enough for our brand. Voice-wise I’m a developer; I mainly care that money moves. Customization around admin refunds covered our case. Usable, but plan time for first-time credential mapping.
Blake M. –
Staging tests gave us confidence before cutover. We logged result set 8 before go-live. Customers stopped asking if the card form was broken.
Jordan K. –
Update routine for this gateway plugin has been low-stress. Ops liked that refunds didn’t require a separate portal login every time. Refunds from admin saved a few support tickets already. Updates are part of why we pay for maintained software.
CodeAstrology –
Rated For Feature Availability Not bad. I have gotten exact result from this plugin. Overall thanks for this plugin.
wahab83_pk –
Rated For Feature Availability Great Extension..