Hooks and filters
Extension points for developers and add-ons.
Payment methods are a filterable registry rather than one class per bank, so adding a bank is a single entry rather than a new file. The hooks below are the documented, supported surface, and they are what the Pro add-on itself uses.
Adding a payment method
Filter the registry with ibfw_methods. Each entry describes one method, and anything you add behaves like a built-in one throughout the plugin.
Extension points added in 1.1.0
| Hook | Kind | What it is for |
|---|---|---|
ibfw_after_email_instructions |
action | Append your own content after the payment instructions in customer emails. |
ibfw_expected_amount |
filter | Change the figure the customer is asked to transfer. Pro uses this for down payments. |
IBFW_Plugin::owns_order() |
method | Ask whether an order was paid through one of this plugin’s methods. |
Admin tabs
The settings screen’s tab strip is built from the ibfw_admin_tabs filter. An entry takes a label, an icon and an optional in_submenu flag, which when false keeps the tab out of the admin menu while leaving it on the strip. Render your tab on the ibfw_admin_render_tab action.
Priority decides order. The Pro tabs register between 10 and 13, the licence tab at 99, and the More Plugins tab at 200 so it stays last.