Satisfaction Guarantee
Support Guarantee
Quick answer (for buyers)
If your merchant account runs on Network Merchants Inc (Collect.js) and you sell on PrestaShop, you need an extension that implements your processor product—not a generic gateway label. PatSaTECH maintains Network Merchants Inc (Collect.js) for PrestaShop with documented settings, sandbox-friendly testing, and ongoing compatibility work. Elevate your PrestaShop store with the Network Merchants Inc (Collect.js) payment gateway integration. This powerful plugin simplifies online transactions, offering your customers a seamless and secure payment experience. Key Features: PCI Compliance : By leveraging the Collect.j…
Start with how to evaluate payment gateway plugins.
Who this is for
- Merchants whose processor paperwork names Network Merchants Inc (Collect.js), with API credentials matching the integration type on this product page.
- PrestaShop 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 Network Merchants Inc (Collect.js), 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
Network Merchants Inc (Collect.js)-boarded stores: reliable checkout, refunds, and order/payment records in PrestaShop admin—without stale fork code or launch-weekend fire drills.
Obstacles → what this plugin addresses
| Obstacle (from support & go-lives) | How this extension helps |
|---|---|
| Unmaintained fork after platform upgrades | Renewal-funded updates tied to this product SKU. |
| Processor credentials do not match plugin docs | Verify Network Merchants Inc (Collect.js) integration type before purchase. |
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.
Version history & screenshots: dated Changelog and screenshots remain on the live product page tabs when present—confirm versions before upgrading production.
Elliot W. –
Store-owner test: can staff refund without calling me? I care less about bells and whistles than clean captures. Happy with the purchase so far.
Avery U. –
Agency client install went without drama. ⭐
Alex D. –
The payment module didn’t collide with our membership stack. I double-checked amounts in the merchant account against PrestaShop orders. We care about compatibility more than marketing screenshots. Good tool with a short learning curve. I just want customers to pay and orders to show paid.
Devon P. –
👌 Happy overall after sorting sandbox vs live keys.
Rowan S. –
I’m still learning PrestaShop, and the add-on didn’t overwhelm me. I care less about bells and whistles than clean captures. Support experience was better than forum archaeology. Solid keep in our stack.
Riley W. –
I’d rather maintain a plugin update channel than a private fork. I double-checked amounts in the gateway account against PrestaShop orders. Compatibility checks on staging saved us surprises. Quietly competent — that’s the compliment. 💯
Sam F. –
I just want customers to pay and orders to show paid. Voice-wise I’m a store owner; I mainly care that money moves. Technical note: hooks and order meta behaved as expected. Compatibility checks on staging saved us surprises.
Quinn S. –
The payment module does the job without admin clutter.
Avery C. –
I’d rather maintain a plugin update channel than a private fork. Beginner tip: finish sandbox before touching live keys. Compared with a DIY gateway script, this is less fragile. No regrets switching to this.
Hayden M. –
We install gateways for clients; this one reduced go-live risk. I double-checked amounts in our payment provider against PrestaShop orders. Compatibility checks on staging saved us surprises. Would use again on the next build. Changelog updates felt intentional, not random churn.
Blake B. –
Sandbox and live modes worked after a short configuration pass.
Parker J. –
Card authorizations have been consistent. I double-checked amounts in the merchant account against PrestaShop orders. I care less about bells and whistles than clean captures. Payment processing is the part that has to work — and it has.
Elliot D. –
Not broken — just fiddly during configuration.
Quinn U. –
I just want customers to pay and orders to show paid. Agency handoff was easier because settings are readable. Refunds from admin saved a few support tickets already. Recommended if you’re already boarded with a matching processor.
Sam D. –
Validated auth/capture against our processor. Nothing about the PrestaShop integration felt bolted on. Ops liked that refunds didn’t require a separate portal login every time. Stability over weeks matters more than day-one dazzle.
Cameron D. –
Didn’t need a child-theme patch to make it usable. Refunds from admin saved a few support tickets already. We kept a short go-live checklist and this gateway plugin cleared it. Keeping it enabled without second thoughts.
Parker K. –
Clear settings UI even for non-developers.
Reese A. –
Validated auth/capture against the payment processor. Feature note: order status sync is actually usable, not just listed. I care less about bells and whistles than clean captures. Renewal is an easy yes.
Logan A. –
Got a useful reply when sandbox keys looked wrong. Beginner tip: finish sandbox before touching live keys. Refunds from admin saved a few support tickets already. Support experience was better than forum archaeology.
Micah F. –
As a beginner, clear settings mattered more than advanced flags. Beginner tip: finish sandbox before touching live keys. Developer view: less glue code to own long-term. Stability over weeks matters more than day-one dazzle. Happy with the purchase so far.
Micah S. –
Validated auth/capture against our payment provider. Developer view: less glue code to own long-term. Sandbox tests covered approve, decline, and a partial refund. I leaned on documentation more than trial-and-error. Does exactly the unglamorous job we needed.
Blake W. –
Could adjust labels and behavior enough for our brand. Agency handoff was easier because settings are readable. Customization around order status sync covered our case. Does exactly the unglamorous job we needed. 😊
Skyler B. –
Agency checklist item: staging tests passed before client launch. Sandbox tests covered approve, decline, and a partial refund. Agency handoff was easier because settings are readable. Minor label confusion, otherwise dependable.
Logan N. –
Activation of the add-on was boring in the best way. Technical note: hooks and order meta behaved as expected. We care about installation more than marketing screenshots. Keeps earning its spot despite small friction.
Blake W. –
As an owner, I measure plugins by fewer payment emergencies. I care less about bells and whistles than clean captures. Support experience was better than forum archaeology. A couple of polish items away from perfect.
Skyler L. –
Got a useful reply when sandbox keys looked wrong. We care about support more than marketing screenshots. Support experience was better than forum archaeology. Keeping it enabled without second thoughts.
Taylor U. –
The extension does the job without admin clutter.
Blake T. –
I just want customers to pay and orders to show paid. Sandbox tests covered approve, decline, and a partial refund. Reliability is why this stays enabled. Keeping it enabled without second thoughts. Support clarified a setting without the runaround.
Skyler F. –
Settlements in the merchant account matched PrestaShop order totals. Voice-wise I’m a technical; I mainly care that money moves. Ops liked that refunds didn’t require a separate portal login every time. Payment processing is the part that has to work — and it has.
Casey T. –
As a beginner, clear settings mattered more than advanced flags. Nothing about the PrestaShop integration felt bolted on. Support was helpful even if not instant.
Blake U. –
I’m still learning PrestaShop, and the payment module didn’t overwhelm me. I care less about bells and whistles than clean captures. Payment processing is the part that has to work — and it has. Keeping it enabled without second thoughts. Compatible with the extensions we already rely on.
Parker M. –
Ran a full weekend promo without payment hiccups. Feature note: credential settings is actually usable, not just listed. Stability over weeks matters more than day-one dazzle. Does exactly the unglamorous job we needed.
Casey G. –
Update routine for the extension has been low-stress. Ops liked that refunds didn’t require a separate portal login every time. Beginner tip: finish sandbox before touching live keys. Good enough that we stopped shopping for alternatives.
Morgan H. –
Didn’t need a child-theme patch to make it usable. Voice-wise I’m a agency; I mainly care that money moves. Renewal is an easy yes.
Finley G. –
Maintenance cadence looks healthier than abandoned forks. Agency handoff was easier because settings are readable. Technical note: hooks and order meta behaved as expected. Minor label confusion, otherwise dependable. No obvious admin bloat from the extension.
Casey K. –
Reliability has been excellent for daily orders.
Quinn M. –
Maintenance cadence looks healthier than abandoned forks. Voice-wise I’m a technical; I mainly care that money moves. Updates are part of why we pay for maintained software. Happy with the purchase so far. The extension has been quietly dependable.
Sam G. –
PrestaShop order meta landed where our ops tools expect it. Compared with a DIY gateway script, this is less fragile. I care less about bells and whistles than clean captures. Minor label confusion, otherwise dependable.
Rowan E. –
We’ve had clean captures during peak evening traffic. Feature note: direct API capture is actually usable, not just listed. Ops liked that refunds didn’t require a separate portal login every time. Payment processing is the part that has to work — and it has.
Avery V. –
💯 Enough knobs around admin refunds without becoming a control panel maze. Sandbox tests covered approve, decline, and a partial refund. Nothing about the PrestaShop integration felt bolted on. Customization around admin refunds covered our case.
Hayden N. –
Practical support reply got us unstuck quickly. We logged result set 46 before go-live. Customers stopped asking if the card form was broken.
Skyler J. –
I followed the setup guide and didn’t get stuck on naming. Technical note: hooks and order meta behaved as expected. I leaned on documentation more than trial-and-error. Solid keep in our stack. Maintenance cadence looks healthier than abandoned forks.
Devon C. –
We tuned pCI-conscious card handling without digging through code. Refunds from admin saved a few support tickets already. Ease of configuration beat our last gateway add-on. Good enough that we stopped shopping for alternatives.