Open USD moves the stablecoin fight from issuing the coin to distributing it visual preview
By Navin AgrawalPayments3 min read

Open USD moves the stablecoin fight from issuing the coin to distributing it

Open Standard announced Open USD on June 30, 2026 with a partner-backed model: no-fee mint and redeem, no volume caps, and reserve economics shared with the businesses moving the money. The technical object is another dollar stablecoin. The strategic move is shifting the revenue fight from holding the reserves to distributing the rail.

Stablecoin payments have an architecture answer and no operations answer visual preview
By Navin AgrawalPayments3 min read

Stablecoin payments have an architecture answer and no operations answer

At 3:17 AM the confirmation never arrived. Two million in institutional stablecoin, and the custody record said complete, the counterparty said pending, the smart contract said something else again. The regulatory stack is finally coherent. The exception playbook that ACH and wires spent decades building does not exist yet, and that gap is where institutions are walking in.

Sanctions screening as code: one policy, a different actuator per rail visual preview
By Navin AgrawalPayments3 min read

Sanctions screening as code: one policy, a different actuator per rail

The payment is final in under a second and your sanctions analyst is still opening the alert. On an instant rail there is no review window, so the screen has to clear or stop the payment in code, inside the latency budget. The policy model can be common across rails. The action on a hit cannot, because RTP, the card networks, and SEPA Instant each demand a different commit semantic.

Under a second is the right answer to the wrong question visual preview
By Navin AgrawalPayments3 min read

Under a second is the right answer to the wrong question

At an AWS Bedrock AgentCore Payments session the question was what happens at a thousand transactions a second, and the answer was settlement in under a second. Both are true and they answer different questions. The right frame for one payment crossing a trust boundary is the wrong frame for a million events a day inside one agent fleet, where the chain fee stacks up before anything else does.