Offer additional manual payment methods

Additional payment gateways lets you create any number of manual payment methods, such as payment at collection or payment by an agreed arrangement. Each method has its own title, instructions, order status and customer roles. It works with POM Theme, classic WooCommerce checkout, Checkout blocks and HPOS order storage.

These methods record orders without contacting a payment provider or collecting money. They do not provide automatic refunds, saved cards or recurring subscription payments.

Create a payment method

You need WooCommerce and permission to manage POM Tweaks settings.

  1. Open Settings → POM Tweaks → E-Commerce → Cart & checkout → Additional payment gateways.
  2. Select Enable and click Add new.
  3. Enter a unique Gateway ID, beginning with custom_gateway_, followed by lowercase letters, numbers or underscores. For example, use custom_gateway_collection.
  4. Enter the customer-facing Title and select Enable this payment gateway.
  5. Add a Description for checkout and Instructions for the order confirmation page and customer order emails. Both accept text and basic safe HTML. Plain-text emails retain readable text and links.
  6. Choose Status after processing and, optionally, Allowed roles.
  7. Click Save, reopen the row and verify its values. Check checkout with a representative customer and a guest before offering the method to customers.

There is no five-method limit. Drag rows to arrange new methods; ordering already configured in WooCommerce → Settings → Payments takes precedence. WooCommerce's native enable/disable control updates the same setting. Use POM Tweaks to edit the method's other fields; its WooCommerce settings page links here.

Keep gateway IDs stable

Orders and other payment rules identify a method by its Gateway ID. Keep that ID unchanged after the method has been used. Changing the title does not change its identity, and reordering a row does not renumber it.

Invalid IDs are ignored. If several rows use the same ID, only the first is used, even when it is disabled. Use a different ID for every new method. Existing methods may use custom_gateway_1 through custom_gateway_5; retain those IDs.

Choose the order status

Choice Result for an order with a balance due
Pending payment The order awaits payment. WooCommerce may cancel it according to the store's unpaid-order and stock settings.
On hold The order is held for manual payment confirmation.
Processing The order can enter fulfilment immediately, although this gateway has collected no money.

WooCommerce handles stock reduction once per order. Zero-total orders use WooCommerce's normal payment completion, including applicable payment method order status rules. Those rules' offline-status choice applies only to native bank transfer, cheque and cash on delivery; choose this method's initial status in its own row.

Restrict who can use a method

Leave Allowed roles empty to allow everyone, including guests. Otherwise, customers must be logged in and have at least one selected role. All their roles are checked. Selecting Administrator also permits network super administrators.

These checks apply to classic checkout, Checkout blocks and payment processing on the server. Other payment restrictions can further limit availability. A temporarily unavailable saved role remains listed so saving another field does not remove the restriction.

Verify and pause a method

Confirm that the enabled method appears with its description, that an excluded customer cannot choose it, and that a staging order receives the intended status and instructions. Instructions appear in customer order emails, not administrator order emails.

Clear Enable this payment gateway to stop new payments while keeping the row's instructions available for existing orders. Removing the row also removes those instructions; the payment ID and title already stored on orders remain. Disabling the whole tweak removes its methods and instructions until it is enabled again.

If a method is missing, check both enable controls, the ID format, duplicate rows and allowed roles. Also check other rules that restrict payment methods for the customer's products or account.