US-20260127582-A1 - System, Method, and Device for Device-Agnostic Services

US20260127582A1US 20260127582 A1US20260127582 A1US 20260127582A1US-20260127582-A1

Abstract

A system and method provide device agnostic services. The method includes providing a device agnostic gateway having a channel to communicate with a transaction device, the device agnostic gateway positioned between the transaction device and a transaction participant system. The method also includes receiving, from a client device, a request to complete a transaction, the request comprising identifying information and, by the transaction device, processing the request to complete the transaction via a service provider, the transaction requiring the transaction participant system. The method also includes receiving a token based on the identifying information of the first request and provide the token to the device agnostic gateway; transmitting, with the device agnostic gateway, the token to a subsystem of the transaction participant system to associate the token with transaction details of the transaction available to the transaction participant system; and providing, via the device agnostic gateway, the transaction details in response to receiving the identifying information.

Inventors

Arash DELJAVAN FARSHI

Assignees

THE TORONTO-DOMINION BANK

Dates

Publication Date: 20260507
Application Date: 20241101

Claims (20)

1 . A system for providing device agnostic services, the system comprising: a transaction device; a transaction participant system; a processor; and a memory coupled to the processor, the memory storing computer executable instructions that when executed by the processor cause the system to: provide a device agnostic gateway comprising a service gateway, a device proxy, and a web proxy, wherein the service gateway enables communication between the transaction device and an authorization service, and wherein the device proxy and the web proxy provide a communication channel between the transaction device and the transaction participant system; receive, from a client device, a request to complete a transaction, the request comprising identifying information; by the transaction device, process the request to complete the transaction via a service provider, the transaction requiring the transaction participant system; receive a token based on the identifying information of the request and provide the token to the device agnostic gateway; transmit, with the device agnostic gateway, the token to a subsystem of the transaction participant system; store, in the subsystem, the token in association with transaction details of the transaction available to the transaction participant system; and provide, via the transaction participant system, the transaction details in response to receiving the identifying information.
2 . The system of claim 1 , wherein the token is generated by the service provider and the identifying information comprises sensitive payment information.
3 . The system of claim 1 , wherein the transaction device is a point of sale device, the transaction participant system is a financial institution, and the transaction details include a digital receipt.
4 . The system of claim 1 , wherein the transaction device is configured to process the transaction prior to receiving the token.
5 . The system of claim 1 , wherein the transaction is completed via another channel, and the token is provided to the device agnostic gateway via the communication channel.
6 . The system of claim 5 , wherein the device agnostic gateway parses traffic received via the communication channel and determines whether the transaction device is authenticated for the device agnostic gateway.
7 . The system of claim 1 , wherein the transaction details are provided automatically in response to the token being submitted to the subsystem.
8 . The system of claim 1 , wherein the instructions cause the system to: receive a subsequent request comprising subsequent identifying information for the transaction details from a further device; query the service provider for a subsequent token based on the subsequent identifying information; and in response to determining that the subsequent token matches the token, provide the further device with the transaction details.
9 . The system of claim 8 , wherein the instructions cause the system to: store transaction details in a database on the subsystem in association with the token; and in response to the subsequent token matching the token, return stored transaction details in the database.
10 . The system of claim 1 , further comprising a notification system responsible for managing notification preferences, wherein the instructions cause the system to: in response to the subsystem receiving the token, transmitting, by the subsystem, a notification to the notification system.
11 . The system of claim 10 , wherein the notification system generates a notification with the transaction details and transmits the notification with the transaction details to a client device associated with the token.
12 . The system of claim 10 , wherein the notification system is an event notification system for the transaction participant system, and the event notification system transmits notifications via a selected channel with the transaction details.
13 . The system of claim 1 , wherein the device agnostic gateway provides another channel for communication with client devices for subsequent requests for the transaction details.
14 . A method for providing device agnostic services, the method comprising: providing a device agnostic gateway comprising a service gateway, a device proxy, and a web proxy, wherein the service gateway enables communication between the transaction device and an authorization service, and wherein the device proxy and the web proxy provide a communication channel between a transaction device and a transaction participant system; receiving, from a client device, a request to complete a transaction, the request comprising identifying information; by the transaction device, processing the request to complete the transaction via a service provider, the transaction requiring the transaction participant system; receiving a token based on the identifying information of the request and provide the token to the device agnostic gateway; transmitting, with the device agnostic gateway, the token to a subsystem of the transaction participant system; storing, in the subsystem, the token in association with transaction details of the transaction available to the transaction participant system; and providing, via the transaction participant system, the transaction details in response to receiving the identifying information.
15 . The method of claim 14 , wherein the token is generated by the service provider and the identifying information comprises sensitive payment information.
16 . The method of claim 15 , wherein the transaction device is a point of sale device, the transaction participant system is a financial institution, and the transaction details include a digital receipt.
17 . The method of claim 14 , wherein the transaction device is configured to process the transaction prior to receiving the token.
18 . The method of claim 14 , comprising: receiving a subsequent request comprising subsequent identifying information for the transaction details from a further device; querying the service provider for a subsequent token based on the subsequent identifying information; and in response to determining that the subsequent token matches the token, provide the further device with the transaction details.
19 . The method of claim 14 , wherein the device agnostic gateway provides another channel for communication with client devices for subsequent requests for the transaction details.
20 . (canceled)

