Cafetito Hooks 107 hooks

Fires once the plugin has finished bootstrapping and all of its components are loaded. This is the recommended moment for add-ons to register their own gateways, settings, or callbacks against Cafetito, because the container and registries are ready at this point.

Fires when the plugin is activated, after the installer has created or upgraded the database tables and registered capabilities. Use it to seed default options or run one-time activation tasks for your extension.

Fires when the plugin is deactivated, after Cafetito has performed its own cleanup of scheduled events. Use it to clear your add-on's scheduled tasks or transient state.

Fires from the uninstall routine after Cafetito has removed its own data. Use it to delete any options, tables, or files your extension created so the uninstall is complete.

Fires when the Cafetito admin layer has finished initializing (menus, list tables, and admin services). Use it to hook additional admin-only behavior that depends on Cafetito's admin objects being available.

Filters the list of WordPress roles that receive the Cafetito management capability when the plugin is installed. By default only administrator is granted. Add role slugs to extend access.

Filters the capability required to see and access the Cafetito admin menu. Use it to relax or tighten who can reach the plugin's screens.

Filters the tabs shown on the settings page. Add an entry to register a new settings tab provided by your extension.

Filters the default settings values for a given settings group. It fires once per group (for example general and email), with the group name as the second argument. Use it to provide defaults for your own settings or override the plugin's.

Fires after a settings tab has been saved. Use it to react to configuration changes, for example to flush caches or recompute derived options.

Fires while rendering the settings page so a custom tab can output its own fields. The current tab slug is passed so you can render only when your tab is active.

Fires within the gateways section of the settings page so add-on gateways can render their configuration controls alongside the built-in ones.

Fires while rendering a settings tab to allow adding extra setting groups (sections) to that tab. The tab slug is passed so output can be conditional.

Filters the array of registered payment gateways. This is the primary extension point to add a custom gateway to Cafetito: append your gateway instance to the array.

Fires each time a gateway is registered in the registry. Use it to react when a particular gateway becomes available, for example to attach gateway-specific hooks.

Filters the id of the gateway used by default when none is explicitly selected. By default it is the first available gateway. Return a different gateway id to change the default.

Filters the Redsys endpoint URL resolved for a given operation type and environment. Use it to point requests at a custom or alternative endpoint.

Filters the parameters sent to Redsys when starting or processing a payment. Use it to add or adjust merchant parameters before the request is signed and sent. The third argument is the payment context, which is null for some flows (such as refunds).

Filters the map of Redsys error codes to human-readable messages used when surfacing refund and operation errors. Add or override codes to customize the wording shown to administrators.

Fires immediately after a new transaction is created and persisted, before the visitor is redirected to the gateway. Use it to record or enrich the transaction with your own metadata.

Fires whenever a transaction transitions from one status to another. This is the central place to react to any state change, receiving both the old and the new status so you can branch on the specific transition.

Fires when a payment is successfully completed. Use it to trigger fulfillment, sync to a CRM, or run any post-payment logic.

Fires when a payment fails. Use it to alert staff or record the failure for follow-up.

Fires when a payment is cancelled (for example, the visitor aborts at the gateway). Use it to clean up or record the cancellation.

Fires just before the visitor is redirected to the gateway to complete payment. Use it for last-minute logging or to set session data tied to the payment context.

Filters the query arguments used to fetch transactions from the repository. Use it to constrain or extend transaction queries globally.

Filters the order reference generated for a transaction from its internal id. Use it to customize the format of the reference passed to the gateway.

Fires after Cafetito writes an entry to a transaction's event log. Use it to mirror events into an external logging or monitoring system.

Filters the contextual data array attached to a transaction log entry before it is stored. Use it to add structured context to your logged events.

Filters whether a given transaction is allowed to be refunded. Cafetito computes an initial value from the gateway's refund support and the transaction state; return false to block, or true to allow, based on your own rules.

Filters the amount to be refunded for a transaction before the refund is issued. Use it to cap or adjust the refund amount.

Fires just before a refund request is sent to the gateway. Use it for pre-refund logging or validation side effects.

