US-20260127584-A1 - PERSONALLY IDENTIFIABLE INFORMATION SECURE PERSON-TO-PERSON PAYMENT TECHNOLOGY

Abstract

In some aspects, the techniques described herein relate to a method, including: receiving, from a sender, a P2P transfer request including at least a receiver token PAN corresponding to a receiver account of a receiver; obtaining a sender token PAN corresponding to a sender account of the sender; communicating, to an enhanced processing platform, a P2P transfer advice request including at least the sender token PAN and the receiver token PAN; receiving, from the enhanced processing platform, an account authorization message including at least a sender account number corresponding to the sender account and a receiver account number corresponding to the receiver account; and providing, to a receiver account holding institution (AHI) system via a payment network, funds to be transferred from the sender account associated with the sender account number to the receiver account associated with the receiver account number.

Inventors

• Nilesh Tulsidas Upadhye
• Joseph D. Hayes

Assignees

• MASTERCARD INTERNATIONAL INCORPORATED

Dates

Publication Date

20260507

Application Date

20260105

Claims (20)

1. 1 . One or more computer-readable storage media having instructions stored thereon that when executed by a processing system, direct the processing system to: receive, from a sender, a P2P transfer request comprising at least a receiver token PAN corresponding to a receiver account of a receiver; obtain a sender token PAN corresponding to a sender account of the sender; communicate, to an enhanced processing platform, a P2P transfer advice request comprising at least the sender token PAN and the receiver token PAN; receive, from the enhanced processing platform, an account authorization message comprising at least a sender account number corresponding to the sender account and a receiver account number corresponding to the receiver account; and provide, to a receiver account holding institution (AHI) system via a payment network, funds to be transferred from the sender account associated with the sender account number to the receiver account associated with the receiver account number.
2. 2 . The media of claim 1 , wherein the receiver token PAN received in the P2P transfer request is received in a form of a QR code.
3. 3 . The media of claim 1 , wherein the sender token PAN and the receiver token PAN do not contain personally identifiable information.
4. 4 . The media of claim 1 , wherein the instructions to obtain the sender token PAN further direct the processing system to: identify the sender token PAN corresponding to a sender identifier received in the P2P transfer request.
5. 5 . The media of claim 1 , wherein the P2P transfer request further comprises the sender token PAN.
6. 6 . The media of claim 1 , wherein the P2P transfer advice request is a request to translate the sender token PAN into the corresponding sender account number and the receiver token PAN into the corresponding receiver account number.
7. 7 . The media of claim 1 , wherein the account authorization message authorizes funds to be transferred from the sender account associated with the sender account number to the receiver account associated with the receiver account number.
8. 8 . The media of claim 1 , wherein the P2P transfer request is a request for a sender-initiated (Push) PII secure P2P payment.
9. 9 . A system comprising: a processing system; a storage system; and instructions stored on the storage system that, when executed by the processing system, direct the processing system to at least: receive, from a sender, a P2P transfer request comprising at least a receiver token PAN corresponding to a receiver account of a receiver; obtain a sender token PAN corresponding to a sender account of the sender; communicate, to an enhanced processing platform, a P2P transfer advice request comprising at least the sender token PAN and the receiver token PAN; receive, from the enhanced processing platform, an account authorization message comprising at least a sender account number corresponding to the sender account and a receiver account number corresponding to the receiver account; and provide, to a receiver account holding institution (AHI) system via a payment network, funds to be transferred from the sender account associated with the sender account number to the receiver account associated with the receiver account number.
10. 10 . The system of claim 9 , wherein the receiver token PAN received in the P2P transfer request is received in a form of a QR code.
11. 11 . The system of claim 9 , wherein the sender token PAN and the receiver token PAN do not contain personally identifiable information.
12. 12 . The system of claim 9 , wherein the instructions to obtain the sender token PAN further direct the processing system to: identify the sender token PAN corresponding to a sender identifier received in the P2P transfer request.
13. 13 . The system of claim 9 , wherein the P2P transfer request further comprises the sender token PAN.
14. 14 . The system of claim 9 , wherein the P2P transfer advice request is a request to translate the sender token PAN into the corresponding sender account number and the receiver token PAN into the corresponding receiver account number.
15. 15 . The system of claim 9 , wherein the account authorization message authorizes funds to be transferred from the sender account associated with the sender account number to the receiver account associated with the receiver account number.
16. 16 . The system of claim 9 , wherein the P2P transfer request is a request for a sender-initiated (Push) PII secure P2P payment.
17. 17 . A method, comprising: receiving, from a sender, a P2P transfer request comprising at least a receiver token PAN corresponding to a receiver account of a receiver; obtaining a sender token PAN corresponding to a sender account of the sender; communicating, to an enhanced processing platform, a P2P transfer advice request comprising at least the sender token PAN and the receiver token PAN; receiving, from the enhanced processing platform, an account authorization message comprising at least a sender account number corresponding to the sender account and a receiver account number corresponding to the receiver account; and providing, to a receiver account holding institution (AHI) system via a payment network, funds to be transferred from the sender account associated with the sender account number to the receiver account associated with the receiver account number.
18. 18 . The method of claim 17 , wherein the receiver token PAN received in the P2P transfer request is received in a form of a QR code.
19. 19 . The method of claim 17 , wherein the sender token PAN and the receiver token PAN do not contain personally identifiable information.
20. 20 . The method of claim 17 , wherein obtaining the sender token PAN comprises identifying the sender token PAN corresponding to a sender identifier received in the P2P transfer request.

