US 11,720,975 B2
Systems and methods for multi-purse transaction file splitting
Thejaswini Srikanta, Cary, NC (US); Jayesh Parab, Morrisville, NC (US); and Pradeep Srinivasan Madhu, Morrisville, NC (US)
Assigned to FMR LLC, Boston, MA (US)
Filed by FMR LLC, Boston, MA (US)
Filed on Nov. 5, 2020, as Appl. No. 17/90,488.
Prior Publication US 2022/0138865 A1, May 5, 2022
Int. Cl. G06Q 40/00 (2023.01); G06Q 20/34 (2012.01); G06F 16/18 (2019.01); G06F 21/60 (2013.01); H04L 9/08 (2006.01); G06Q 20/36 (2012.01); G06Q 40/02 (2023.01); G06Q 20/38 (2012.01); G06Q 40/12 (2023.01)
CPC G06Q 40/12 (2013.12) [G06F 16/1865 (2019.01); G06F 21/602 (2013.01); G06Q 20/34 (2013.01); G06Q 20/3674 (2013.01); G06Q 20/3676 (2013.01); G06Q 20/389 (2013.01); G06Q 40/02 (2013.01); H04L 9/0861 (2013.01); G06Q 2220/00 (2013.01)] 15 Claims
OG exemplary drawing
 
1. A computerized method for distributing transaction files among a plurality of accounts corresponding to a physical card, the method comprising:
recording, by a point of sale (POS) terminal, a plurality of transaction records corresponding to payment activity for a plurality of different physical cards, wherein each physical card is associated with a plurality of different accounts including at least one health savings account, and wherein each transaction record includes a purse ID corresponding to one of the different accounts of the physical card;
transmitting, by the POS terminal, the plurality of transaction records to a transaction processing entity computing device;
generating, by the transaction processing entity computing device, a plurality of transaction files for the plurality of transactions, each transaction file comprising a different file type;
receiving, by a server computing device, the plurality of transaction files from the transaction processing entity computing device;
for each transaction file in the plurality of transaction files:
determining, by the server computing device, a file type of the transaction file;
generating, by the server computing device, a data layout mapping for the transaction file based upon the file type of the transaction file;
identifying, by the server computing device, at least one purse segment in the transaction file using a purse segment location defined by the data layout mapping of the transaction file, wherein each purse segment corresponds to a transaction associated with the physical card; and
for each of the at least one purse segments:
identifying, by the server computing device, a purse ID in the purse segment using a purse ID location defined by the data layout mapping of the transaction file;
extracting, by the server computing device, transaction data from the transaction file corresponding to the purse ID using a transaction data location defined by the data layout mapping of the transaction file;
masking, by the server computing device, one or more personal data elements in the transaction data when the purse ID corresponds to a health savings account; and
storing, by the server computing device, the transaction data corresponding to the purse ID in a distribution file;
deleting, by the server computing device, the plurality of transaction files and the corresponding data layout mappings from a memory of the server computing device;
identifying, by the server computing device for each distribution file, an account processing system corresponding to the purse ID in the distribution file; and
transmitting, by the server computing device, each of the distribution files to a separate account processing system corresponding to the purse ID in the distribution file, including generating a separate encryption key for each account processing system upon connecting to the account processing system and encrypting the distribution file using the encryption key prior to transmission.