# Payment Systems

Published articles for Payment Systems.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Resource Locks and Fast Unlock for Shared Balances in Certificate-Based Payment Systems

DevFeed: [Resource Locks and Fast Unlock for Shared Balances in Certificate-Based Payment Systems](<https://devfeed.tech/articles/resource-locks-and-fast-unlock-for-shared-balances-in-certificate-based-payment-systems-111750.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.41207>)

Author: Lingkang Shangguan

Published: 2026-11-02T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [consistency](<https://devfeed.tech/topics/consistency.md>), [locking](<https://devfeed.tech/topics/locking.md>), [synchronization](<https://devfeed.tech/topics/synchronization.md>), [race-condition](<https://devfeed.tech/topics/race-condition.md>)

Tags: [certificate](<https://devfeed.tech/tags/certificate.md>), [computer](<https://devfeed.tech/tags/computer.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [computing](<https://devfeed.tech/tags/computing.md>), [consensus](<https://devfeed.tech/tags/consensus.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [echo](<https://devfeed.tech/tags/echo.md>), [freeze](<https://devfeed.tech/tags/freeze.md>), [locks](<https://devfeed.tech/tags/locks.md>), [payment](<https://devfeed.tech/tags/payment.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [resource](<https://devfeed.tech/tags/resource.md>), [stablecoin](<https://devfeed.tech/tags/stablecoin.md>), [stablecoin-payments](<https://devfeed.tech/tags/stablecoin-payments.md>), [subscriptions](<https://devfeed.tech/tags/subscriptions.md>), [transactions](<https://devfeed.tech/tags/transactions.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

The abstract argues that safe unlocking of shared balances requires validators to see certificate formation: a quorum certificate kept private by a client could otherwise be overridden during concurrent debits. Its hybrid protocol leaves personal accounts on FastPay's client-driven path, while shared balances have a version number and authorized accounts. Shared-resource transactions go to any validator and use ECHO/READY broadcast; admission requires both the sender's nonce and the resource's nonce to be free. With no contention, the path needs no consensus. If concurrent debits split votes, validators detect the split, freeze that resource version, and use one agreement instance scoped to it; losing transactions regain their sender nonce. The abstract claims consistency, no overdraft, validity, finality, and liveness, and says the protocol composes with PDCC reconfiguration.

### Source excerpt

arXiv:2610.41207v1 Announce Type: new Abstract: Certificate-based payment systems such as FastPay settle a payment with one round of signatures from a quorum of validators and avoid global ordering. The client collects the signatures, and validators never talk to each other. We observe that this client-driven design is complete only as long as no lock is ever undone. Each account has a single writer, a conflict can only come from that writer's own misbehavior, and the account stays locked as the penalty. Stablecoin payments routinely need balances that several accounts debit: treasuries, merchant pools, allowances and subscriptions. There, honest accounts race, locks must be undone, and a quorum certificate held privately by a client can be silently overridden. We prove that no unlock rule is safe in this setting unless certificate formation is visible to validators. We present a hybrid protocol. Personal accounts keep the client-driven FastPay path unchanged. A shared resource is a balance with its own version number and a set of authorized accounts. Transactions on shared resources are submitted to any validator and certified by a two-phase broadcast, ECHO then READY. The admission check requires both the sender's nonce and the resource's nonce to be free. Without contention, this path needs no consensus. When concurrent debits split the votes in any proportion, validators detect the split themselves, freeze the affected resource version, and resolve it with one agreement instance scoped to that version. Losing transactions return their sender nonce. We prove consistency, no overdraft, validity, finality and liveness. The protocol composes with the PDCC reconfiguration protocol.

## Follow the money: Who benefits from the UK's Apple Pay crackdown?

DevFeed: [Follow the money: Who benefits from the UK's Apple Pay crackdown?](<https://devfeed.tech/articles/follow-the-money-who-benefits-from-the-uk-s-apple-pay-crackdown-90843.md>)

Original publisher: [Read original article](<https://www.computerworld.com/article/4237750/follow-the-money-who-benefits-from-the-uks-apple-pay-crackdown.html>)

Author: Jonny Evans

Published: 2026-10-20T10:14:00Z

Content type: opinion

Language: en

Sources: [Computerworld](<https://devfeed.tech/sources/computerworld.md>)

Topics: [Finance](<https://devfeed.tech/topics/finance.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [apple-iphone-mobile-mobile-payment-mobile-phones-smartphones-vendors-and-providers](<https://devfeed.tech/tags/apple-iphone-mobile-mobile-payment-mobile-phones-smartphones-vendors-and-providers.md>), [apple-pay](<https://devfeed.tech/tags/apple-pay.md>), [banks](<https://devfeed.tech/tags/banks.md>), [benefit](<https://devfeed.tech/tags/benefit.md>), [chip](<https://devfeed.tech/tags/chip.md>), [competition](<https://devfeed.tech/tags/competition.md>), [competition-and-markets-authority](<https://devfeed.tech/tags/competition-and-markets-authority.md>), [digital-wallet](<https://devfeed.tech/tags/digital-wallet.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [eu](<https://devfeed.tech/tags/eu.md>), [fintech](<https://devfeed.tech/tags/fintech.md>), [ios](<https://devfeed.tech/tags/ios.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [klarna](<https://devfeed.tech/tags/klarna.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-payment](<https://devfeed.tech/tags/mobile-payment.md>), [mobile-phones](<https://devfeed.tech/tags/mobile-phones.md>), [money](<https://devfeed.tech/tags/money.md>), [nfc](<https://devfeed.tech/tags/nfc.md>), [payment](<https://devfeed.tech/tags/payment.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [payments](<https://devfeed.tech/tags/payments.md>), [paypal](<https://devfeed.tech/tags/paypal.md>), [smartphones](<https://devfeed.tech/tags/smartphones.md>), [storytype-newsanalysis](<https://devfeed.tech/tags/storytype-newsanalysis.md>), [uk](<https://devfeed.tech/tags/uk.md>), [vendors-and-providers](<https://devfeed.tech/tags/vendors-and-providers.md>), [wallet](<https://devfeed.tech/tags/wallet.md>)

### AI overview

The CMA proposes requiring Apple to give rivals fair, reasonable, transparent and non-discriminatory access to iPhone NFC, following complaints that current terms are not commercially viable. The article argues UK banks may be the main beneficiaries, seeking to route payments directly from bank accounts and reduce fees paid to Apple; the expected consumer benefits remain uncertain. It notes that EU NFC access has been used by several cross-border services, while Apple warns that mandated changes could weaken privacy and security. Apple supports secure-element storage on-device; host-based card emulation stores data off-device. In the EU, developers seeking NFC access with HCE need an Apple entitlement and must meet technical, security and regulatory standards, which the author expects could also apply in the UK.

### Source excerpt

The UK wants to take a chunk out of Apple Pay, as the Competition and Markets Authority (CMA) moves to force Apple to open access to its 12-year-old contactless payment system to rivals. The regulator has published a consultation document that proposes requiring Apple to allow competitors to use the near-field communication (NFC) chip on its devices to enable alternative payment systems on iOS on "fair, reasonable, transparent and non-discriminatory terms." The regulator says action is required because UK businesses have complained that Apple's existing NFC access arrangements are not commercially viable. 30% of UK adults use Apple Pay? The regulator also revealed some interesting statistics concerning use of contactless tech in the UK: Contactless payments represent 39% of all payments, compared to just 3% of transactions a decade ago. 62% of adults currently use a digital wallet. 50% of those use Apple Wallet -- which implies that around 30% of UK adults use Apple Pay. "These proposals open the door to more innovation, more choice and economic growth, including in the UK's important fintech sector," said Sarah Cardell, chief executive of the CMA. It's not clear if those companies will take advantage of this forced liberalization. The CMA tells us that the only services that have done so in the EU, where Apple has already been forced to open up NFC, have all been transnational entities, including Vipps, PayPal, Klarna, Curve, and BBVA. Are consumers flocking to these services to rejoice in this new market liberalization? While this open NFC has only been in place a few months, I don't think so. Who will really benefit from this? Cardell also said, "By removing barriers to entry, we can help create the conditions for brilliant British businesses with great ideas to develop new products and services here -- from payment apps and digital IDs to travel passes and digital keys." That seems highly speculative to me, but I can see UK banks offering up digital payments direc

## How Stripe's OpenRouter acquisition could support agent-to-agent commerce

DevFeed: [How Stripe's OpenRouter acquisition could support agent-to-agent commerce](<https://devfeed.tech/articles/the-agent-to-agent-economy-is-closer-than-you-think-88529.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4236020/the-agent-to-agent-economy-is-closer-than-you-think.html>)

Author: Daniel Herrington

Published: 2026-10-16T10:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [API Business Models](<https://devfeed.tech/topics/api-business-models.md>), [API Economy](<https://devfeed.tech/topics/api-economy.md>)

Tags: [agent-to-agent-commerce](<https://devfeed.tech/tags/agent-to-agent-commerce.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-financial-services-industry-fintech-industry-markets-payment-systems-t](<https://devfeed.tech/tags/artificial-intelligence-financial-services-industry-fintech-industry-markets-payment-systems-t.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [financial-services-industry](<https://devfeed.tech/tags/financial-services-industry.md>), [fintech](<https://devfeed.tech/tags/fintech.md>), [industry](<https://devfeed.tech/tags/industry.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [markets](<https://devfeed.tech/tags/markets.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [technology-industry](<https://devfeed.tech/tags/technology-industry.md>)

### AI overview

The opinion argues that Stripe's acquisition of OpenRouter may help connect AI model routing with real-time payment infrastructure, enabling software agents to transact with one another. It outlines obstacles including trust, settlement speed, and microtransaction costs, then considers possible implications for insurance and enterprise products.

### Source excerpt

Stripe recently acquired AI routing platform OpenRouter for a reported $7.5 billion, making it one of the largest venture-backed AI startup exits and fintech M&A deals of the year. It's a blockbuster deal that instantly became one of the most intriguing tech developments to occur this year. Not just because of the dollars involved or the reasons your tech newsfeed or social media timeline insists. The broader perception seems to be that this is just a standard software developer tooling narrative. Financial analysts and tech enthusiasts would have you believe the main takeaways here are the massive acquisition price and Stripe's shiny new resource to lower AI token costs. To many, OpenRouter is simply a tech-savvy developer utility that routes basic prompts to inexpensive AI models while setting aside pricey frontier models for complicated reasoning tasks. Others view it as a way to prevent vendor lock-in from cloud ecosystem giants such as AWS Bedrock. But these perspectives are missing the big picture. From my perspective, it's clear that this acquisition sends a definitive signal about where the future of digital payments is heading - not just the future of artificial intelligence software. While it won't happen overnight, agent-to-agent commerce is clearly opening the floodgates to a paradigm where autonomous software agents will serve as fully empowered economic participants that can conduct business on behalf of both individuals and enterprises. In my line of work, that means we aren't far away from the time when, for example, an automated car insurance agent can eventually meet, negotiate with, evaluate risk for and sell coverage to another company's autonomous agent - with the entire exchange happening seamlessly behind the scenes. From agents that assist to agents that transact Consider how AI agents operate nowadays versus how they will perform in the near future. Today, agents primarily pass context back and forth across software interfaces. Case in point

## Why individually passing readiness tests may still leave a payment platform vulnerable at peak

DevFeed: [Why individually passing readiness tests may still leave a payment platform vulnerable at peak](<https://devfeed.tech/articles/your-payment-platform-can-pass-every-black-friday-readiness-test-and-still-fail-61735.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4227770/your-payment-platform-can-pass-every-black-friday-readiness-test-and-still-fail.html>)

Author: Sayali Patil

Published: 2026-09-29T14:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [payment volume spikes](<https://devfeed.tech/topics/payment-volume-spikes.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [black-friday-and-cyber-monday](<https://devfeed.tech/tags/black-friday-and-cyber-monday.md>), [black-friday-and-cyber-monday-financial-services-industry-fintech-industry-markets-payment-syst](<https://devfeed.tech/tags/black-friday-and-cyber-monday-financial-services-industry-fintech-industry-markets-payment-syst.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [capacity-planning](<https://devfeed.tech/tags/capacity-planning.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [financial-services-industry](<https://devfeed.tech/tags/financial-services-industry.md>), [fintech](<https://devfeed.tech/tags/fintech.md>), [incident](<https://devfeed.tech/tags/incident.md>), [industry](<https://devfeed.tech/tags/industry.md>), [load-testing](<https://devfeed.tech/tags/load-testing.md>), [markets](<https://devfeed.tech/tags/markets.md>), [payment](<https://devfeed.tech/tags/payment.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [shopping](<https://devfeed.tech/tags/shopping.md>), [shopping-occasions](<https://devfeed.tech/tags/shopping-occasions.md>)

### AI overview

Individually tested authorization, fraud, and settlement services can still fail together at peak traffic when they compete for shared capacity and react to one another. The article argues that readiness testing should account for interactions among components under shared stress.

### Source excerpt

Every service in your payment stack can pass its own readiness test in isolation, and checkout can still go down at peak. The problem usually isn't a failed service. It's the shared capacity they all draw against at once. I've sat in more than one Black Friday readiness review that looked like this. Authorization load tested to twice projected peak volume. The fraud engine stress-tested separately, scored well, signed off on its own. Settlement with a documented failover plan. Every team walks out of that room with a green checkmark next to their system, and every checkmark is earned. Nobody cut corners. And more than once, I've watched checkout fail anyway once the real traffic hit. Authorization was healthy. Fraud was healthy. Settlement was healthy. The checkout experience wasn't. Every dashboard the incident channel pulled up looked fine in isolation, the same kind of silent failure I've seen play out in other production systems, just showing up here in payments instead. It's exactly what made the incident hard to diagnose in real time. The assumption underneath every one of those readiness reviews is one I held myself for a long time: that system readiness is the sum of component readiness. If authorization passes, and fraud passes, and settlement passes, the payment platform is ready. It's a reasonable assumption, and it's incomplete in a specific, testable way. A system can be individually ready and collectively unready. Proving that every component survives the load is not the same as proving the transaction survives when every component is under pressure and reacting to the others. Why passing every individual test still leaves you exposed Most organizations already do the conventional peak-season work well: load testing, capacity planning, failover exercises. That work matters, and it isn't the gap. The blind spot sits one layer below it, in what happens when those individually healthy systems interact under the same stress. When it shows up, it isn't a te

## Cell-Based Architecture for Resilient Payment Systems

DevFeed: [Cell-Based Architecture for Resilient Payment Systems](<https://devfeed.tech/articles/cell-based-architecture-for-resilient-payment-systems-56635.md>)

Original publisher: [Read original article](<https://americanexpress.io/cell-based-architecture-for-resilient-payment-systems/>)

Published: 2026-06-11T04:00:00Z

Content type: article

Language: en

Sources: [American Express Technology](<https://devfeed.tech/sources/american-express-technology.md>)

Topics: [cell-based-architecture](<https://devfeed.tech/topics/cell-based-architecture.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [cell-based-architecture](<https://devfeed.tech/tags/cell-based-architecture.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [databases](<https://devfeed.tech/tags/databases.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [latency](<https://devfeed.tech/tags/latency.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [payments](<https://devfeed.tech/tags/payments.md>), [resiliency](<https://devfeed.tech/tags/resiliency.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [scale](<https://devfeed.tech/tags/scale.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

American Express describes how it uses cell-based architecture in a global payments platform to contain failures, reduce blast radius, maintain low-latency processing, and scale capacity without expanding failure domains. The approach groups related microservices, databases, and other components into independent cells.

### Source excerpt

How American Express uses cell-based architecture to deliver resilient, low-latency payments at global scale.

## Unlocking the relational power of graph neural networks in fraud prevention

DevFeed: [Unlocking the relational power of graph neural networks in fraud prevention](<https://devfeed.tech/articles/unlocking-the-relational-power-of-graph-neural-networks-in-fraud-prevention-56967.md>)

Original publisher: [Read original article](<https://www.thoughtworks.com/insights/articles/graph-neural-networks-in-fraud-prevention>)

Author: Alla Gancz, Artiom Troyanovsky, Joao Salcedo, Brian Blanchard, Paul Chang, Georgios Kolovos: Payments and FinTech Leader, Shardul Vaidya, Md Naim, Zachary Jacobson

Published: 2026-03-16T00:00:00Z

Content type: article

Language: en

Sources: [Thoughtworks Insights](<https://devfeed.tech/sources/thoughtworks-insights.md>)

Topics: [Graphs](<https://devfeed.tech/topics/graphs.md>), [Payment Fraud](<https://devfeed.tech/topics/payment-fraud.md>), [Deep neural networks](<https://devfeed.tech/topics/deep-neural-networks.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Security, Privacy and Abuse Prevention](<https://devfeed.tech/topics/security-privacy-and-abuse-prevention.md>)

Tags: [ai-and-ml](<https://devfeed.tech/tags/ai-and-ml.md>), [false-positives](<https://devfeed.tech/tags/false-positives.md>), [financial-services](<https://devfeed.tech/tags/financial-services.md>), [fraud-detection](<https://devfeed.tech/tags/fraud-detection.md>), [graph](<https://devfeed.tech/tags/graph.md>), [inference](<https://devfeed.tech/tags/inference.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [neural-networks](<https://devfeed.tech/tags/neural-networks.md>), [payment-fraud](<https://devfeed.tech/tags/payment-fraud.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

This article describes a fraud-prevention approach that combines graph-based intelligence, neural networks, and AI inference pipelines for real-time payment systems. It explains how payment fraud has evolved from rules-based detection to machine-learning and behavioral approaches, with particular attention to authorized push payment scams and the need for low-latency, explainable detection.

### Source excerpt

Unlocking the relational power of graph neural networks in fraud prevention

## NCMC design and technical limitations

DevFeed: [NCMC design and technical limitations](<https://devfeed.tech/articles/ncmc-design-and-technical-limitations-39787.md>)

Original publisher: [Read original article](<https://anuragbhatia.com/post/2026/ncmc-design-and-limitations/>)

Published: 2026-01-03T18:46:00Z

Content type: opinion

Language: en

Sources: [Personal blog of Anurag Bhatia](<https://devfeed.tech/sources/personal-blog-of-anurag-bhatia.md>)

Topics: [Internet](<https://devfeed.tech/topics/internet.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Risk](<https://devfeed.tech/topics/risk.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [card](<https://devfeed.tech/tags/card.md>), [dmrc](<https://devfeed.tech/tags/dmrc.md>), [internet](<https://devfeed.tech/tags/internet.md>), [ncmc](<https://devfeed.tech/tags/ncmc.md>), [npci](<https://devfeed.tech/tags/npci.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [payments](<https://devfeed.tech/tags/payments.md>)

### AI overview

The article examines India's National Common Mobility Card (NCMC), focusing on its offline-wallet design and how it differs from online UPI and card payments used in other transit systems.

### Source excerpt

I was in Mumbai a few months ago for the Equinix India Peering forum. The event happened to be very near the airport & I found that the airport, conference venue, hotel, and a few other locations I was visiting were all near the newly built Mumbai Line 3 (Aqua Line). To save on hassle with regular tickets, I went for an NCMC (National Common Mobility Card). Most people travelling in the Delhi metro would be aware of it by now, thanks to a bit of marketing push inside the metro train with announcements. Mumbai line 3 has a tie-up with SBI for the card, and thus, I got the SBI card. Ended up using it in Mumbai, Delhi and Chennai over the last few months. Lately, I have been reading about way NCMC works, the limitations of the Indian NCMC design compared to other mass transit systems. In many countries, mass transit systems simply use MasterCard/Visa/Apple Pay tap and charge directly from the respective card (credit/debit card, etc.), like the London tube, Stockholm metro, HK airport express, Singapore, etc. Indian deployment is bit different. Indian NCMC offline wallet concept The whole idea of NCMC is to have a single card which can make payment for public transport, including metro, buses etc across the country digitally. It has to be fast and reliable, and this is where the whole tech differs from systems like UPI or Visa/MasterCard/Rupay POS payments. In case of UPI as well as credit/debit card payments on POS machines - entire transaction runs online. Money goes from the person paying the amount to the receiver as part of a settlement facilitated by NPCI. I don't need to go in detailed steps involved there, but the key idea is that there's an active involvement of 1) Payer's APP 2) Payer's bank 3) Receiver's PSP 4) Receiver's bank 5) NPCI UPI switch, etc. All these have to work and most important - internet has to work. 😀 All this largely works well for casual payments across the vendors, but not for transit payments, especially at metro stations. It easily takes

## Agentic commerce: driving smarter growth with every interaction

DevFeed: [Agentic commerce: driving smarter growth with every interaction](<https://devfeed.tech/articles/agentic-commerce-driving-smarter-growth-with-every-interaction-57193.md>)

Original publisher: [Read original article](<https://www.thoughtworks.com/insights/blog/generative-ai/agentic-commerce-smarter-growth-every-interaction>)

Author: Alla Gancz, Visalakshi Subramaniam, Panagiotis Kriaris

Published: 2025-10-14T00:00:00Z

Content type: article

Language: en

Sources: [Thoughtworks Insights](<https://devfeed.tech/sources/thoughtworks-insights.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Conversational AI](<https://devfeed.tech/topics/conversational-ai.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>), [stripe](<https://devfeed.tech/topics/stripe.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [openai](<https://devfeed.tech/tags/openai.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [payments](<https://devfeed.tech/tags/payments.md>), [stripe](<https://devfeed.tech/tags/stripe.md>)

### AI overview

The article examines agentic commerce, in which autonomous AI agents search for products, tailor recommendations and complete purchases for customers. It discusses how OpenAI and Stripe's instant checkout and Agentic Commerce Protocol affect retail journeys, payments and merchant requirements for authenticating and authorizing agent-initiated transactions.

### Source excerpt

Agentic commerce: driving smarter growth with every interaction

## UK Payments Infrastructure Moves to a New Public-Private Delivery Model

DevFeed: [UK Payments Infrastructure Moves to a New Public-Private Delivery Model](<https://devfeed.tech/articles/a-bold-new-chapter-for-uk-payments-infrastructure-what-s-next-57131.md>)

Original publisher: [Read original article](<https://www.thoughtworks.com/insights/blog/digital-innovation/new-chapter-uk-payments-infrastructure>)

Author: Alla Gancz

Published: 2025-07-18T00:00:00Z

Content type: article

Language: en

Sources: [Thoughtworks Insights](<https://devfeed.tech/sources/thoughtworks-insights.md>)

Topics: [systems](<https://devfeed.tech/topics/systems.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [governance](<https://devfeed.tech/tags/governance.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [operational-resilience](<https://devfeed.tech/tags/operational-resilience.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [plan](<https://devfeed.tech/tags/plan.md>), [policy](<https://devfeed.tech/tags/policy.md>), [procurement](<https://devfeed.tech/tags/procurement.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [security](<https://devfeed.tech/tags/security.md>), [uk](<https://devfeed.tech/tags/uk.md>)

### AI overview

The Bank of England and HM Treasury announced a new delivery model for UK retail payments infrastructure, dividing responsibilities between public authorities and the private sector. The model includes a new Retail Payments Infrastructure Board, an industry-led delivery company, and planned strategic and implementation frameworks.

### Source excerpt

A bold new chapter for UK payments infrastructure: What's next?

## An analysis of the Square and Cash App outage

DevFeed: [An analysis of the Square and Cash App outage](<https://devfeed.tech/articles/an-analysis-of-the-square-and-cash-app-outage-15496.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/an-analysis-of-the-square-and-cash-app-outage>)

Author: Paul Friedman

Published: 2025-03-05T11:00:00Z

Content type: news

Language: en

Sources: [Square Corner](<https://devfeed.tech/sources/square-corner-blog-medium.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [cash-app](<https://devfeed.tech/tags/cash-app.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [databases](<https://devfeed.tech/tags/databases.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [impact](<https://devfeed.tech/tags/impact.md>), [offline](<https://devfeed.tech/tags/offline.md>), [outage](<https://devfeed.tech/tags/outage.md>), [payment](<https://devfeed.tech/tags/payment.md>), [payment-processing](<https://devfeed.tech/tags/payment-processing.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [payments](<https://devfeed.tech/tags/payments.md>), [postmortem](<https://devfeed.tech/tags/postmortem.md>), [public](<https://devfeed.tech/tags/public.md>), [reporting](<https://devfeed.tech/tags/reporting.md>), [service-disruption](<https://devfeed.tech/tags/service-disruption.md>), [square](<https://devfeed.tech/tags/square.md>)

### AI overview

A security certificate bundle update on February 26 caused Square payment systems and Cash App services to lose database connectivity. After monitoring detected elevated errors at 20:00 UTC, the disruption spread to payments at 20:20; the certificate change was rolled back at 20:42. Square enabled offline card-present payments at 20:53, but some sellers had trouble using them. Functionality began recovering at 20:58 and was largely restored by 21:03; lingering reporting issues continued until the incident was resolved at 22:13. Square says it will remove manual certificate-change steps, review certificate processes and deployment surfaces, improve offline payments and its offline playbook, and enhance degraded-service experiences.

### Source excerpt

Service Disruption - Public Postmortem [2025/02/26]

## Building rock-solid Stripe integrations: A developer's guide to success

DevFeed: [Building rock-solid Stripe integrations: A developer's guide to success](<https://devfeed.tech/articles/building-rock-solid-stripe-integrations-a-developer-s-guide-to-success-81744.md>)

Original publisher: [Read original article](<https://stripe.dev/blog/building-solid-stripe-integrations-developers-guide-success>)

Author: James Beswick

Published: 2025-02-06T00:00:00Z

Content type: tutorial

Language: en

Sources: [Stripe Dot Dev Blog](<https://devfeed.tech/sources/stripe-dot-dev-blog.md>)

Topics: [stripe](<https://devfeed.tech/topics/stripe.md>), [API Economy](<https://devfeed.tech/topics/api-economy.md>)

Tags: [payment](<https://devfeed.tech/tags/payment.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [payments](<https://devfeed.tech/tags/payments.md>), [robust](<https://devfeed.tech/tags/robust.md>), [stripe](<https://devfeed.tech/tags/stripe.md>), [subscription](<https://devfeed.tech/tags/subscription.md>)

### AI overview

A developer guide to building Stripe integrations, covering robust and secure payment systems, seamless user experiences, subscription management, and dispute resolution.

### Source excerpt

Learn about Stripe integrations with essential tips for robust, secure payment systems and seamless user experiences. This guide prepares developers for real-world scenarios, from subscription management to dispute resolution, ensuring secure and seamless payments.

## Advanced error handling patterns for Stripe enterprise developers

DevFeed: [Advanced error handling patterns for Stripe enterprise developers](<https://devfeed.tech/articles/advanced-error-handling-patterns-for-stripe-enterprise-developers-81726.md>)

Original publisher: [Read original article](<https://stripe.dev/blog/advanced-error-handling-patterns-for-Stripe-enterprise-developers>)

Author: Ben Smith

Published: 2024-09-03T00:00:00Z

Content type: tutorial

Language: en

Sources: [Stripe Dot Dev Blog](<https://devfeed.tech/sources/stripe-dot-dev-blog.md>)

Topics: [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [stripe](<https://devfeed.tech/topics/stripe.md>)

Tags: [advanced](<https://devfeed.tech/tags/advanced.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [payment-systems](<https://devfeed.tech/tags/payment-systems.md>), [stripe](<https://devfeed.tech/tags/stripe.md>)

### AI overview

The post presents advanced patterns for building resilient Stripe payment systems in enterprise applications. It says these patterns help maintain stability and a smooth user experience as integrations grow in complexity and volume.

### Source excerpt

This post demonstrates some more advanced patterns to help you build resilient and robust payment systems to integrate Stripe with your enterprise applications. As your integration grows in complexity and volume, these patterns become crucial for maintaining system stability and providing a smooth user experience.