AuxCORE Payment Gateway For WooCommerce Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
AuxCORE Payment Gateway for WooCommerce connects a WooCommerce store to an approved AuxCORE merchant account.
Supported payment methods in this WordPress.org build:
- Secure Online Payment using the AuxCORE hosted checkout drawer
- Credit/debit card payments
- ACH payments
- WooCommerce classic checkout and WooCommerce Blocks
- Refund support for supported payment methods
- Signed hosted-checkout webhooks
- WooCommerce HPOS compatibility declaration
Text-to-Pay is not included in this WordPress.org build.
An active AuxCORE merchant account and API credentials are required. The plugin does not create a merchant account and does not provide payment processing by itself.
External services
This plugin connects to external payment services because payment processing cannot be performed entirely inside WordPress.
AuxCORE
The merchant configures an AuxCORE API URL and API key in WooCommerce settings. When the merchant or shopper uses the payment features, the plugin may send information required to create, process, reconcile, refund, or support a payment. Depending on the selected payment method, this can include:
- Order ID and order number
- Order amount and currency
- Customer name, email, and phone number
- Billing and shipping address
- Order line-item names, quantities, and amounts
- Merchant and tenant identifiers
- Tokenized payment information or ACH information needed for the selected payment method
- Payment, refund, and transaction identifiers
The hosted checkout is loaded from the AuxCORE service configured for the merchant. AuxCORE also sends signed payment-status webhooks back to this WordPress site.
AuxCORE/AuxPAY service information: https://auxpay.net/
Privacy policy: https://auxpay.net/privacy-policy/
Payrix PayFields
For merchants whose AuxCORE card configuration uses Payrix-hosted card fields, this plugin can load the Payrix PayFields script from:
- Production: https://api.payrix.com/payFieldsScript
- Test: https://test-api.payrix.com/payFieldsScript
Payrix-hosted fields are used to tokenize card information in the shopper’s browser. Raw card data handled inside those hosted fields is sent to Payrix under the merchant’s configured payment relationship rather than being stored by this plugin.
Payrix terms: https://www.payrix.com/wp-content/uploads/sites/2/2021/09/PEX-USA-Terms-of-Service.pdf
Payrix privacy policy: https://www.payrix.com/wp-content/uploads/sites/2/2022/02/PAX-Privacy-Policy.pdf
Privacy
This plugin does not add advertising or analytics tracking. Payment and order information is transmitted only as required to provide the configured payment services. Merchants are responsible for providing their own customer-facing privacy disclosures and for using AuxCORE and connected processors in accordance with their agreements and applicable law.
Debug logging is disabled by default. When enabled, the plugin records operational payment-state and correlation information needed for troubleshooting. It is designed not to log PAN, CVV, bank account numbers, routing numbers, or full payment gateway payloads.
Source code and build tools
Human-readable JavaScript source is included in this plugin under:
assets/js/blocks/assets/js/classic/assets/js/auxcore-drawer.jsassets/js/admin.js
Generated WooCommerce Blocks bundles are stored under assets/js/dist/.
Build instructions and the source-to-generated-file mapping are included below. The included package.json and webpack.config.js describe the npm/webpack build used for the distributed JavaScript.
To rebuild the generated WooCommerce Blocks bundles:
- Install Node.js and npm.
- Run
npm installin the plugin directory. - Run
npm run build. - The human-readable source under
assets/js/blocks/andassets/js/classic/is compiled to the corresponding files underassets/js/dist/.
The distributed bundle filenames are defined in webpack.config.js, and all source files required to rebuild them are included in the plugin archive.
No public Git repository is required to review the generated code because the human-readable source and build configuration are included directly in the submitted plugin archive.
Screenshots
No screenshots provided

