What the new TDS Author Payment Program tiers pay

The TDS Author Payment Program got a structural overhaul, and if you write for the platform, the math behind your next payout has changed. I have spent more than a decade building payment gateways and reward systems, so I have watched a lot of incentive shifts go past. When a platform “iterates” on its payment logic, the usual direction is consolidation. TDS went the other way and made the scaling more aggressive for high-volume, high-engagement authors.

The intent behind the updated TDS Author Payment Program looks straightforward: reward quality at scale. One-hit wonders count for less than authors who clear the engagement threshold month after month. So the mid-range tiers got tighter while the ceiling on a top-performing article went up.

How the TDS Author Payment Program math works now

The old $100 base tier was broad. It covered everything from 500 to 5,000 views, which is a wide range to settle with one flat fee. The new model splits that up. An article now leaves the flat fee and moves onto a per-view commission at 2,500 views instead.

The monthly article cap going from four to ten is the part I find more interesting. Platforms choke on high-frequency payouts all the time, either from the admin overhead or from Stripe API limits. Raising the cap says TDS thinks its backend and its budget can absorb 150% more eligible content per author. Their original launch details are still up if you want to see where the program started.

Written out as a PHP function, the new TDS Author Payment Program tiers come down to this:

<?php
/**
 * Programmatic representation of the new TDS payout tiers (Effective March 2026).
 * 
 * @param int $engaged_views The number of engaged views.
 * @return float Calculated payout amount.
 */
function bbioon_calculate_tds_payout( int $engaged_views ) : float {
    $payout = 0.0;
    $cap    = 7500.00;

    if ( $engaged_views < 500 ) {
        return 0.0;
    }

    if ( $engaged_views >= 500 && $engaged_views < 2500 ) {
        $payout = 100.00;
    } elseif ( $engaged_views >= 2500 && $engaged_views < 7500 ) {
        $payout = $engaged_views * 0.05;
    } elseif ( $engaged_views >= 7500 ) {
        $payout = $engaged_views * 0.10;
    }

    return min( $payout, $cap );
}
?>

What the per-view switch does to your payout

Once an article passes 2,500 views, the flat $100 turns into $0.05 per view, and the gap opens up fast. A piece at 5,000 views pays $250 under the new rules against $100 under the old ones. That changes what you optimize for. Publishing on schedule stops being the whole job, and how far a piece travels weeks after it goes live starts to matter more.

I have written before about how clear communication and changelogs shape your professional reputation, and payment changelogs deserve the same close read. Past 7,500 views the rate becomes $0.10, so one article that clears that mark pays at least $750. That is a real professional fee for a single piece.

If keeping up with TDS Author Payment Program changes is eating hours you would rather spend building, I can take the WordPress side off your plate. I have been working with it since the 4.x days.

Who the new tiers actually favor

The updated TDS Author Payment Program is built for the top slice of contributors, the roughly 10% who pull most of the engagement. Bigger per-view rewards plus a higher monthly cap add up to a pro tier for technical writers. Before you submit, read their submission guidelines and check that your Stripe configuration can handle the extra volume.

author avatar
Ahmad Wael
I'm a WordPress and WooCommerce developer with 15+ years of experience building custom e-commerce solutions and plugins. I specialize in PHP development, following WordPress coding standards to deliver clean, maintainable code. Currently, I'm exploring AI and e-commerce by building multi-agent systems and SaaS products that integrate technologies like Google Gemini API with WordPress platforms, approaching every project with a commitment to performance, security, and exceptional user experience.