US 2026/0268302 A1Published application

Permission Management Via Mobile Payment Application

AssigneeBlock, Inc.

InventorsAyokunle Omojola, Sean Slinsky, Marcelo Cortes, Daniele Perito, Daniel Federman, Pritesh Bodalia, Deepkarn Bedi

Life of this patent

Estimating the term…

patentgrep

Loading patent…

Abstract

Permission management via a mobile payment application is described. A first request to authorize an account of a customer for payment a transaction between the customer and a third-party merchant can be received from a third-party application. Based on the first request indicating that the third-party merchant is permitted to store payment data associated with the account of the customer for processing payment(s) for future transaction(s), a token can be sent to the third-party merchant to be stored for processing the payment(s) for the future transaction(s). A user interface presented via an instance of a mobile payment application, associated with the payment service, on a computing device of the customer, can enable the customer to manage permission(s) associated with the token. A permission associated with the token can be modified based at least in part on receiving a second request via the mobile payment application.

Claims20

Dependent claims

A method, implemented by at least one server of a payment service, comprising:

receiving, from a third-party application associated with a third-party merchant, a first request to authorize an account of a customer for payment of at least a transaction between the customer and the third-party merchant;
sending, to the third-party application and based at least in part on the first request indicating that the third-party merchant is permitted to store payment data associated with the account of the customer for processing one or more payments for one or more future transactions, a token to be stored for processing the one or more payments for the one or more future transactions without the customer having to provide the payment data in association with the one or more future transactions;
causing a user interface to be presented via an instance of a mobile payment application, associated with the payment service, on a computing device of the customer, wherein the user interface enables the customer to manage one or more permissions associated with the token;
receiving, from the computing device of the customer and via an interaction with the user interface, a second request to modify a permission of the one or more permissions associated with the token;
and
modifying the permission associated with the token based at least in part on the second request.

3 more elements

A system associated with a payment service, the system comprising:

one or more processors;
and
one or more computer-readable media storing instructions that, when executed by the one or more processors, cause the system to perform operations comprising:
receiving, from a third-party application associated with a third-party merchant, a first request to authorize an account of a customer for payment of at least a transaction between the customer and the third-party merchant;
sending, to the third-party application and based at least in part on the first request indicating that the third-party merchant is permitted to store payment data associated with the account of the customer for processing one or more payments for one or more future transactions, a token to be stored for processing the one or more payments for the one or more future transactions without the customer having to provide the payment data in association with the one or more future transactions;
causing a user interface to be presented via an instance of a mobile payment application, associated with the payment service, on a computing device of the customer, wherein the user interface enables the customer to manage one or more permissions associated with the token;
receiving, from the computing device of the customer and via an interaction with the user interface, a second request to modify a permission of the one or more permissions associated with the token;
and
modifying the permission associated with the token based at least in part on the second request.

6 more elements

One or more computer-readable media storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

receiving, from third-party application associated with a third-party merchant, a first request to authorize an account of a customer for payment of at least a transaction between the customer and the third-party merchant;
sending, to the third-party application and based at least in part on the first request indicating that the third-party merchant is permitted to store payment data associated with the account of the customer for processing one or more payments for one or more future transactions, a token to be stored for processing the one or more payments for the one or more future transactions without the customer having to provide the payment data in association with the one or more future transactions;
causing a user interface to be presented via an instance of a mobile payment application, associated with a payment service, on a computing device of the customer, wherein the user interface enables the customer to manage one or more permissions associated with the token;
receiving, from the computing device of the customer and via an interaction with the user interface, a second request to modify a permission of the one or more permissions associated with the token;
and
modifying the permission associated with the token based at least in part on the second request.

3 more elements

Dependencies are inferred from the claim text.

Facts

Application: 19/462,914Filed 28 Jan 2026
Priority: 30 Sep 2015
Published: 10 Sep 2026
Term ends: Not estimatedThe source records don’t support an estimate.

Classification8 codes

G06Q 20/322
Using wireless devices: aspects of commerce using mobile devices [M-devices]
G06Q 20/02
Payment architectures, schemes or protocols: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
G06Q 20/12
Payment architectures: specially adapted for electronic shopping systems
G06Q 20/32
Characterised by the use of specific devices or networks: using wireless devices

Family

Application14/871,576Continuation · filed 30 Sep 2015
Application14/946,544Continuation · filed 19 Nov 2015
Application17/063,975Continuation · filed 6 Oct 2020
Application19/462,914Continuation
US 10,467,615 B1Related patent
US 10,810,592 B1Related patent
US 12,572,919 B2Related patent
US 2021/0019755 A1Published application
US 2026/0268302 A1This patent

From the US filing history. Foreign family members aren’t listed.