AuxCORE Payment Gateway for WooCommerce

By AuxPAY

0+ active installationsVersion 1.0.1

Connect WooCommerce to AuxCORE for secure hosted checkout, credit/debit card, and ACH payments.

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.js
  • assets/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:

  1. Install Node.js and npm.
  2. Run npm install in the plugin directory.
  3. Run npm run build.
  4. The human-readable source under assets/js/blocks/ and assets/js/classic/ is compiled to the corresponding files under assets/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.

Installation

  1. Upload the plugin ZIP in Plugins > Add New > Upload Plugin or install it from WordPress.org after approval.
  2. Activate AuxCORE Payment Gateway for WooCommerce.
  3. Confirm WooCommerce is installed and active.
  4. Open WooCommerce > Settings > AuxCORE.
  5. Enter the AuxCORE API URL and API key supplied for your merchant account.
  6. Save settings. The plugin will resolve the merchant configuration and register the signed webhook endpoint.
  7. Enable only the payment methods that apply to your merchant account.
  8. Test checkout before accepting live payments.

The API URL should use HTTPS in production.

FAQ

Does this plugin include Text-to-Pay?

No. Text-to-Pay is intentionally not included in this WordPress.org build.

Does the plugin store credit card numbers or CVV?

The plugin is designed to use tokenized or hosted payment-field workflows. It does not intentionally store PAN or CVV in WordPress.

Why does Secure Online Payment create a WooCommerce order before the payment is final?

WooCommerce needs an order record so the payment session can be correlated with the cart. A created order is not treated as paid. Non-final states such as pending, process, processing, or customer authentication remain unpaid until an authoritative final approval is confirmed.

How are hosted payment webhooks authenticated?

The AuxCORE webhook endpoint uses a timestamped HMAC signature and rejects invalid or expired signatures. Financial webhook data is validated against the WooCommerce order before the order state is changed.

Does this plugin support WooCommerce HPOS?

Yes. The plugin declares compatibility with WooCommerce High-Performance Order Storage and uses WooCommerce order APIs for order data.

Changelog

1.0.1

  • WordPress.org compliance-only update; no payment processing or AuxCORE API behavior changed.
  • Added translator comments and numbered placeholders for translatable payment-status strings.
  • Documented the atomic payment-lock database calls for WordPress Coding Standards without changing the lock implementation.
  • Moved build/source documentation into readme.txt and removed the extra root Markdown file.
  • Reduced WordPress.org tags to five.

1.0.0

  • Initial WordPress.org AuxCORE submission build.
  • Includes AuxCORE hosted checkout, credit/debit card, and ACH payment methods.
  • Text-to-Pay removed from the WordPress.org package.
  • Uses AuxCORE-specific class, option, AJAX, script, and filter prefixes.
  • Uses WordPress enqueue APIs for plugin scripts and styles.
  • Includes human-readable JavaScript source and build documentation.
  • Reworked the hosted webhook as a WordPress REST endpoint with HMAC signature verification.
  • Added strict webhook field validation and sanitization before payment-state processing.
  • Preserves hosted-payment finality safeguards so non-final processor states are not treated as paid.
  • Supports customer-action / 3-D Secure redirect URLs, including WPay-compatible RequiresAction and RedirectUrl response shapes.
  • Improves pending-payment progress messaging and prevents unresolved payments from appearing as confirmed on the WooCommerce order-received page.