Description

BACKGROUND Maintaining personally identifiable information (PII) security is important for all entities that accept, store, process, or transmit payment information. PII is information that can be utilized to identify or trace an individual's identity including, but not limited to, name, address, social security number, biometric data, or date of birth. Maintaining PII security can be costly or otherwise difficult to achieve. BRIEF SUMMARY Personally identifiable information (PII) secure person-to-person (P2P) payment technology is described herein. Through the described technology, a P2P payment can be made using a token primary account number (PAN), allowing for a single product to be used for contactless payments, e-commerce payments, and P2P payments. When an account or payment card is digitized using an enhanced processing platform, the enhanced processing platform issues a token PAN which represents but is not directly a user's actual primary account number and can be used for P2P payments. The introduction of the described token PAN allows for a P2P payment to made without sharing PII data. Indeed, unlike personal contact information conventionally used in a P2P payment, such as a personal mobile number, email address, or username, the described token PAN is not personally identifiable information. Thus, overall exposure risk for PII data can be reduced. In some aspects, the techniques described herein relate to one or more computer-readable storage media having instructions stored thereon that when executed by a processing system, direct the processing system to: receive, from a sender, a P2P transfer request including at least a receiver token PAN corresponding to a receiver account of a receiver; obtain a sender token PAN corresponding to a sender account of the sender; communicate, to an enhanced processing platform, a P2P transfer advice request including at least the sender token PAN and the receiver token PAN; receive, from the enhanced processing platform, an account authorization message including at least a sender account number corresponding to the sender account and a receiver account number corresponding to the receiver account; and provide, to a receiver account holding institution (AHI) system via a payment network, funds to be transferred from the sender account associated with the sender account number to the receiver account associated with the receiver account number. This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS FIGS. 1A and 1B illustrate example operating environments and signal flows for sender-initiated (Push) PII secure P2P payments. FIG. 2 illustrates an example operating environment and signal flow for receiver-initiated (Pull) PII secure P2P payments. FIG. 3 illustrates an example process carried out by a sender AHI system according to an embodiment of the invention. FIG. 4 illustrates an example process carried out by a receiver AHI system according to an embodiment of the invention. FIG. 5 illustrates an example process carried out by an enhanced processing platform according to an embodiment of the invention. FIG. 6 illustrates an example operating environment for PII secure P2P payment processing. FIG. 7 illustrates components of a computing system that may be used in certain embodiments described herein. DETAILED DESCRIPTION Personally identifiable information (PII) secure person-to-person (P2P) payment technology is described herein. Through the described technology, a P2P payment can be made using a token primary account number (PAN), allowing for a single product to be used for contactless payments, e-commerce payments, and P2P payments. When an account or payment card is digitized using an enhanced processing platform, the enhanced processing platform issues a token PAN which represents but is not directly a user's actual primary account number and can be used for P2P payments. The introduction of the described token PAN allows for a P2P payment to made without sharing PII data. Indeed, unlike personal contact information conventionally used in a P2P payment, such as a personal mobile number, email address, or username, the described token PAN is not personally identifiable information. Thus, overall exposure risk for PII data can be reduced. The enhanced processing platform can receive, from a sender account holding institution (AHI) system, a P2P transfer advice request comprising at least a sender token PAN and a receiver token PAN. The enhanced processing platform can identify a sender account number from a token vault using the sender token PAN; and identify a receiver account number from the token vault using the receiver token PAN. The enhanced