Granted Patent B2

US 12,572,927 · App. 17/853,309 · Granted Mar 10, 2026

Inventor: Sachin Pawaskar (Mason, OH)

Assignee: Worldpay, LLC

G06Q20/382G06Q20/027G06Q20/102G06Q20/4014G06Q20/4018G06Q30/0613

Abstract

Claims (78)

1 . A computer-implemented method comprising:

receiving, by an issuance service, a request from a device associated with at least one user, wherein the request includes an open account request;

transmitting, by the issuance service, a first notification regarding the request, via a service gateway, to an application server;

providing, by the service gateway, a secure application programming interface (API) abstraction layer configured to translate partner-specific API requests into a format compatible with the application server, wherein the secure API abstraction layer facilitates scalable communication between the application server and partner distributed computing system;

transmitting, by the application server, the first notification regarding the request to a mainframe system, wherein the application server monitors a database of the mainframe system for receiving a second notification;

transmitting, by the application server, the second notification regarding the request, via the service gateway, to the partner distributed computing system, wherein the second notification includes account information regarding an account opened for use on a digital payment platform;

determining, by the service gateway, a failure in receiving a confirmation from the partner distributed computing system within a pre-determined time threshold;

iterating, by the application server, a sequence of operations including (i) transmitting the second notification to the partner distributed computing system, (ii) registering a failure event upon detecting the failure in receiving the confirmation, and (iii) notifying the application server of the failure to increment an attempt count for transmitting the second notification based on a threshold attempt count limit;

determining, by the application server, to cease the attempt count for transmitting the second notification to the partner distributed computing system based on determining the threshold attempt count limit has been exceeded;

transmitting, by the partner distributed computing system, a request for additional information, via the service gateway, to the application server;

encrypting, by the application server, the additional information using an encoding scheme;

transmitting, by the application server, the encrypted additional information, via the service gateway, to the partner distributed computing system upon determining a timestamp associated with the request for additional information has not expired;

receiving, by the application server, the confirmation and one or more nonce values from the partner distributed computing system based, at least in part, on identification and association of the account with the at least one user;

encrypting, by a service provider, the account information utilizing the encoding scheme based, at least in part, on the one or more nonce values; and

transmitting, by the service provider, the encrypted account information to a device associated with a digital payment provider.

2 . The method of claim 1 , wherein transmitting the second notification, further comprising:

storing the account information regarding the account opened for use on the digital payment platform; and

generating the second notification based, at least in part, on the stored account information.

3 . The method of claim 1 , wherein the threshold attempt count limit is preconfigured for the partner distributed computing system.

4 . The method of claim 1 , further comprising:

monitoring, one or more events regarding opening of a plurality of accounts for use on the digital payment platform, at specified time intervals; and

transmitting one or more notifications to the partner distributed computing system upon determining an update or a change in the one or more events.

5 . The method of claim 1 , wherein the one or more nonce values include a server nonce value and a device signature nonce value.

6 . The method of claim 5 , wherein the one or more nonce values are received from the partner distributed computing system in real-time or near real-time, and wherein the account information is encrypted in real-time or near real-time.

7 . The method of claim 1 , wherein the open account request includes opening a bank account, a credit card account, a debit card account, or a combination thereof for the at least one user.

8 . The method of claim 1 , wherein the account information is encrypted using a Base64 encoding scheme.

9 . A computer system comprising:

one or more memories storing processor-executable instructions that, when executed by one or more processors, cause the one or more processors to facilitate operations comprising:

receive, by an issuance service, a request from a device associated with at least one user, wherein the request includes an open account request;

transmit, by the issuance service, a first notification regarding the request, via a service gateway, to an application server;

provide, by the service gateway, a secure application programming interface (API) abstraction layer configured to translate partner-specific API requests into a format compatible with the application server, wherein the secure API abstraction layer facilitates scalable communication between the application server and partner distributed computing system;

transmit, by the application server, the first notification regarding the request to a mainframe system, wherein the application server monitors a database of the mainframe system for receiving a second notification;

transmit, by the application server, the second notification regarding the request, via the service gateway, to the partner distributed computing system, wherein the second notification includes account information regarding an account opened for use on a digital payment platform;

determine, by the service gateway, a failure in receiving a confirmation from the partner distributed computing system within a pre-determined time threshold;

iterate, by the application server, a sequence of operations including (i) transmitting the second notification to the partner distributed computing system, (ii) registering a failure event upon detecting the failure in receiving the confirmation, and (iii) notifying the application server of the failure to increment an attempt count for transmitting the second notification based on a threshold attempt count limit;

determine, by the application server, to cease the attempt count for transmitting the second notification to the partner distributed computing system based on determining the threshold attempt count limit has been exceeded;

