ifthenpay | Payments for Fluent Forms

PHP Compatibility

Categories with Findings

Positive Observations

• Frontend assets (checkout.css / checkout.js) are enqueued lazily from inside the render filter rather than unconditionally on wp_enqueue_scripts, so they only load on pages that actually render an ifthenpay payment method.
• Admin assets are gated on `strpos( $hook, 'fluent_form' )`, avoiding loading admin CSS/JS on unrelated wp-admin screens.
• The methods catalog is shared between the frontend and admin via a single transient key (iftp_ff_available_methods), avoiding duplicate remote fetches.
• Remote API responses are memoized per-request in IfthenpayIntegration (gatewayKeysMemo, availableMethodsMemo), preventing repeated identical HTTP calls within a single render.
• Method position lookups are cached for an hour in a transient (iftp_ff_method_positions) in IfthenpayProcessor::resolveMethodPosition().
• The activation-email endpoint enforces a 24h cooldown via a DAY_IN_SECONDS transient, preventing spammy mail sends and repeated HTTP POSTs.
• No N+1 query patterns: formatAmount, decode, and the payload builders are pure in-memory operations; the only DB reads are bounded single-row table lookups.
• No unbounded $wpdb->get_results() calls; wpFluent queries are scoped by form_id and meta_key.
• Settings writes use update_option(..., false) for the backoffice key, avoiding autoload bloat.