COMPUTER SYSTEM AND COMPUTER-IMPLEMENTED METHOD FOR PURCHASING AT LEAST ONE TICKET TO AN EVENT

• US 20190325404A1
• Filed: 04/22/2019
• Published: 10/24/2019
• Est. Priority Date: 04/23/2018
• Status: Abandoned Application

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: GUPTA, Sudhir, AGRAWAL, Rahul, PIPARSANIYA, Harsh
• Application Number:
  US16/390,252
• Publication Number:
  US 20190325404A1
• Time in Patent Office: Days
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 20/045 using payment protocols involving tickets
• CPC Class Codes: G06Q 20/0457 the tickets being sent electronically
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/3274 using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G10L 15/26 Speech to text systems G10L15/08 takes precedence

Abstract

A payment network server for processing a payment transaction for at least one ticket to an event is described. The server comprises a transaction module, an authorisation module and an access verification module. The transaction module is configured to: (i) receive a payment transaction request comprising at least a customer account identifier and a payment amount from a customer electronic device; and (ii) transmit a payment transaction response comprising at least the transaction identifier to the customer electronic device. The authorisation module is configured to transmit a request for authorisation to proceed with the payment transaction to an issuer server, where the request for authorisation comprises at least the customer account identifier and the payment amount, and where the payment amount is blocked in a customer account associated with the customer account identifier if the payment transaction is authorised. The access verification module is configured to: (i) transmit a speakeasy request comprising a request for a speakeasy password to the customer electronic device if the payment transaction is authorised; (ii) receive the speakeasy password from the customer electronic device; (iii) generate a transaction identifier which is associated with the payment transaction; and (iv) store the transaction identifier and the speakeasy password at a payment network database, where the speakeasy password is associated with the transaction identifier.

Claims

1. A payment network server for processing a payment transaction for at least one ticket to an event, the payment network server comprising:

a transaction module configured to;

receive, from a customer electronic device, a payment transaction request comprising at least a customer account identifier and a payment amount; and

transmit, to the customer electronic device, a payment transaction response comprising at least the transaction identifier;

an authorisation module configured to;

transmit, to an issuer server, a request for authorisation to proceed with the payment transaction, wherein the request for authorisation comprises at least the customer account identifier and the payment amount, and wherein the payment amount is blocked in a customer account associated with the customer account identifier if the payment transaction is authorised; and

receive, from the issuer server, an authorisation response indicating if the payment transaction is authorised or refused; and

an access verification module configured to;

transmit, to the customer electronic device, a speakeasy request comprising a request for a speakeasy password if the payment transaction is authorised;

receive, from the customer electronic device, a speakeasy response comprising the speakeasy password;

generate a transaction identifier, the transaction identifier being associated with the payment transaction; and

store, using a payment network database, the transaction identifier and the speakeasy password, wherein the speakeasy password is associated with the transaction identifier.

2. The server of claim 1 further comprising:

a ticket utilisation module configured to;

receive, from an invitee electronic device via a merchant server, a ticket utilisation request comprising at least the transaction identifier;

transmit, to the invitee electronic device, a speakeasy confirmation request comprising a request for a speakeasy password input;

receive, from the invitee electronic device, a speakeasy confirmation response comprising at least the speakeasy password input;

verify, using the payment network database, the speakeasy password input, the speakeasy password input is verified if the speakeasy password input matches the speakeasy password associated with the transaction identifier; and

transmit, to the merchant server, a ticket utilisation response indicating if utilisation of the ticket is approved or refused, the utilisation of the ticket is approved if the speakeasy password input is verified.

3. The server of claim 2, wherein when the ticket is utilised by the invitee, the transaction module is further configured to:

transmit, to the issuer server, a fund transfer request to transfer at least a portion of the payment amount for the payment transaction, the fund transfer request comprising at least the transaction identifier and a transfer amount, the transfer amount being associated with at least a cost of the ticket used by the invitee to participate in the event; and

receive, from the issuer server, a fund transfer response indicating whether the fund transfer request is approved or refused.

4. The server of claim 2, wherein when the ticket is utilised by the invitee, the transaction module is further configured to:

receive, from the merchant server, a fund transfer request comprising a request to transfer at least a portion of the payment amount for the payment transaction, the fund transfer request comprising at least the transaction identifier and a transfer amount, the transfer amount being associated with at least a cost of the ticket used by the invitee to participate in the event;

transmit, to the issuer server, the fund transfer request to transfer at least the transfer amount; and

receive, from the issuer server, a fund transfer response indicating whether the fund transfer request is approved or refused.

5. The server of claim 1 further comprising:

a distribution module configured to;

receive, from the customer electronic device, invitee details associated with at least one invitee invited to participate in the event, the invitee details comprising at least an invitee contact; and

transmit, to each invitee electronic device associated with the at least one invitee using the invitee contact, the transaction identifier and the speakeasy password.

6. The server of claim 5, wherein the invitee contact is one of a mobile number or an electronic mail address.