transmit, by the partner distributed computing system, a request for additional information, via the service gateway, to the application server;

encrypt, by the application server, the additional information using an encoding scheme;

transmit, by the application server, the encrypted additional information, via the service gateway, to the partner distributed computing system upon determining a timestamp associated with the request for additional information has not expired;

receive, by the application server, the confirmation and one or more nonce values from the partner distributed computing system based, at least in part, on identification and association of the account with the at least one user, wherein the one or more nonce values include a server nonce value and a device signature nonce value;

encrypt, by a service provider, the account information utilizing the encoding scheme based, at least in part, on the one or more nonce values; and

transmit, by the service provider, the encrypted account information to a device associated with a digital payment provider.

10 . The system of claim 9 , wherein transmitting the second notification, further comprising:

store the account information regarding the account opened for use on the digital payment platform; and

generate the second notification based, at least in part, on the stored account information.

11 . The system of claim 9 , wherein the threshold attempt count limit is preconfigured for the partner distributed computing system.

12 . The system of claim 9 , further comprising:

monitor, one or more events regarding opening of a plurality of accounts for use on the digital payment platform, at specified time intervals; and

transmit one or more notifications to the partner distributed computing system upon determining an update or a change in the one or more events.

13 . A non-transitory computer readable medium storing a program causing a computer to execute a method comprising:

receiving, by an issuance service, a request from a device associated with at least one user, wherein the request includes opening an account for use on a digital payment platform;

transmitting, by the issuance service, a first notification regarding the request, via a service gateway, to an application server;

providing, by the service gateway, a secure application programming interface (API) abstraction layer configured to translate partner-specific API requests into a format compatible with the application server, wherein the secure API abstraction layer facilitates scalable communication between the application server and partner distributed computing system;

transmitting, by the application server, the first notification regarding the request to a mainframe system, wherein the application server monitors a database of the mainframe system for receiving a second notification;

transmitting, by the application server, the second notification regarding the request, via the service gateway, to the partner distributed computing system, wherein the second notification includes account information regarding the account opened for use on the digital payment platform;

determining, by the service gateway, a failure in receiving a confirmation from the partner distributed computing system within a pre-determined time threshold;

iterating, by the application server, a sequence of operations including (i) transmitting the second notification to the partner distributed computing system, (ii) registering a failure event upon detecting the failure in receiving the confirmation, and (iii) notifying the application server of the failure to increment an attempt count for transmitting the second notification based on a threshold attempt count limit;

determining, by the application server, to cease the attempt count for transmitting the second notification to the partner distributed computing system based on determining the threshold attempt count limit has been exceeded;

transmitting, by the partner distributed computing system, a request for additional information, via the service gateway, to the application server;

encrypting, by the application server, the additional information using an encoding scheme;

transmitting, by the application server, the encrypted additional information, via the service gateway, to the partner distributed computing system upon determining a timestamp associated with the request for additional information has not expired;

receiving, by the application server, the confirmation and one or more nonce values from the partner distributed computing system based, at least in part, on identification and association of the account with the at least one user;

encrypting, by a service provider via the encoding scheme, the account information based, at least in part, on the one or more nonce values; and

transmitting, by the service provider, the encrypted account information to a device associated with a digital payment provider.

14 . The non-transitory computer readable medium of claim 13 , wherein transmitting the second notification, further comprising:

storing the account information regarding the account opened for use on the digital payment platform; and

generating the second notification based, at least in part, on the stored account information.

15 . The non-transitory computer readable medium of claim 13 , wherein the threshold attempt count limit is preconfigured for the partner distributed computing system.

16 . The method of claim 1 , wherein the confirmation from the partner distributed computing system indicates receipt and transmission of the second notification to the digital payment platform.

17 . The method of claim 1 , wherein the application server monitoring the database of the mainframe system for receiving the second notification, further comprises:

determining, by the database of the mainframe system, an update in content of the database; and

transmitting, by the database of the mainframe system, the second notification to a notification framework component of the application server based on the update of the content.

18 . The method of claim 1 , wherein the additional information includes one or more of a status code, a status message, an event count, an event type, or a timestamp data.

19 . The method of claim 1 , wherein incrementing the attempt count for transmitting the second notification to the partner distributed computing system comprises:

retransmitting, by the application server, the second notification, via the service gateway, to the partner distributed computing system upon each failure to receive the confirmation until the threshold attempt count limit is reached.

20 . The method of claim 1 , further comprising:

queuing the open account request in a queue component of the mainframe system; and

generating an event based on the open account request in an event database of the mainframe system.

Assignments (6)

Continuity (2)

References Cited (71)