On June 25, 2026 a patent application published that is directed at one of the harder problems in on-chain payments: moving value between two blockchains that do not, by themselves, talk to each other. Titled "Universal Payment Channel," the application is assigned to Visa International Service Association and carried at US20260179065A1. Before reading the scope, the label that matters: this is a published application, not a granted patent. It records what Visa filed and asked an examiner to consider, not anything it can yet enforce. With that fixed, the question worth asking is exactly what the independent claim recites.

In plain terms, the application is directed to a hub computer that brokers a cross-chain swap. A first service provider computer — in communication with a first user device and a first blockchain network — deploys a first smart contract on that first chain in response to its own request, and that contract "implements" an interaction channel between the service provider and the hub. A second service provider computer does the same on a second blockchain with a second smart contract. The hub sits in the middle. It never asks the two chains to interoperate directly; instead, each side talks to the hub through a smart-contract-mediated channel on its own chain, and the hub reconciles the two legs.

The mechanics the claim recites are a hashed-secret exchange. The first service provider generates a "sender promise" comprising a first amount of a first digital currency, a set of first parameters — including a hashed secret, an interaction-channel identifier, and the local state of the first smart contract — and a digital signature over those parameters. It transmits that promise to the hub through the first interaction channel. The hub verifies the signature, generates a corresponding "server promise" comprising a second amount of a second digital currency, and transmits that to the second service provider. The first service provider then receives the secret behind the hashed secret, verifies it by re-hashing and comparing, and issues a "server receipt" carrying the updated local state of its smart contract. A "receiver receipt" referencing the second smart contract is issued to the second service provider on the other chain.

The hub computer can also receive a second user account identifier from a second service provider computer in communication with a second user device, and also a second blockchain network containing a second smart contract. The hub computer may receive a first amount of a first digital currency from the first service provider computer, and may then transfer a second amount of a second digital currency to the second service provider computer.— Universal Payment Channel, US20260179065A1

What claim 1 captures — and what it conspicuously limits

Two limitations in the independent claim do real work. First, the claim expressly recites that "the first digital currency is different from the second digital currency." The claimed system is not a same-asset transfer that merely spans two chains; it captures a cross-currency swap brokered by the hub. Second, the claim recites that the first smart contract "connects the first service provider computer to the hub computer without connection to a first blockchain" — the interaction channel is the unit of coordination, and the contract is deployed on demand, in response to the service provider's request, to implement that channel. The hashed-secret-and-reveal structure is the familiar conditional-settlement pattern of payment-channel designs: the secret links the two legs so that the second leg can only settle once the first is committed. Read literally, the claim is directed to that two-sided, hub-mediated, hashed-secret swap between differing digital currencies, not to any cross-chain bridge in general.

The classification is consistent with that reading. The application carries a main CPC classification of G06Q 20/389 — within G06Q 20/ (payment architectures, schemes and protocols), the subclass for protocols involving an intermediary or clearing house. That is a deliberately payments-architecture placement rather than an H04L 9/ cryptographic-mechanism placement: the disclosed contribution the examiner is being asked to consider is the settlement architecture — the hub, the channels, the promise-and-receipt flow — not a new cryptographic primitive. The hashing is a building block; the claimed invention is the intermediary scheme that uses it.

A cluster directed at moving tokens across and within chains

The hero does not publish alone. It lands in a same-day Visa cluster whose throughline is the plumbing of multi-token, multi-chain value movement — the operational problems a cross-chain hub creates once it exists. US20260179088A1, "Multi-Blockchain Token Rebalancer," is directed to holding a target ratio of a token across several blockchains: it measures the current amount on a chain, generates a ratio, compares it to the target, and executes a rebalancing transaction to bring the chain back toward target. A hub that swaps currencies across chains accumulates and depletes inventory on each side; a rebalancer is the corollary mechanism that keeps that inventory in line.

Two further filings in the cluster are directed at the cost and reversibility of moving tokens. US20260179066A1, "Decoupling Native and Non-Native Tokens in Blockchain Transactions," is directed to a relay service that lets a transfer of one token incur its transaction overhead (gas) in a second token, retrieved per a policy, "without transferring the second type of token from the transmitter wallet" — separating the asset being moved from the asset paying the fee. US20260179082A1, "Executing Transactions in Blockchain Systems via Token Pools with Convertible Tokens," is directed to aggregating tokens from many wallets into a global pool and exchanging a first token for a second based on the pool's ratio — a pooled-conversion mechanism for reversible transactions. Both read as components of a system that has to convert between token types as a matter of routine.

The cluster's fifth member turns to custody. US20260179083A1, "End-User Controlled Wallets in Blockchain Systems," is directed to splitting a private key into portions: a first portion decrypted from an authorization code and a salt tied to user credentials, a second portion decrypted from credentials tied to the application, with access granted only on both — a key-splitting scheme so a service provider can mediate wallet access without holding the whole key. Taken together, the five applications sketch the pieces an intermediary needs to run cross-chain digital-currency payments at scale: a hub to broker the swap, a rebalancer to manage inventory, fee-token decoupling and convertible pools to handle the economics, and split-key wallets to handle custody.

What the hero application claims, then, is narrower and more specific than "a blockchain bridge": a hub computer that uses an on-demand smart contract on each of two blockchains to open per-chain interaction channels, passes a signed, hashed-secret promise through them, and settles by swapping a first digital currency for a different second digital currency. Whether the claims that ultimately issue track this published language is a question for prosecution, and the scope an examiner allows may be narrower than the disclosure reads. For the record as filed, the coverage is plain on its face under G06Q 20/389, and its company is unambiguous — it published alongside a set of Visa applications directed, repeatedly, at the mechanics of moving tokens between and within blockchains.