IP Library Granted Patent US 11,818,116
Granted Patent B2
US 11,818,116 · App. 16/251,684 · Granted Nov 14, 2023

Network gateway messaging systems and methods

Inventors: Jerald Dawkins (Tulsa, OK); Justin Stanley (Bixby, OK)
Assignee: TOKENEX, INC.
H04L63/0823H04L63/0485H04L63/12H04L63/166
View Patent ↗
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 11,818,116
App. No.
16/251,684
Granted
Nov 14, 2023
Kind
B2
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 (52)

1. A method, comprising:

receiving sensitive information through a portal interface captured by a gateway to prevent a first party from having possession of the sensitive information;

generating a token from the sensitive information;

receiving a message from a first party that comprises a payload comprising token and content destined for a second party, the token being embedded and wrapped within the payload with token identifying data, the token identifying data comprising a token locator comprising a tuple having a line number, starting character position and ending character position;

locating the token in the message using the token locator;

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. 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 sensitive information through a portal interface captured by a gateway to prevent a first party from having possession of the sensitive information;

generate a token from the sensitive information;

receive a message from the client that comprises a payload comprising token, the token being embedded and wrapped within the payload with token identifying data, the token identifying data comprising a token locator comprising a tuple having a line number, starting character position and ending character position;

locate the token in the message using the token locator;

exchange the token with the sensitive information; and

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

12. The system according to claim 11 , 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.

13. The system according to claim 11 , 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.

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

15. The system according to claim 14 , 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.

16. The system according to claim 11 , 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.

17. The system according to claim 11 , 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.

18. A system, comprising:

a processor; and

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

receive sensitive information through a portal interface captured by a gateway to prevent a first party from having possession of the sensitive information;

generate a token from the sensitive information;

receive a message from the client that comprises a payload and the token, the token being embedded and wrapped within the payload with token identifying data, the message comprising:

an endpoint that directs the message to a network gateway; authentication credentials; and

a token locator comprising a tuple having a line number, starting character position and ending character position;

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.

19. The system according to claim 18 , 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 (6)
SECURITY INTEREST Recorded Mar 6, 2025
From: IXOPAY, INC.
To: CRESTLINE DIRECT FINANCE, L.P. AS COLLATERAL AGENT
Reel/Frame 070430/0260 →
RELEASE OF SECURITY INTEREST Recorded Feb 25, 2025
From: JPMORGAN CHASE BANK, N.A., AS AGENT
To: IXOPAY, INC. (F/K/A TOKENEX, INC.)
Reel/Frame 070316/0833 →
CHANGE OF NAME Recorded Feb 19, 2025
From: TOKENEX, INC.
To: IXOPAY, INC.
Reel/Frame 070268/0826 →
SECURITY INTEREST Recorded May 5, 2023
From: TOKENEX, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 063549/0171 →
NUNC PRO TUNC ASSIGNMENT Recorded Nov 30, 2021
From: TOKENEX LLC
To: TOKENEX INC.
Reel/Frame 058247/0166 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 22, 2021
From: STANLEY, JUSTIN; DAWKINS, JERALD
To: TOKENEX, LLC
Reel/Frame 058186/0621 →
Continuity (2)
Continuation 15051614 · Feb 23, 2016
Related Publication 20200236103A1 · Jul 23, 2020