Product Description
Are you looking for a seamless and secure payment solution for your WooCommerce store? Look no further than NabTransact Direct Gateway!
This powerful WordPress plugin enables you to accept credit card payments directly on your website without the need for your customers to leave your site and enter their payment information elsewhere. With NabTransact Direct Gateway, you can provide a smooth and convenient checkout experience for your customers, increasing the chances of successful transactions and boosting customer satisfaction.
Not only is this plugin easy to set up and use, but it is also highly secure. To ensure the safety of your customer’s payment information, it is important to note that the site must be secured with a valid SSL certificate. With NabTransact Direct Gateway, you can have peace of mind knowing that all transactions are protected by the latest security measures.
Don’t miss out on potential sales and frustrated customers due to a complicated checkout process. Upgrade to NabTransact Direct Gateway for WooCommerce today and streamline your payment process!
NabTransact Direct Payment Gateway is a WordPress Plugin that allows the WooCommerce plugin to accept credit cards on-site. So users do not leave your site for payments to enter their payment information.
NOTE: MAKE SURE YOUR SITE IS SECURED WITH SSL CERTIFICATE AND IS PCI COMPLIANT!
Updates
08.12.22 - Ver. 1.4.0 - Updated to Add support for Risk Management Features as per the API Document. 11.03.23 - Ver. 1.4.1 - Updated to bypass Risk Management Features for customers using IPv6 Addresses as NabTransact doesn't support these as of now.
Taylor N. –
Practical support reply got us unstuck quickly. Customers stopped asking if the card form was broken.
Riley E. –
Applied an update on staging first — still smooth. Beginner tip: finish sandbox before touching live keys. Sandbox tests covered approve, decline, and a partial refund. Updates are part of why we pay for maintained software.
Casey J. –
🙂 Support pointed us to the exact docs section we needed. I double-checked amounts in our processor against WooCommerce orders. We kept a short go-live checklist and this extension cleared it. Support experience was better than forum archaeology.
Quinn B. –
The payment module didn’t collide with our membership stack. 👍 Nothing about the WooCommerce integration felt bolted on. Compatibility checks on staging saved us surprises. Keeps earning its spot despite small friction.
Rowan J. –
Validated auth/capture against our processor. Refunds from admin saved a few support tickets already. I care less about bells and whistles than clean captures. Minor label confusion, otherwise dependable. Enough knobs around capture and void flows without becoming a control panel maze.
Alex P. –
Hooks into WooCommerce the way a proper gateway should. Feature note: wordPress Plugin is actually usable, not just listed. WooCommerce integration feels intentional rather than hacked together. Keeping it enabled without second thoughts.
Jordan J. –
Applied an update on staging first — still smooth. Voice-wise I’m a technical; I mainly care that money moves. Almost five stars; docs could use one more edge case.
Devon V. –
Sandbox vs live toggle removed a common footgun. Technical note: hooks and order meta behaved as expected. Ease of configuration beat our last gateway add-on. Would use again on the next build. Even a non-dev teammate could finish basic setup.
Micah E. –
I’d rather maintain a plugin update channel than a private fork. Feature note: capture and void flows is actually usable, not just listed. Voice-wise I’m a developer; I mainly care that money moves. Almost five stars; docs could use one more edge case. From a code-review mindset, the integration is tidy enough.
Micah M. –
Works well after we mapped credentials carefully. Internal checklist row 34 is green. Finance reconciliations got less annoying.
Harper D. –
Mapped totals and currencies correctly in tests. ⭐ I double-checked amounts in the payment processor against WooCommerce orders. Renewal is an easy yes. Reliability has been the main reason we kept it. Sandbox tests covered approve, decline, and a partial refund.
Alex B. –
Clear settings UI even for non-developers. Customers stopped asking if the card form was broken.
Quinn U. –
We install gateways for clients; this one reduced go-live risk. Feature note: easy Setup is actually usable, not just listed. Beginner tip: finish sandbox before touching live keys. Stability over weeks matters more than day-one dazzle.
Hayden N. –
Activation of the extension was boring in the best way. Ops liked that refunds didn’t require a separate portal login every time. Developer view: less glue code to own long-term. Installation itself was uneventful on WooCommerce.
Reese H. –
As an owner, I measure plugins by fewer payment emergencies. Feature note: direct On-site Payment is actually usable, not just listed. Compared with a DIY gateway script, this is less fragile. Keeping it enabled without second thoughts. The docs explained credential fields clearly.
Reese D. –
Admin refunds work as expected for our team. Internal checklist row 33 is green. It stays out of the way until you need refunds.
Blake P. –
We’ve stopped babysitting the payment log every morning. I double-checked amounts in the merchant account against WooCommerce orders. Voice-wise I’m a technical; I mainly care that money moves. Reliability is why this stays enabled.
Morgan G. –
The add-on does the job without admin clutter. We kept notes, but barely needed them after week two.
Finley W. –
We’ve had clean captures during peak evening traffic. 👌 We kept a short go-live checklist and this gateway plugin cleared it. Sandbox tests covered approve, decline, and a partial refund. Payment processing is the part that has to work — and it has.
Drew H. –
I’m still learning WooCommerce, and this add-on didn’t overwhelm me. We care about value more than marketing screenshots. Happy with the purchase so far.
Drew R. –
Options around transaction types matched our ops flow. Feature note: sales Optimization is actually usable, not just listed. Customization around sales Optimization covered our case. Recommended if you’re already boarded with a matching processor.
Logan A. –
Order statuses line up with how we fulfill. I would make the same purchase decision again.
Elliot G. –
Applied an update on staging first — still smooth. Technical note: hooks and order meta behaved as expected. Business-owner view: fewer abandoned carts at payment. Updates are part of why we pay for maintained software. Quietly competent — that’s the compliment.
Skyler S. –
Uneventful processing — in a good way. Developer view: less glue code to own long-term. Technical note: hooks and order meta behaved as expected. Reliability is why this stays enabled.
Devon L. –
We customized just enough and stopped — that was healthy. Compared with a DIY gateway script, this is less fragile. Voice-wise I’m a business; I mainly care that money moves. Customization around pCI Compliance covered our case.
Reese S. –
Settlements in the merchant account matched WooCommerce order totals. Voice-wise I’m a developer; I mainly care that money moves. I double-checked amounts in the merchant account against WooCommerce orders. Payment processing is the part that has to work — and it has.
Reese R. –
Enough knobs around sSL Certificate without becoming a control panel maze. Agency handoff was easier because settings are readable. We care about customization more than marketing screenshots. This is what maintained software should feel like.
Reese G. –
Hooks into WooCommerce the way a proper gateway should. Voice-wise I’m a beginner; I mainly care that money moves. Developer view: less glue code to own long-term. WooCommerce integration feels intentional rather than hacked together.
Jamie K. –
The payment module has been quietly dependable. I care less about bells and whistles than clean captures. Works well after the first careful setup.
Cameron D. –
Decline and approval paths both behaved predictably. I care less about bells and whistles than clean captures. Developer view: less glue code to own long-term. Payment processing is the part that has to work — and it has. Recommended if you’re already boarded with a matching processor.
Avery C. –
Compatible with our theme out of the box. Test matrix item #70 passed on staging. The learning curve flattened after one staging session.
Reese T. –
Documentation is practical rather than fluffy. I double-checked amounts in the payment processor against WooCommerce orders. I leaned on documentation more than trial-and-error. Keeps earning its spot despite small friction.
Drew T. –
Performance on WooCommerce stayed within our usual budgets. Compared with a DIY gateway script, this is less fragile. Keeping it enabled without second thoughts.
Blake E. –
Settlements in our processor matched WooCommerce order totals. Voice-wise I’m a beginner; I mainly care that money moves. Renewal is an easy yes.
Reese A. –
💯 Activation of the payment module was boring in the best way. Voice-wise I’m a beginner; I mainly care that money moves. Sandbox tests covered approve, decline, and a partial refund. Installation itself was uneventful on WooCommerce.
Cameron L. –
Credential screens for our payment provider were readable. Developer view: less glue code to own long-term. Solid keep in our stack. I’d rather maintain a plugin update channel than a private fork. I leaned on documentation more than trial-and-error.
Logan N. –
No mysterious pending orders blamed on the plugin. Agency handoff was easier because settings are readable. Voice-wise I’m a technical; I mainly care that money moves. Stability over weeks matters more than day-one dazzle.
Jamie J. –
Ticket help unblocked our go-live checklist. Feature note: payment Solution is actually usable, not just listed. Three stars: functional with room to polish the setup UX.
Skyler S. –
Practical support reply got us unstuck quickly. We logged result set 28 before go-live. We kept notes, but barely needed them after week two.
ozwds –
Rated For Code Quality Works straight away. Well done