Removing duplicate transactions from a transaction exchange platform

A transaction exchange platform comprising:

• a streaming data platform;
• a plurality of microservices comprise a screening microservice and a client registry microservice;
• at least one processor;
• and
• memory storing instructions that, when executed by the at least one processor, cause the transaction exchange platform to:
• receive, by the screening microservice, a first transaction object corresponding to a first payment transaction, wherein the first transaction object comprises first transaction details;
• determine, by the screening microservice, whether the first transaction object is a duplicate payment transaction by comparing the first transaction details to a data structure comprising transaction details of a plurality of payment transactions;
• based on a determination that the first transaction details overlap with second transaction details of a second payment transaction, send, by the screening microservice to a first user device, a request inquiring whether the first payment transaction is a duplicate of the second payment transaction;
• receive, by the screening microservice from the first user device, a response indicating that the first payment transaction is not a duplicate of the second payment transaction;
• in response to receiving the response, generate an identification token for the first transaction object;
• add the first transaction object to a streaming data platform, wherein adding the first transaction object to the streaming data platform comprises setting a current workflow stage of the first transaction object to a pre-initialization stage;
• retrieve, by the client registry microservice and based on a current workflow stage indicating the pre-initialization stage, a plurality of transaction objects, wherein the plurality of transaction objects comprises the first transaction object;
• prepend, by the client registry microservice and based on a determination that the first payment transaction is permitted, a client identifier to the identification token to generate a first transaction identifier;
• update, by the client registry microservice, the current workflow stage of the first transaction object to an initialization state;
• add, by the client registry microservice, the updated first transaction object to the streaming data platform;
• based on a determination that the current workflow stage of the updated first transaction object indicates that the updated first transaction object has completed processing, remove the updated first transaction object from the streaming data platform and outputting the updated first transaction object to a validation platform;
• determine, by the validation platform, whether a format of the first transaction is valid;
• based on determination that the format of the first transaction is valid, append a batch identifier to the first transaction identifier and add the first transaction to a file;
• and
• upload the file to a portal to initiate the first transaction and a plurality of transactions contained in the file.

One or more non-transitory computer readable media comprising instructions that, when executed, cause a transaction exchange platform to:

• receive, by a screening microservice, a first transaction object corresponding to a first payment transaction, wherein the first transaction object comprises first transaction details;
• determine, by the screening microservice, whether the first transaction object is a duplicate payment transaction by comparing the first transaction details to a data structure comprising transaction details of a plurality of payment transactions;
• based on a determination that the first transaction details overlap with second transaction details of a second payment transaction, send, by the screening microservice to a first user device, a request inquiring whether the first payment transaction is a duplicate of the second payment transaction;
• receive, by the screening microservice from the first user device, a response indicating that the first payment transaction is not a duplicate of the second payment transaction;
• in response to receiving the response, generate an identification token for the first transaction object;
• add the first transaction object to a streaming data platform, wherein adding the first transaction object to the streaming data platform comprises setting a current workflow stage of the first transaction object to a pre-initialization stage;
• retrieve, by a client registry microservice and based on a current workflow stage indicating the pre-initialization stage, a plurality of transaction objects, wherein the plurality of transaction objects comprises the first transaction object;
• prepend, by the client registry microservice and based on a determination that the first payment transaction is permitted, a client identifier to the identification token to generate a first transaction identifier;
• update, by the client registry microservice, the current workflow stage of the first transaction object to an initialization state;
• add, by the client registry microservice, the updated first transaction object to the streaming data platform;
• based on a determination that the current workflow stage of the updated first transaction object indicates that the updated first transaction object has completed processing, remove the updated first transaction object from the streaming data platform and output the updated first transaction object to a validation platform;
• determine, by the validation platform, whether a format of the first transaction is valid;
• based on determination that the format of the first transaction is valid, append a batch identifier to the first transaction identifier and add the first transaction to a file;
• and
• upload the file to a portal to initiate the first transaction and a plurality of transactions contained in the file.