Patent 21 / P2P Payment Sessions
01 / 11 US11711421B2
↑↓ navigate  ·  all patents →
Siten Sanghvi  ·  Granted Jul 25, 2023

P2P Payment Sessions

A server-mediated peer-to-peer payment architecture that connects nearby user devices by geolocation proximity, handles the app-not-installed scenario via P2P alert, supports multi-party (3-device) sessions, and completes the transfer by streaming account data to the server — with NFC or Bluetooth as the P2P transport.

US11711421B2Patent
Jun 23, 2021Filed
25 monthsTime to grant
20 Claims / 3 independentScope
1 CitationForward citations
SCROLL TO EXPLORE
Visual patent explainer
02 / The Problem

P2P payments require both parties to have the same app, a phone number, or a shared account link. Proximity alone isn't enough.

Existing P2P payment systems require prior relationship setup: both parties must have the same app installed, have exchanged phone numbers, or have connected accounts in advance. There's no mechanism to discover a nearby device, establish a payment session, and handle the case where the receiving device doesn't have the app — purely based on physical proximity.

Requires Prior SetupBoth parties must have the app installed and exchange identifiers before a proximity-based payment can start — blocking spontaneous transactions between strangers or infrequent contacts
No App-Fallback PathWhen one party doesn't have the app, the session fails entirely — there's no mechanism for the initiating device to alert the other party to install it during the session
Two-Party OnlyMost P2P payment architectures are designed for exactly two parties — group payments at the transaction level (splitting a dinner bill across 3 or 4 people) require separate transactions
03 / The Invention

Proximity discovers the session. The server conducts it. The P2P channel handles what the server can't reach.

The first device establishes a P2P connection with the second device based purely on geolocation proximity — no prior relationship required. The server receives the session initiation request and both parties' account data via streaming. If the second device doesn't have the app, the first device sends an alert through the P2P connection directing installation.

The server then conducts the distribution interaction session — transferring data between the two accounts. Claims 2–5 extend this to three-party sessions: a first device can simultaneously establish P2P sessions with a second and third device, with fallback mechanisms for out-of-range third parties using stored contact information.

04 / Architecture

Geo-proximity establishes the P2P link. The server conducts the transfer.

The architecture separates discovery (P2P, proximity-based) from execution (server-mediated). The P2P channel handles device discovery, app installation alerts, and session initiation signaling. The server receives account data via streaming and performs the actual account-to-account transfer.

Claim 13 and 20 specify the P2P transport: NFC or Bluetooth. Both are short-range, device-to-device protocols — limiting the session to devices that are physically near each other, which serves as a natural verification that both parties intend to transact.

Architecture — US11711421B2
First device: establishes
P2P by geo-proximity
Second device
(NFC or Bluetooth)
First device sends
session request to server
Server initiates
distribution session
Account data streams
to server from device
Server conducts transfer
between accounts
05 / App Install Flow

Second device doesn't have the app? First device alerts it — through the P2P connection.

One of the most technically interesting elements of the patent is the app-not-installed flow (Claim 1). When the first device determines that the distribution interaction application is not installed on the second device, it sends an alert through the already-established P2P connection — the alert contains an instruction to install the application.

This bootstraps a new user into the session without requiring any out-of-band communication (no SMS, no QR code, no email). The P2P channel that was established for the session is used to deliver the installation prompt — maintaining the proximity-bound interaction model end-to-end.

App Install Alert Flow — US11711421B2 Claim 1
1
P2P connection established between first and second device via NFC/Bluetooth proximity check
2
First device determines that the distribution interaction app is NOT installed on the second device
3
Alert transmitted through P2P channel to second device — alert contains installation instruction and app reference
4
Second device installs app — session can now be initiated through the distribution interaction application
5
Server initiates session between both devices — account data streams, transfer conducted
06 / Session Simulator

Two-party, three-party, out-of-range, no-app — the server handles every scenario.

The patent covers four distinct session scenarios across its claims. Select a scenario below to trace the server and device interactions.

Session Scenarios
07 / Three-Party Sessions

Split a payment across three devices in one session — or fall back to stored contact info.