Fires after a refund has been successfully processed by the gateway. Use it to notify the donor, adjust accounting, or sync the refund elsewhere.

Fires when a refund attempt fails at the gateway. Use it to alert staff or record the failure with the gateway result for diagnosis.

Fires when a gateway notification (IPN) is received and its result has been parsed. Use it to react to server-to-server payment notifications, for example to trigger custom fulfillment.

Fires when an incoming gateway notification fails signature verification. Use it for security monitoring and alerting on potentially fraudulent or malformed callbacks.

Filters the notification (IPN) URL that Cafetito sends to the gateway as the callback endpoint for a given gateway. Use it to override the URL, for example behind a proxy or custom routing.

Fires on the return screen when the visitor comes back from a successful payment. Use it to display a thank-you, fire analytics, or run front-end side effects on the success page.

Fires on the return screen when the visitor returns after cancelling the payment. Use it to record the cancellation or show a custom message.

Filters the full HTML of the return result card before it is output to the page. Use it to wrap, replace, or augment the rendered result.

Filters the title shown on the return result screen for a given variant. Use it to customize the heading wording.

Filters the summary rows (label/value pairs) shown for the transaction on the return screen. Use it to add or remove rows of detail.

Filters the action buttons or links shown on the return screen for a given variant. Use it to add a "return to home" or custom call-to-action button.

Filters the body message shown on a successful return. The second argument indicates whether the result is definitive (confirmed) or still provisional.

Filters the body message shown when the visitor returns after cancelling. Use it to customize the cancellation copy.

Filters the body message shown when a payment is rejected. Use it to customize the rejection copy.

Filters the parsed attributes of the Cafetito shortcode before they are used to build the button configuration. Use it to inject defaults or override attributes globally.

Filters the attributes of the Cafetito Gutenberg block before rendering. Use it to normalize or extend block attributes.

Filters the resolved button configuration object built from the shortcode or block attributes. This is the central object describing a payment button or form. Use it to programmatically adjust amounts, fields, labels, or gateway selection.

Filters the list of available donor form fields. Use it to register a custom field or remove a built-in one.

Fires after a front-end form has been submitted and successfully validated, just before checkout starts. Use it to react to a valid submission, for example to capture the sanitized visitor input.

Fires when server-side validation of a form submission fails, before the visitor is redirected back with errors. Use it to log or monitor failed submissions.

Filters the validation errors of a form submission. It lets an add-on add or remove errors (for example, to enforce a custom required field). The errors map uses field keys to message strings.

Filters the data array used to create a transaction from a validated submission. Use it to attach additional fields, metadata, or computed values to the transaction at creation time.

Filters the URL the gateway should redirect to after a successful payment. Use it to send the visitor to a custom thank-you page instead of the default return screen.

Filters the URL the gateway should redirect to after a cancelled payment. Use it to send the visitor to a custom page.

Filters the client IP address resolved for the current request, used for logging and fraud checks. Use it when behind a proxy or load balancer to provide the correct originating IP.

Filters the currency code used by the plugin. Defaults to EUR. Return a different ISO currency code to change the currency used for amounts and formatting.

Filters the default concept (description) text used for a payment when none is supplied, for a given button type. Use it to provide a custom default concept.

Filters the formatted, human-readable string of a monetary amount. Use it to fully customize how amounts are displayed (separators, symbol placement, decimals).

Fires immediately before the payment form is rendered. Use it to output content above the form, given the resolved configuration.

Fires immediately after the payment form is rendered. Use it to output content below the form.

Filters the complete rendered HTML of the payment form. Use it to wrap or post-process the markup.

Filters the title of the payment form. Use it to override the heading text.

Filters the subtitle of the payment form. Use it to override the secondary heading text.

Filters the label of a donor form field. Use it to rename fields shown to visitors.

Filters the label of a payment method shown in the form. Use it to rename a method (for example, "Card" or "Bizum").

Filters the icon used for a payment method in the form. Use it to supply a custom icon URL or markup.

Filters the secondary label (sublabel) of a payment method shown in the form. Use it to add a short descriptor under the method name.

