p3/paymentgateway

Accept payment network payments on your Magento 2 website with hosted & direct integrations

2.0.6 2025-06-11 10:21 UTC

Requires

• php: ~7.4.0||~8.1.0||~8.2.0
• ext-bcmath: *
• ext-curl: *
• ext-openssl: *
• magento/framework: 103.0.*
• magento/module-checkout: 100.4.*
• magento/module-payment: 100.4.*
• magento/module-quote: 101.2.*
• magento/module-sales: 103.0.*

GPL-3.0

README

Compatibility

Compatible with Magento 2.3 and Magento 2.4

Supports both Hosted and Direct integrations

Installation

Step 1:

If you are upgrading this module, please make sure to disable the module first with bin/magento module:disable P3_PaymentGateway.

Step 2:

There are several ways to install the extension:

• Install the Extension using Composer

  Execute the following command to install the extension:

  composer require pixxles/payment-gateway
  

• Copy files

  Make sure to delete app/code/P3 directories that may interfere with the new version. Make sure to delete the P3_PaymentGateway row from the setup_module table in the database so that any database tables required can get created. Create a directory app/code/P3/PaymentGateway and copy the contents of the plugin to this directory.

Step 3: Enable the new module using the command bin/magento module:enable P3_PaymentGateway

Step 4: Upgrade and re-compile magento so that the system will install the module and create all necessary arrangements for the module. This command can be helpful...

bin/magento setup:upgrade && bin/magento setup:db-schema:upgrade && bin/magento setup:di:compile && chmod 775 -R ./var

Step 5: Login to the Admin area of Magento. Click on System > Cache Management. Click on the button labelled ‘Flush Magento Cache’, located at the top right of the page.

Step 6: Click on Stores > Configuration then click on Payment Methods under the Sales heading on the left-hand side of the page. All installed payment methods will be displayed.

Step 7: Click on Payment Network Gateway to expand the configuration options that you will need to fill out before you can use the module. Here you can also select the hosted or direct integration type. Debugging should be turned off during production.

Step 8: Head over to the store's settings and select advanced and then system. Once on this page; change the caching type to 'Varnished'.

FAQ

The processing page /paymentgateway/order/process shows an error page (Page Not Found)

Did you upgrade and re-compile Magento? Otherwise, have you changed either the order controller filename, the directory the order controller was in, or the name of that directory? Do you have the route setup in the /etc/frontend/routes.xml under the route attributes; id of p3 and frontName as p3. Does that same route contain the module element with a name attribute of P3_PaymentGateway? If you answered no to any of these questions. Please set up the appropriate arrangements based on the questions asked and try again after an upgrade & recompile command. Ask support if the error continues.

I get the following error - router requires an id but one isn't set

Go to etc/frontend/routes.xml and make sure the router element uses an id attribute with the value standard

I get the following error - "Module version difference schema version higher/lower than in a database"

Make sure to delete the P3_PaymentGateway row from the setup_module database so that any database tables required can get created during the upgrade/db-schema process upon installation

I get incorrect signature during checkout

Is a signature set up in your configuration both in Magento and the MMS? Make sure this only contains alphabetical and numeric characters without any spaces, full-stops, etc.

I cannot see the Payment Network Gateway in the backend (admin area)

Please try running the following commands:

php bin/magento setup:upgrade
php bin/magento setup:di:compile

The amount, address and name appear to cache upon a checkout Are you using the latest version of this module which fixes this issue?

Disclaimer

Sample code, SDKs and modules have been created as reference material only. Modules are developed and tested against vanilla base platform installs only. Any further module compatibility would need to be tested by the user/merchant/developer. Version support is as shown within the associated VERSION section. All sample code, SDKs and modules offer foundation transaction functionality for merchant and developers to use as a guide and/or to adapt, enhance or otherwise build upon. For the avoidance of doubt, this means that some desired functionality may not be useable or exist. All sample code, SDKs or modules that are used will require complete full end to end testing by the user/merchant/developer. Further to this, use of any sample code, SDKs or modules, Open Payment Network bears no responsibility for; nor extends any warranty in regard to; nor accepts any liability arising due to any changes or errors in functionality that may result. Developers, merchants or other users of any sample code, SDKs or modules accept these conditions de facto upon usage.