Payments vendors crowd into AI, risk and local rails

Stripe is making payments look like an AI control plane

Stripe had the loudest fortnight. On 5 Sep and again on 8 Sep, observed reports said Stripe had acquired OpenRouter, with reports on both dates valuing the deal at $7.5bn. On 4 Sep and 6 Sep, separate reports said Stripe had acquired Clerky to enhance legal infrastructure and incorporation offerings for start-ups. On 4 Sep, DBS and Stripe announced a partnership around agentic payments in APAC, and Stripe also hired a new executive focused on stablecoins. On 8 Sep, Stripe appointed a new head of global product based in Singapore.

The pattern is not just payments expansion. It is Stripe attaching itself to company formation, AI model routing, stablecoins and agentic commerce. The product surface moved in the same direction. On 9 Sep, Stripe released stripe-react-native 0.76.0, adding a feature to delete a registered wallet address from the current Link account. On 5 Sep, stripe-dotnet v52.5.0-alpha.2 added support for Radar.BillingEvaluation. These are not press-release abstractions. They are checkout, identity, wallet and risk primitives being extended in code.

The quieter signal was the homepage choreography. On 4 Sep, Stripe removed the navigation options “Guide me” and “Find what’s right for you” and replaced “Get Stripe product recommendations” with “Transform your enterprise with agile financial infrastructure”. On 5 Sep it reversed that change. On 6 Sep it reversed it again. On 7 Sep it restored the recommendation language again. That is an unusually visible positioning test: enterprise infrastructure versus guided product selection, switching on consecutive days while the company was also adding large numbers of career pages.

There was competitive pressure in the background. On 5 Sep, two articles reported Anthropic’s initiative to develop in-house payments infrastructure, framed as a potential challenge to Stripe. On 9 Sep, five CVEs were published referencing vulnerabilities in WordPress plugins related to Stripe, including Accept Stripe Payments and Event Tickets and Registration. Neither event changes Stripe’s trajectory on its own, but both explain why trust, extensibility and platform control are now the same conversation.

Adyen turned the vertical dial up

Adyen’s fortnight was about localisation and verticalisation. On 4 Sep, Adyen appointed Nicole Olbe as president for EMEA. On 7 Sep and 8 Sep, Adyen’s partnership with Limitless Technology Group was reported, focused on enhancing payment solutions for gifting brands in APAC. On 13 Sep, reports said Adyen was planning to expand in India after receiving payment licences, allowing it to grow its local team and platform.

The website work was heavy and synchronised. On 4 Sep, Adyen added product pages around peak season, unified commerce and Adobe payment integration, while removing pages for a 2025 seasonal campaign and the Pix and PromptPay payment methods. On 5 Sep, it added pages on in-person fraud trends in retail and AI in its development lifecycle, while removing Paysafecard and Payshop pages. On 7 Sep, it added machine-to-machine payments pages and removed pages related to PayNow, PayPal and Paypo. On 9 Sep, it added 62 product pages across digital media, financial services, food and hospitality, and travel and mobility, while removing 62 older product pages with similar content in different languages and formats. On 14 Sep, it added 16 retail and services product pages while removing 16 product pages detailing specific payment methods.

That sequence matters. This was not a single launch page. It was a broad reshaping of the catalogue from payment-method enumeration towards industry, retail, services and operational themes. Adyen was not quiet in developer channels either. On 8 Sep, it released version 35.0.0 of the adyen-dotnet-api-library with a simplified object model and improved serialisation correctness. On 13 Sep, it released version 6.0.0-alpha.1 of its Android SDK, the first alpha of the next major version, aimed at payment method enablement and developer experience.

Hiring aligns with the same picture. On 14 Sep, Adyen listed 24 openings across roles including Commercial Counsel, Data Engineer and Full-Stack Developer, in San Francisco, Amsterdam, Warsaw and Chicago. Earlier postings across 4 Sep, 5 Sep, 7 Sep and 9 Sep included engineering, compliance, sales and customer risk review roles. The market read is simple: Adyen is operationalising local licences, vertical pages and SDK work at once.

Checkout.com pushed deeper into merchant infrastructure

Checkout.com’s fortnight was narrower than Stripe’s and Adyen’s, but more pointed. On 10 Sep, it launched a product page for US direct acquiring under the MALPB charter, a page for Best Buy Marketplace’s payments infrastructure and a page for platforms. On 12 Sep, two articles detailed Checkout.com providing card acquiring, debit routing and support for Best Buy’s Marketplace offering. On 14 Sep, Checkout.com added Chrono24 as a new customer logo and published a case study on that collaboration.

The developer trail supported the same merchant-infrastructure push. On 4 Sep, checkout-sdk-net 6.0.0 began requiring a merchant-specific subdomain for certain platform types and added error handling for invalid subdomains. On 7 Sep, checkout-sdk-python 4.1.0 added comprehensive support for Bacs Direct Debit. On 10 Sep, Checkout.com added a new checkout-risk-sdk-android repository. This is infrastructure work: acquiring, routing, direct debit, risk and platform configuration.

Pricing also moved. On 9 Sep, the Custom tier changed: “No account maintenance fees” was added, while “Fraud tools included” was removed. That is a small line-item change, but it sits beside the new risk SDK repository on 10 Sep and the Best Buy Marketplace push on 12 Sep. The company is presenting itself around enterprise merchant capability, while risk packaging appears to be getting more explicit.

The content estate tightened at the same time. On 14 Sep, Checkout.com added two product pages related to Visa response codes and strong customer authentication in Bosnia and Herzegovina, while removing one product page and 36 blog pages. A payments vendor deleting dozens of blog pages in the same week it adds case-study and acquiring proof points is choosing authority over breadth.

Europe consolidated while open banking narrowed its message

The largest structural event outside Stripe was in Europe. On 4 Sep, Mollie acquired GoCardless in a deal valued at €1.1bn, with the combination described as creating a payments and financial services partner serving more than 350,000 client companies. On 7 Sep, multiple articles again reported the acquisition, including legal advice from Linklaters. The deal puts account-to-account payment capability inside a broader European merchant payments platform.

GoCardless still shipped through the transition. On 7 Sep, it released version 9.0.0 of the gocardless-nodejs library, including breaking changes that correct amount field types from string to integer. On 11 Sep, it created three repositories: yb-voyager, woocommerce-gateway-gocardless and gocardless-pro-android-sdk. On 11 Sep, it also launched a blog page titled “Convert Abandoned Carts” and removed a product page that provided press information. On 5 Sep, GoCardless detected an AUDDIS-I incident affecting transferred mandates, with impact categorised as none and status investigating.

Plaid’s movement was quieter but precise. On 10 Sep, it introduced product pages for credit fraud risk reporting and identity verification monitoring, added four blog pages including AI topics, and removed six career listings and 239 blog pages. On 14 Sep, Plaid listed 13 openings primarily in engineering and machine learning, including Senior Data Scientist and GTM Compliance Analyst roles across remote options and offices in San Francisco, New York City and Raleigh.

The message from the open banking side is not expansion for its own sake. GoCardless is being absorbed into a larger European payments platform, while Plaid is pruning heavily and leaning into credit, identity, fraud and machine learning. The broad “connect your bank account” story is giving way to risk, compliance and conversion use cases.