Filters the submit button label of the payment form. Use it to customize the call-to-action wording.

Filters the label used in the compact (inline button) rendering mode of the form. Use it to customize the wording in compact layouts.

Filters the front-end form preset (style/layout preset) before it is applied. Use it to override the visual preset of forms.

Fires after the front-end assets (scripts and styles) have been registered with WordPress. Use it to register additional assets or declare dependencies on Cafetito's handles.

Fires after the front-end assets have been enqueued for output. Use it to enqueue your own assets that depend on Cafetito's.

Filters the URL of a named built-in icon. The default points to the SVG bundled with the plugin. Use it to swap an icon for your own asset.

Fires just before a notification email is sent. Use it for last-minute logging or to alter related state for a given email type and transaction.

Fires after a notification email is sent successfully. Use it to record that the email went out or to chain further notifications.

Fires when sending a notification email fails. Use it to alert staff or retry through an alternative channel.

Filters whether a given email type should be sent for a transaction. Defaults to true. Return false to suppress a specific notification.

Filters the placeholder map used to interpolate the email subject and body for a transaction. Use it to add custom placeholders that your templates can reference.

Filters the subject line of a notification email. Use it to customize the subject per email type.

Filters the raw body message of a notification email before placeholders are applied and the HTML is built. Use it to replace the template text.

Filters the final HTML of a notification email after the body has been assembled. Use it to wrap the content in a custom template or add a header/footer.

Filters the list of recipients for a notification email. Use it to add or remove recipients (for example, a BCC for accounting).

Filters the email preset (style/template preset) applied to a notification email for a given type and transaction. Use it to switch presets per email type.

Filters the "From" name used when sending notification emails. Defaults to the site name. Use it to brand outgoing emails.

Filters the "From" address used when sending notification emails. Defaults to empty (WordPress default). Use it to set a custom sender address.

Filters the headers array sent with a notification email. Use it to add custom headers, Reply-To, or CC/BCC headers.

Fires after the admin assets are enqueued, with the current admin page hook suffix. Use it to enqueue your own admin assets on Cafetito's screens.

Filters the map of transaction statuses to their admin badge definitions (label and styling). Use it to add badges for custom statuses or restyle existing ones.

Filters the summary cards shown above the transactions list. Use it to add custom KPI cards computed from the current summary and filters.

Filters the bulk actions available on the transactions list table. Use it to register a custom bulk action.

Filters the columns displayed in the transactions list table. Use it to add or remove columns.

Fires while rendering a cell of a custom column in the transactions list, for each row. Echo the cell content for your column when its key matches.

Fires once per transaction row while rendering the list table. Use it to output extra row markup or trigger per-row logic.

Fires while rendering the filter controls above the transactions list. Use it to output additional filter inputs. The current active filters are passed.

Filters the query arguments used to fetch transactions for the admin list, given the active filters. Use it to apply custom filtering logic to the admin list query.

Fires on the transaction detail screen, after the core transaction data section. Use it to render additional panels or metadata for the transaction.

Filters the action buttons shown on the transaction detail screen. Use it to add a custom action (for example, a link to an external system).

Fires when an administrator marks a transaction as reviewed. Use it to record the review or trigger downstream workflow.

Fires after an internal note is saved on a transaction. Use it to react to staff notes, for example to sync them elsewhere.

Filters the header row used for the CSV export of transactions. Use it to add columns to the export (pair with cafetito_export_csv_row).

Filters a single data row of the CSV export, given the transaction it represents. Use it to add values that align with custom headers.

Filters the list of fiscal fields (such as NIF/CIF and address fields) collected for invoicing. Use it to add or remove fiscal fields.

Filters whether fiscal data collection is enabled. Return true or false to force fiscal fields on or off.

Filters a translatable text string by key, allowing centralized overriding of the plugin's user-facing copy. Match on the key to override a specific string.

Filters the REST API namespace used by the plugin (default cafetito/v1) for its endpoints, including the notification (IPN) route. Use it to version or relocate the plugin's REST routes. Note that changing this affects the notification URL sent to gateways, so adjust gateway configuration accordingly.