Athenian Custom Payment Gateways for WooCommerce
Overview
Product overview
WooCommerce works well for immediate online payment capture, but many real businesses also sell through terms accounts, marketplaces, house accounts, ACH, wire, check, and other externally settled channels. Those workflows usually get forced into ad hoc notes, custom fields, or manual back-office work after the order already exists.
Athenian Custom Payment Gateways solves that by introducing purpose-built payment workflows for nonstandard payment operations. It gives merchants a checkout-visible terms account gateway with approval controls and credit validation, plus an admin-only manual gateway for externally settled orders. Both workflows feed into a shared order metadata model so purchase order numbers, due dates, payment sources, and reconciliation references remain visible, searchable, and usable across WooCommerce admin.
Use cases
- Manual payment collection
- Terms accounts
- B2B checkout
- Order payment operations
Developer
Developer starting point
This baseline documents custom gateway code and WooCommerce integration seams. It does not claim that a payment, order settlement, account approval, or financial ledger mutation has been exercised.
Ecosystem integration story
WooCommerce
This plugin extends WooCommerce rather than bypassing it. It plugs into native payment gateway registration, checkout validation, order status handling, admin order screens, order preview panels, email formatting, and order search so the workflow remains familiar to store operators.
Customer account data and ACF-backed account controls
The terms gateway can read customer-specific values such as per-order credit limits, available credit, accounting email, and notification lists from ACF fields or user meta. That allows merchants to tie checkout permissions and credit exposure directly to account records they already manage.
Accounting and operations workflows
Athenian Custom Payment Gateways helps bridge the gap between storefront ordering and back-office reconciliation. It captures the internal references, due dates, and notification routing that accounting teams need to process terms orders and externally settled payments with less manual cleanup.
Marketplace and external sales channels
For businesses that import, recreate, or manually manage orders tied to external channels, the admin-only manual gateway gives teams a cleaner method to represent those payments inside WooCommerce without pretending that checkout captured the transaction.
The broader Athenian plugin ecosystem
Within the Athenian ecosystem, this plugin fills the payment-operations gap. Where other Athenian components may focus on product, pricing, vendor, or platform coordination, Athenian Custom Payment Gateways focuses on how orders are placed on account, how externally settled payments are recorded, and how payment-related order metadata stays usable after the order is created.
Install
- Reviewed source folder: athenian-custom-payment-gateways
- Plugin version reviewed: 1.0.0
- Local source inventory: 10 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-custom-payment-gateways at main / 046b2a45e09fce630b56a221f65879de43a72b43.
- WordPress and WooCommerce.
- Payment status, account approval, order settlement, email, and ledger effects require separate authenticated verification.
Configuration
- Working positioning — see the linked technical reference excerpt.
- Executive summary — see the linked technical reference excerpt.
- Core marketing message — see the linked technical reference excerpt.
- The problem this plugin solves — see the linked technical reference excerpt.
- What this plugin does — see the linked technical reference excerpt.
- Ecosystem integration story — see the linked technical reference excerpt.
- Why this matters commercially — see the linked technical reference excerpt.
- Key differentiators — see the linked technical reference excerpt.
- Suggested messaging pillars — see the linked technical reference excerpt.
- Short-form copy options — see the linked technical reference excerpt.
- Sales narrative — see the linked technical reference excerpt.
- Best-fit use cases — see the linked technical reference excerpt.
- Positioning statement — see the linked technical reference excerpt.
- Platform-focused primary functionality copy — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 0
- Static action/filter hooks detected in local PHP source: 14
- REST route registrations detected in local PHP source: 0
Shortcodes
- No static add_shortcode registrations were detected by the baseline scanner.
REST Endpoints
- No register_rest_route calls were detected by the baseline scanner.
Hooks
- before_woocommerce_init — athenian-custom-payment-gateways.php
- plugins_loaded — athenian-custom-payment-gateways.php
- woocommerce_admin_order_data_after_billing_address — includes/class-athenian-cpg-admin-order-fields.php
- woocommerce_admin_order_preview_end — includes/class-athenian-cpg-admin-order-fields.php
- woocommerce_admin_process_shop_order — includes/class-athenian-cpg-admin-order-fields.php
- woocommerce_available_payment_gateways — includes/class-athenian-cpg-gateway-manual.php
- woocommerce_checkout_process — includes/class-athenian-cpg-gateway-terms-account.php
- woocommerce_email_format_string — includes/class-athenian-cpg-helpers.php
- woocommerce_order_table_search_query_meta_keys — includes/class-athenian-cpg-admin-order-fields.php
- woocommerce_payment_gateways — athenian-custom-payment-gateways.php
- woocommerce_process_shop_order_meta — includes/class-athenian-cpg-admin-order-fields.php
- woocommerce_shop_order_search_fields — includes/class-athenian-cpg-admin-order-fields.php
- woocommerce_update_options_payment_gateways_ — includes/class-athenian-cpg-gateway-manual.php
- woocommerce_update_options_payment_gateways_ — includes/class-athenian-cpg-gateway-terms-account.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: d51f924928557b9ac440f0fa60ad4c479be14ab34eb33a11fa21b6646688f9b7
- Repository URL: https://github.com/Athenian-Brands/athenian-custom-payment-gateways
- Repository reference: main
- Repository commit: 046b2a45e09fce630b56a221f65879de43a72b43
Source files include: athenian-custom-payment-gateways-icon.png, athenian-custom-payment-gateways.php, athenian-custom-payment-gateways.zip, docs/athenian-custom-payment-gateways-marketing-document.md, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, includes/class-athenian-cpg-admin-order-fields.php, includes/class-athenian-cpg-gateway-manual.php, includes/class-athenian-cpg-gateway-terms-account.php, includes/class-athenian-cpg-helpers.php
Troubleshooting
This baseline documents custom gateway code and WooCommerce integration seams. It does not claim that a payment, order settlement, account approval, or financial ledger mutation has been exercised.
- Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.
FAQ
What is this page intended to establish?
A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.
Is the linked repository baseline verified?
Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.
What remains for release-grade documentation?
Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.