7. The server of claim 1, wherein the speakeasy password comprises a string of numbers, symbols or alphanumeric characters.

8. The server of claim 1, wherein the speakeasy password received via the customer electronic device is in the form of a speech.

9. The server of claim 1, wherein the transaction identifier is one of the following:

a Quick Response (QR) code, a barcode, an EZcode, a high capacity color barcode, a ShotCode, a MaxiCode, a GTIN12 code, a GTIN-13 code, an Aztec code, a name and a mobile number.

10. A computer-implemented method for processing a payment transaction for at least one ticket to an event, the method comprising:

receiving, from a customer electronic device, a payment transaction request comprising at least a customer account identifier and a payment amount;

transmitting, to an issuer server, a request for authorisation to proceed with the payment transaction, wherein the request for authorisation comprises at least the customer account identifier and the payment amount, and wherein the payment amount is blocked in a customer account associated with the customer account identifier if the payment transaction is authorised;

receiving, from the issuer server, an authorisation response indicating if the payment transaction is authorised or refused;

transmitting, to the customer electronic device, a speakeasy request comprising a request for a speakeasy password if the payment transaction is authorised;

receiving, from the customer electronic device, a speakeasy response comprising the speakeasy password;

generating a transaction identifier, the transaction identifier being associated with the payment transaction;

storing, using a payment network database, the transaction identifier and the speakeasy password, wherein the speakeasy password is associated with the transaction identifier; and

transmitting, to the customer electronic device, a payment transaction response comprising at least the transaction identifier.

11. The method of claim 10 further comprising:

receiving, from an invitee electronic device via a merchant server, a ticket utilisation request comprising at least the transaction identifier;

transmitting, to the invitee electronic device, a speakeasy confirmation request comprising a request for a speakeasy password input;

receiving, from the invitee electronic device, a speakeasy confirmation response comprising at least the speakeasy password input;

verifying, using the payment network database, the speakeasy password input, the speakeasy password input is verified if the speakeasy password input matches the speakeasy password associated with the transaction identifier; and

transmitting, to the merchant server, a ticket utilisation response indicating if utilisation of the ticket is approved or refused, the utilisation of the ticket is approved if the speakeasy password input is verified.

12. The method of claim 11, wherein when the ticket is utilised by the invitee, the method further comprises:

transmitting, to the issuer server, a fund transfer request to transfer at least a portion of the payment amount for the payment transaction, the fund transfer request comprising at least the transaction identifier and a transfer amount, the transfer amount being associated with at least a cost of the ticket used by the invitee to participate in the event; and

receiving, from the issuer server, a fund transfer response indicating whether the fund transfer request is approved or refused.

13. The method of claim 11, wherein when the ticket is utilised by the invitee, the method further comprises:

receiving, from the merchant server, a fund transfer request comprising a request to transfer at least a portion of the payment amount for the payment transaction, the fund transfer request comprising at least the transaction identifier and a transfer amount, the transfer amount being associated with at least a cost of the ticket used by the invitee to participate in the event;

transmitting, to the issuer server, the fund transfer request to transfer at least the portion of the payment amount; and

receiving, from the issuer server, a fund transfer response indicating whether the fund transfer request is approved or refused.

14. The method of claim 10 further comprising:

receiving, from the customer electronic device, invitee details associated with at least one invitee invited to participate in the event, the invitee details comprising at least an invitee contact; and

transmitting, to each invitee electronic device associated with the at least one invitee using the invitee contact, the transaction identifier and the speakeasy password.

15. The method of claim 14, wherein the invitee contact is one of a mobile number or an electronic mail address.

16. The method of claim 10, wherein the speakeasy password is-comprises a string of numbers, words, symbols or alphanumeric characters.

17. The method of claim 10, wherein the speakeasy password received via the customer electronic device is in the form of a speech.

18. The method of claim 10, wherein the transaction identifier is one of the following:

a Quick Response (QR) code, a barcode, an EZcode, a high capacity color barcode, a ShotCode, a MaxiCode, a GTIN12 code, a GTIN-13 code, Aztec code, a name and a mobile number.

19. A non-transitory computer-readable medium having stored thereon program instructions for causing at least one processor to:

receive, from a customer electronic device, a payment transaction request comprising at least a customer account identifier and a payment amount;

transmit, to an issuer server, a request for authorisation to proceed with the payment transaction, wherein the request for authorisation comprises at least the customer account identifier and the payment amount, and wherein the payment amount is blocked in a customer account associated with the customer account identifier if the payment transaction is authorised;

receive, from the issuer server, an authorisation response indicating if the payment transaction is authorised or refused;

transmit, to the customer electronic device, a speakeasy request comprising a request for a speakeasy password if the payment transaction is authorised;

receive, from the customer electronic device, a speakeasy response comprising the speakeasy password;

generate a transaction identifier, the transaction identifier being associated with the payment transaction;

store, using a payment network database, the transaction identifier and the speakeasy password, wherein the speakeasy password is associated with the transaction identifier; and

transmit, to the customer electronic device, a payment transaction response comprising at least the transaction identifier.