Skip to content

News

Security notices,releases, news.

What changed at Payshen and what it means for you, newest first. Every API and SDK change, in detail, is in the developer changelog.

RSS feed · Developer changelog

Latest

Newest first.

  1. Developers

    Security updates for every Payshen client library, ahead of an independent penetration test

    @payshen/sdk 0.10.1, @payshen/checkout 0.4.0, the PHP SDK 0.2.1 and the Python SDK 0.1.3 are out. Upgrading is recommended; nothing in your integration needs to change.

  2. Company

    Payshen Founder and CEO Ratomir Jovanovic Introduces Non-Custodial Payment Orchestration Platform

    Founded by Ratomir Jovanovic, Payshen brings multiple payment service providers together through one integration, with intelligent routing, payment visibility and direct merchant settlement.

  3. Security

    Two-factor authentication is now required to change providers, payments or people

    Anyone whose role can change providers, routing, payments, keys, webhooks, people or settings now needs a code from an authenticator app to do so. Reading is unchanged.

  4. Product

    Smart routing finds good providers sooner and reacts to a bad hour within dozens of payments

    Two engine updates: every new provider now gets a fair trial, and a provider that suddenly approves far less loses its traffic within a few dozen payments instead of a few hundred.

  5. Security

    PHP2Shell (CVE-2026-109618, CVE-2026-109619): Payshen is not affected

    PHP's critical security release of 21 October 2026 fixes two remote code execution flaws in PHP itself. No Payshen system runs PHP. If your store or backend runs PHP, update it today.