Description

TECHNICAL FIELD The following relates generally to methods for device-agnostic services. BACKGROUND Many existing services are found to be fragmented. Some existing service providers create relatively closed ecosystems, whether via hardware or software, where communication between different aspects of, or between, service(s) is/are difficult. Technological change also creates interrelationships between aspects of a service that did not exist beforehand, which legacy technical infrastructure does not support. Some services or aspects of a service are required to respond to regulatory regimes (e.g., also managing sensitive information) which can require technical infrastructure that is difficult to navigate or access. From a customer's point of view, the fragmentation leads to an undesirable opacity. Managing the data access of various service providers, navigating the various service providers to access of service, managing the technical requirements of the various service providers, can be difficult when customers lack insight into the process, or the market requires them to use the fragmented service(s). In one example, merchants may use point-of-sale (POS) devices that are sold and supported by various financial institutions, or POS devices that are supported by a third party, etc. Such POS devices accept payments from accounts that are either part of that financial institution or from another financial institution. These POS devices can include proprietary software or vendor configurations, or themselves may be vendor specific. Retail customers of the merchants therefore are unable to understand how their data is used, have a difficult time collating data from different service providers, etc. The merchant can have difficulty maintaining different services from different service providers. From the retail customer's perspective, to use an example, getting a consistent digital receipt from different merchants may require the use of a plurality of applications, and they may be uncertain as to what personal information is being collected by the various applications. Existing solutions include “digital receipts” being provided by the merchant (e.g., by emailing a copy) using a separate system. BRIEF DESCRIPTION OF THE DRAWINGS Embodiments will now be described with reference to the appended drawings wherein: FIG. 1 is a schematic diagram of an example computing environment. FIG. 2 is a block diagram illustrating an example framework for providing device agnostic services. FIG. 3 is a block diagram illustrating additional details of the example framework for providing device agnostic services. FIG. 4 is a flow chart illustrating operations that may be performed in providing device agnostic services. FIG. 5 is a flow chart illustrating operations that may be performed in processing a subsequent request for transaction details. FIG. 6 is a flow chart illustrating operations that may be performed in token matching for returning stored transaction details. FIG. 7 is a flow chart illustrating operations that may be performed in sending a notification to an event notification system. FIG. 8 is a block diagram of an example configuration of a digital receipt service. FIG. 9 is a block diagram of an example configuration of an enterprise system. FIG. 10 is a block diagram of an example configuration of a computing device such as a POS device or a client computing device associated with a user, customer, or client. DETAILED DESCRIPTION It will be appreciated that for simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth to provide a thorough understanding of the example embodiments described herein. However, it will be understood by those of ordinary skill in the art that the example embodiments described herein may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the example embodiments described herein. Also, the description is not to be considered as limiting the scope of the example embodiments described herein. It will be appreciated that the use of singular terms such as “a” or “an,” in this description is not intended to be limited to instances of solely one object, unless explicitly recited as such. That is, for ease of reference and/or simplicity, the description, for example, may use the term “a” to represent a or multiple components. Similarly, the use of plural terminology, is not intended to limit this disclosure to aspects where multiple (as compared to singular) components are required. For example, “various servers” can refer to a single server, multiple servers of the same kind, or multiple servers of different kinds, etc. There is found to be no seamless experience for customers to re-issue digital receipts or set th