{"id":17255,"date":"2026-09-25T12:00:29","date_gmt":"2026-09-25T06:30:29","guid":{"rendered":"https:\/\/www.fast2sms.com\/help\/pe-tm-chain-status\/"},"modified":"2026-09-26T11:15:15","modified_gmt":"2026-09-26T05:45:15","slug":"pe-tm-chain-status","status":"publish","type":"post","link":"https:\/\/www.fast2sms.com\/help\/pe-tm-chain-status\/","title":{"rendered":"PE-TM Chain Status Explained: Pending, Approved, Rejected & What To Do"},"content":{"rendered":"

You created the PE-TM chain, and now the portal shows a status you are not sure about: Pending, Pending with PE, Pending final approval, Registered, Active, Rejected, Blacklisted. Each operator DLT uses slightly different words for the same lifecycle, and with the TRAI PE-TM Binding Framework enforcing blocking from 30th September, the difference between “Pending” and “Active” is the difference between delivered and dropped. This guide maps every status you will see on Jio, Airtel, Vi, BSNL, Tata and Smartping to what it means and what to do next.<\/p>\n

Signup Now<\/a>Schedule Free Meeting<\/a><\/p>\n

The chain lifecycle in one picture<\/h2>\n

Whatever the portal calls it, a PE-TM chain moves through the same stages:<\/p>\n

    \n
  1. Requested \/ Pending with TM:<\/strong> you (the PE) created the chain naming a TM-D; the telemarketer must accept it.<\/li>\n
  2. Pending with PE \/ Pending final approval:<\/strong> the TM-D accepted; on several portals the PE must now confirm once more.<\/li>\n
  3. Registered \/ Active \/ Approved:<\/strong> both sides approved; the chain is live and its hash is what operators validate against.<\/li>\n
  4. Rejected \/ Blacklisted \/ Inactive:<\/strong> declined, expired or suspended; no valid chain exists for that route.<\/li>\n<\/ol>\n

    Only stage 3 protects your traffic. Everything else counts as “no approved chain” once blocking mode is on.<\/p>\n

    Status names by operator portal<\/h2>\n
    \n\n\n\n\n\n\n\n\n\n\n
    Portal<\/th>\nWaiting on TM<\/th>\nWaiting on you (PE)<\/th>\nLive<\/th>\nFailed<\/th>\n<\/tr>\n<\/thead>\n
    Jio TrueConnect<\/td>\nRequested<\/td>\nPending for Approval (Approve \/ Reject action)<\/td>\nRegistered, Chain Status Active<\/td>\nRejected<\/td>\n<\/tr>\n
    Airtel<\/td>\nPending<\/td>\nPending with PE (View Workflow \u2192 Approve)<\/td>\nActive, “PE TM Chain is Completed”<\/td>\nRejected<\/td>\n<\/tr>\n
    Vi (Vilpower)<\/td>\nApproval Status Pending<\/td>\nChain State Pending (Approve on the lineage view)<\/td>\nChain approved, Status Active<\/td>\nRejected \/ Suspended<\/td>\n<\/tr>\n
    BSNL<\/td>\nApproval Status Pending<\/td>\nPending (final approve after TM accepts)<\/td>\nApproved, Status Active<\/td>\nRejected<\/td>\n<\/tr>\n
    Smartping \/ Videocon<\/td>\nPending PE-TM Chain<\/td>\nPending final approval (Chain Flow \u2192 Approve)<\/td>\nRegistered PE-TM Chain<\/td>\nRejected \/ Blacklisted<\/td>\n<\/tr>\n
    Tata<\/td>\nSubmitted<\/td>\nPE approval where prompted<\/td>\nListed in PE TM Binding List as active<\/td>\nRejected<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Click-by-click screens for each portal: Jio<\/a>, Airtel<\/a>, Vi<\/a>, BSNL<\/a>, Tata<\/a>, Smartping<\/a>.<\/p>\n

    The step most people miss: the second approval<\/h2>\n

    On Jio, Airtel, Vi, BSNL and Smartping, the chain is not live when the telemarketer accepts it<\/strong>. The request comes back to the PE for a final confirmation: “Pending for Approval” on Jio, “Pending with PE” on Airtel, “Pending final approval” on Smartping, the Approve button on the lineage view on Vi. Chains sit in this state for weeks because nobody logs back in. Until you press Approve, there is no active chain and no valid hash, and the mismatch warnings keep coming.<\/p>\n

    Rule of thumb:<\/strong> after your TM confirms they have accepted, log in to each portal the same day and complete the PE-side approval.<\/p>\n

    What each status means for your traffic under the framework<\/h2>\n
    \n\n\n\n\n\n\n\n\n
    Status<\/th>\nBefore 30th September<\/th>\nAfter 30th September<\/th>\n<\/tr>\n<\/thead>\n
    Active \/ Registered<\/td>\nDelivers, no warnings<\/td>\nDelivers<\/td>\n<\/tr>\n
    Pending (any kind)<\/td>\nDelivers with mismatch warnings<\/td>\nBlocked<\/strong><\/td>\n<\/tr>\n
    Rejected \/ Inactive<\/td>\nDelivers with warnings<\/td>\nBlocked<\/strong><\/td>\n<\/tr>\n
    No chain created<\/td>\nDelivers with warnings<\/td>\nBlocked<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Rejected? Here is why, usually<\/h2>\n