IP Library Patent Application 18377456
Patent Application
App. No. 18/377,456

NETWORK GATEWAY MESSAGING SYSTEMS AND METHODS

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
18/377,456
Abstract

Embodiments of the present disclosure relate to network gateway based messaging systems and methods. Some methods include transparent message processing that includes receiving a message from a first party that includes a payload and a token. The token is associated with sensitive information. Next, the method includes replacing the token with the sensitive information within the message and forwarding the message with the sensitive information to a second party. The payload is unaffected by the token exchange process.

Claims (47)

1 . A method, comprising:

receiving a message from a first party that comprises a payload comprising a token and content destined for a second party, the token being associated with sensitive information;

replacing the token with the sensitive information within the payload; and

forwarding the message with the sensitive information to the second party.

2 . The method according to claim 1 , wherein the message comprises a network-based protocol request and a token replacement scheme is incorporated into a header of the network-based protocol request or another location in the message that is not the payload.

3 . The method according to claim 1 , further comprising generating a token replacement scheme by the first party; and

applying the token replacement scheme, by a network gateway, to locate the token within the payload.

4 . The method according to claim 1 , further comprising storing the token and the sensitive information in a digital vault of a network gateway prior to receiving the message from the first party.

5 . The method according to claim 1 , further comprising:

receiving a tokenization request that comprises the sensitive information;

generating the token from the sensitive information;

replacing the sensitive information in the tokenization request with the token at a location of the sensitive information; and

transmitting the tokenization request back to the first party that includes the token in place of the sensitive information.

6 . The method according to claim 1 , wherein the payload comprises a pre-negotiated message format for the second party.

7 . The method according to claim 1 , further comprising transmitting the token or the sensitive information to the first party from a digital vault.

8 . The method according to claim 7 , further comprising receiving, by the first party, a failure message that indicates that a network gateway has failed to forward the message.

9 . The method according to claim 8 , further comprising:

replacing, by the first party, the token with the sensitive information; and

transmitting, by the first party, the message directly to the second party when the first party receives the failure message.

10 . The method according to claim 1 , further comprising applying a token replacement scheme to the message to locate the token, wherein the token is located at a particular location within the message and the token replacement scheme comprises instructions for finding the location of the token.

11 . The method according to claim 1 , wherein the token is embedded and wrapped with token identifying data; and a network gateway locates the token by searching the message for the token identifying data or locating the token using a pre-negotiated token replacement scheme.

12 . A system, comprising:

a client executing a gateway messaging application; and

a network gateway coupled to the client, the network gateway being configured to:

receive a message from the client that comprises a payload comprising a token, the token representing sensitive information;

apply a token replacement scheme to the message to locate the token;

exchange the token with the sensitive information; and

forward the message with the sensitive information to a receiving system without altering the payload.

13 . The system according to claim 12 , wherein the client is configured through the gateway messaging application to:

receive a failure message when the network gateway is unable to forward the message; and

redirect the message to the receiving system.

14 . The system according to claim 12 , wherein the client is configured through the gateway messaging application to replace the token with the sensitive information prior to redirecting the message to the receiving system.

15 . The system according to claim 12 , wherein the message comprises a network-based protocol request and a token locator is incorporated into a header of the network-based protocol request.

16 . The system according to claim 15 , wherein the network gateway is configured to strip off at least a portion of the header prior to forwarding the message with the sensitive information to a receiving system.

17 . The system according to claim 12 , wherein the message comprises a batch file that comprises a plurality of tokens that are each defined by a particular location in the message, and the network gateway is configured to replace one or more of the plurality of tokens with corresponding sensitive data.

18 . The system according to claim 12 , wherein the client is configured through the gateway messaging application to replace an endpoint of the message such that it directs to the network gateway.

19 . A system, comprising:

a processor; and

a memory storing logic that is executable by the processor to:

receive a message from the client that comprises a payload and a token, the token representing sensitive information, the message comprising:

an endpoint that directs the message to a network gateway;

authentication credentials; and

a token locator that identifies a location of the token within the payload;

authenticate the client with the authentication credentials;

replace the token with the sensitive information; and

forward the message with the sensitive information to a receiving system.

20 . The system according to claim 19 , wherein the message comprises a header and the endpoint, authentication credentials, and token locator reside in a header of the message, further wherein the system is configured to remove the header from the message prior to forwarding to the receiving system.

Assignments (4)
CHANGE OF NAME Recorded Mar 14, 2025
From: TOKENEX, INC.
To: IXOPAY, INC.
Reel/Frame 070510/0549 →
SECURITY INTEREST Recorded Mar 6, 2025
From: IXOPAY, INC.
To: CRESTLINE DIRECT FINANCE, L.P. AS COLLATERAL AGENT
Reel/Frame 070430/0260 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 3, 2025
From: DAWKINS, JERALD; STANLEY, JUSTIN
To: TOKENEX, LLC
Reel/Frame 070380/0470 →
NUNC PRO TUNC ASSIGNMENT Recorded Mar 3, 2025
From: TOKENEX, LLC
To: TOKENEX, INC.
Reel/Frame 070381/0875 →