Claims 2–5 extend the architecture to three-party sessions. The first device establishes P2P connections with both a second and third device simultaneously. Account data for all three users streams from the first device to the server, which conducts the full three-way distribution session.

Claim 5 handles the out-of-range scenario: if the third device is beyond the geolocation distance threshold, the P2P connection is established using contact information already stored on the first device — enabling the three-party session even when direct proximity isn't possible for all parties.

Three-Party Session Architecture — US11711421B2

Simultaneous P2P Connections

First device establishes P2P (NFC/Bluetooth) with both second and third devices at the same time. All three must have the app installed.

Three-Way Account Streaming

Account data for all three users streams from the first device to the server — which determines all three accounts and conducts the full three-way transfer.

Out-of-Range Fallback

If third device exceeds the distance threshold, the P2P connection uses contact information stored on the first device — bridging the proximity gap via stored identifiers.

Secondary App Fallback

If the primary app is unavailable on the second device, a third device can participate via a secondary app — enabling mixed-mode multi-party sessions.

08 / Applications

Proximity-native payment sessions for the physical world.

The combination of geo-proximity discovery, P2P app installation bootstrapping, server-mediated account transfer, and multi-party session support creates a payment architecture designed for real-world proximity scenarios — restaurants, events, marketplaces, and group outings.

Use Cases — US11711421B2
Express
Spontaneous P2P Payment User pays a nearby friend for their share of a cab. First device detects second device within Bluetooth range. Both have the app — server initiates session, accounts stream, transfer completes in seconds.
Express
New User Onboarding at Point of Payment First device initiates P2P session with a nearby device that doesn't have the app. Alert sent through P2P channel with install instructions. Second user installs app, session continues — no setup required in advance.
Express
Three-Way Restaurant Split User at dinner establishes P2P with both nearby friends simultaneously. Server conducts three-way distribution session — each party's share deducted from their account in a single server transaction.
Inferred
Apple-Style Secure P2P Streaming Apple's citation (US20230397270A1, Dec 2023) validates the data-streaming session model — applying it to secure audio/video streaming between devices based on state criteria, confirming the architecture's generalizability.
09 / Citations

1 Forward Citation

Cited by Apple Inc. in a 2023 patent on automatically establishing secure connections for streaming audio and video data between devices — directly validating the proximity-based P2P session establishment and account-data-streaming model.

Forward citations confirmed via Google Patents · Jun 22, 2026
Forward Citations (1 of 2 shown)
Apple Inc. US20230397270A1  ·  Dec 7, 2023 Framework for automatically establishing secure connections for streaming audio and video data between devices based on device state criteria
One additional citation omitted. Full list available on Google Patents →
10 / P2P Transport

NFC or Bluetooth — proximity as the trust boundary.

Claims 13 and 20 explicitly specify NFC and Bluetooth as the P2P transport options. Both are short-range technologies — NFC operates within centimeters, Bluetooth within meters. This physical proximity constraint functions as an implicit trust signal: only devices that are physically co-located can initiate a session.

This architectural choice distinguishes the patent's model from internet-based P2P payments, where two parties at opposite ends of the world can transact. The patent's system is specifically designed for the physical-world proximity case — the same design space as contactless payment terminals, but applied to device-to-device sessions.

P2P Transport Properties — US11711421B2

NFC Transport

Near-field communication — effective range ~4cm. Tap-to-connect model. Strongest proximity guarantee; used in contactless payment terminals worldwide.

Bluetooth Transport

Effective range ~10m. Enables connection without physical touch. Supports the three-party scenario where all three devices need simultaneous P2P connections.

Proximity as Trust Signal

Physical co-location is a natural fraud barrier — a device that isn't physically present can't initiate a geo-proximity-based P2P session.

Distance Threshold

The patent specifies a configurable distance threshold for the proximity check — enabling different range requirements for different session types or security levels.

11 / Timeline

Patent Lifecycle

Jun 23, 2021
Filed
Application filed — B2 patent
18 months
Dec 29, 2022
Published
Pre-grant publication US20220417322A1
7 months
Jul 25, 2023
Granted
US11711421B2 granted — 25 months from filing
~18 years
Jun 23, 2041
Expires
Est. expiration (subject to maintenance fees)
End / Patent 21