Data sharing platform

• US 10,089,632 B2
• Filed: 07/26/2015
• Issued: 10/02/2018
• Est. Priority Date: 09/19/2012
• Status: Active Grant

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: Hosp, Adam Kenneth
• Primary Examiner(s): Poinvil, Frantzy
• Application Number:
  US14/809,224
• Publication Number:
  US 20150332276A1
• Time in Patent Office: 1,164 Days
• Field of Search: 705 3- 44
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/22 Payment schemes or models
• CPC Class Codes: G06Q 20/384 using social networks
• CPC Class Codes: G06Q 20/4015 using location information
• CPC Class Codes: G06Q 20/42 Confirmation, e.g. check or permission by the legal debtor of payment
• CPC Class Codes: G06Q 50/01 Social networking

Abstract

A data sharing platform can be used to implement a method for allowing at least one entity which makes payments with a payment network to share transaction data. A database containing the transaction data from the at least one entity which makes payments with the payment network is maintained. A user interface is provided, which presents the at least one entity which makes payments with the payment network with at least one selection providing consent to sharing of at least a portion of the transaction data with at least one third party. The consent from the at least one entity which makes payments with the payment network is obtained, via the at least one selection. Interfacing takes place with the at least one third party to share the at least portion of the transaction data.

Claims

1. A method for sharing transaction data by a switching node within a payment network, said method comprising the steps of:

maintaining, by said switching node within said payment network, a database populated with said transaction data received from a plurality of entities, wherein said transaction data corresponds to payments made by at least one entity of said plurality of entities using said payment network;

maintaining, by said switching node, consent data provided by said at least one entity, said consent data providing consent to share at least a portion of said transaction data with a third party;

maintaining, by said switching node, a registered user database storing a table including a list of registered users that have provided consent data including said at least one entity, a data sharing preference of said at least one entity and a secure token associated with said at least one entity;

receiving, by said switching node, a copy of said secure token from said third party via a third party interface module and a network;

granting, by said switching node, said third party access to said transaction data of said at least one entity associated with said secure token upon matching said copy of said secure token to said secure token stored in said registered user database;

filtering, by said switching node, said transaction data using said data sharing preference to obtain said portion of said transaction data; and

interfacing, by said switching node, with said third party via said third party interface module and said network, to publish said portion of said transaction data via said third party.

2. The method of claim 1, further comprising providing a user interface, accessed via said network, which presents said at least one entity of said plurality of entities which makes payments with said payment network with at least one selection providing consent to share said portion of said transaction data with said third party.

3. The method of claim 2, wherein, in said providing step, said at least one selection comprises:

a merchant identity corresponding to said third party;

said merchant identity corresponding to said third party plus a transaction date;

said merchant identity corresponding to said third party plus said transaction date plus an amount.

4. The method of claim 3, wherein, in said providing step, said at least one selection further comprises item level data.

5. The method of claim 1, where said third party is a social network server.

6. The method of claim 5, further comprising:

obtaining social network activity data from said social network server for said at least one entity which makes payments with said payment network; and

integrating said social network activity data and given records of said transaction data, to obtain integrated social media transaction visualization data.

7. The method of claim 6, further comprising providing to said third party at least one of an offer and a prediction based on said integrated data.

8. The method of claim 1, wherein said interfacing is established using an application program interface at said third party.

9. A system configured to share transaction data, said system comprising:

a memory;

at least one processor operatively coupled to said memory; and

a persistent storage device operatively coupled to said memory and storing in a non-transitory manner instructions which when loaded into said memory cause said at least one processor to be operative to;

maintain a database containing populated with said transaction data received from a plurality of entities, wherein said transaction data corresponds to payments made by at least one entity of said plurality of entities using a payment network;

maintain a database containing consent data provided by said at least one entity, said consent data providing consent to share at least a portion of said transaction data with a third party;

maintain a registered user database storing a table including a list of registered users that have provided consent data including said at least one entity, a data sharing preference of said at least one entity and a secure token associated with said at least one entity;

receive a copy of said secure token from said third party via a third party interface module and a network;

grant said third party access to said transaction data of said at least one entity associated with said secure token upon matching said copy of said secure token to said secure token stored in said registered user database;

filter said transaction data using said data sharing preference to obtain said portion of said transaction data; and

interface with said third party via said third party interface module and said network, to publish said portion of said transaction data via said third party.

10. The system of claim 9, further comprising a user interface which presents said at least one entity of said plurality of entities which makes payments with said payment network with at least one selection providing consent to sharing of said portion of said transaction data with said third party.

11. The system of claim 10, wherein said at least one selection comprises:

a merchant identity corresponding to said third party;

said merchant identity corresponding to said third party plus a transaction date;

said merchant identity corresponding to said third party plus said transaction date plus an amount.

12. The system of claim 11, wherein said at least one selection further comprises item level data.

13. The system of claim 9, where said third party is a social network server.

14. The system of claim 13, wherein said persistent storage device further stores in a non-transitory manner instructions which when loaded into said memory cause said at least one processor to be further operative to:

obtain social network activity data from said social network server for said at least one entity which makes payments with said payment network; and

integrate said social network activity data and given records of said transaction data, to obtain integrated social media transaction visualization data.

15. The system of claim 9, wherein said persistent storage device further stores in a non-transitory manner instructions which when loaded into said memory cause said at least one processor to be further operative to provide to said third party at least one of an offer and a prediction based on said integrated data.

16. The system of claim 9, wherein said instructions on said persistent storage device comprise distinct software modules, and wherein said distinct software modules comprise a database module, a user interface module, and said third party interface module;

wherein;

said database module comprises said instructions which cause said at least one processor to maintain said database;

said user interface module comprises said instructions which cause said at least one processor to provide a user interface and maintain said consent data; and

said third party interface module comprises said instructions which cause said at least one processor to interface with said third party.