Ignition Crowdfunding v0.20.0

This release is mostly groundwork. It adds the extension points that the new Ignition Platform Fees add-on builds on — a way for a payment gateway to say it will settle a platform’s cut, a single place where a platform deduction is applied to the money a creator nets, and a financial breakdown on the wp-admin pledge detail page. Alongside that, one correction backers will notice: the contribution figures shown to a backer are once again the backer’s own.

Bug Fixes

• Backers see their own contribution, not the creator’s — On a site running a platform commission, the net figure on a backer’s dashboard pledge card and in their refund emails could show what the creator received after the platform’s cut, rather than what the backer actually contributed. On a half-refunded $100 pledge that meant a backer reading $47.50 where their own figure was $50.00. Both now show the backer’s own contribution less any refund. A platform’s cut is an arrangement between the platform and the creator, and is never part of what a backer is told they gave. See Refunds.

Developer

• Gateway settlement question — Igcf_Payment_Attempt_Service::settles_application_fee() asks whether a gateway will actually settle this attempt’s platform fee when it captures the payment, with the igcf_payment_attempt_settles_application_fee filter for gateways to answer. It describes the gateway, not the configuration, so a fee add-on can hold back on attempts nothing can collect from. Defaults to no, which keeps commission entirely inert on a site with no split-capable gateway. See the Service Layer and Filters.

• One place to adjust net-to-creator per pledge — The new igcf_pledge_net_amounts filter applies to both the batch read behind list screens and exports, and the single-pledge read behind the wp-admin pledge detail page. An add-on that deducts money from a creator hooks it once and every creator- and admin-facing net figure agrees. The older igcf_payment_attempt_net_to_creator is per attempt and has no core consumer; per-pledge is what display surfaces actually render. See Filters.

• Pledge detail financial breakdown — Five filters let an add-on show its working on the wp-admin pledge detail page: a line item beside Amount, Refunded and Net, plus extra columns and cells on the Payment Attempts and Refunds tables. Core owns ordering and escaping, and discards a contribution that is not the documented shape, so a misbehaving add-on degrades to core’s own figures instead of breaking the page. See Filters.

• Per-campaign gateway availability — igcf_gateway_available_for_campaign lets an add-on take an enabled gateway away from a specific campaign. It fires only for gateways already reporting themselves available, so a listener can only remove one, never add it back. This is how a gateway that can pay some creators but not others — one needing the creator to have connected an account — keeps itself off the campaigns it cannot serve. See Filters.

• Creator pledge-row actions — igcf_dashboard_campaign_pledge_row_args is the creator-table counterpart to the backer-table row filter, so an add-on can put per-row actions such as “Mark payment received” on a creator’s campaign-pledges table. See Filters.

• Backer-safe refund figures — Igcf_Pledge_Service::get_pledge_refund_amounts() returns a pledge’s money figures with no net adjustment applied, for surfaces shown to backers. Its sibling get_pledge_refund_display() keeps applying the seam, for admin and creator surfaces. Picking the wrong one is what caused the bug fixed above. See the Service Layer.