# US 2023/0067705 A1 · A system and method for securely delivering information

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0067705 A1
- Document ID: US20230067705A1
- Status: Published application
- Kind: A1
- Application number: 17/799,619
- Filed: 2021-02-15
- Published: 2023-03-02
- Earliest claimed: 2020-02-13
- Assignees: Syntec Holdings Limited
- Applicants: Syntec Holdings Limited
- Inventors: Colin Philip WESTLAKE
- Web page: https://patentgrep.com/patent/US20230067705A1

## CPC

- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- G06Q 20/305: {using wired telephone networks}
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/325: {using wireless networks}
- H04M 3/2281: {Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls}
- H04M 3/42068: {where the identifier is used to access a profile}
- H04M 3/5141: {Details of processing calls and other types of contacts in an unified manner (unified messaging in packet-switching networks H04L51/56)}
- H04M 15/06: Recording class or number of calling {, i.e. A-party} or called party {, i.e. B-party}
- H04M 3/51: Centralised call answering arrangements requiring operator intervention {, e.g. call or contact centers for telemarketing}
- H04M 7/1295: {Details of dual tone multiple frequency signalling}
- H04M 2201/18: Comparators
- H04M 2203/6027: Fraud preventions
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A computer-implemented method for correlating payment service submissions and data captured from a call stream is described herein. The method comprises receiving data captured from a call stream by a data capture device; receiving a payment service submission comprising an identifier; determining an association between the identifier and the call stream; and replacing the identifier in the payment service submission with the data captured from the call stream associated with the identifier.

## Claims

### Claim 1

A computer-implemented method for correlating payment service submissions and data captured from a call stream, the method comprising:
receiving data captured from a call stream by a data capture device;
receiving a payment service submission comprising an identifier;
determining an association between the identifier and the call stream; and
replacing the identifier in the payment service submission with the data captured from the call stream associated with the identifier.

### Claim 2 (depends on 1)

The method of claim 1, wherein the identifier is a first identifier, or wherein the identifier is a second identifier generated from a first identifier.

### Claim 3 (depends on 2)

The method of claim 2, further comprising generating the second identifier.

### Claim 4 (depends on 1, 2, 3)

The method of any one of claims 1 to 3, wherein determining an association between the identifier and the call stream comprises using metadata for the call stream.

### Claim 5 (depends on 4)

The method of claim 4, wherein the metadata is the identifier or one is algorithmically derivable from the other.

### Claim 6 (depends on 2, 4)

The method of claim 4 when dependent upon claim 2, wherein the identifier is the second identifier, and wherein the metadata is the first identifier or one is algorithmically derivable from the other.

### Claim 7 (depends on 4, 5, 6)

The method of any one of claims 4 to 6, wherein determining an association between the identifier and the call stream comprises using a lookup table comprising metadata for each call stream of a plurality of call streams.

### Claim 8 (depends on 1, 2, 3, 4, 5, 6, 7)

The method of any one of claims 1 to 7, further comprising forwarding the payment service submission with the data captured from the call stream associated with the identifier to an external system and/or storing the payment service submission in memory.

### Claim 9 (depends on 2, 3, 4, 5, 6, 7, 8)

The method of any one of claims 2 to 8, wherein the first identifier and/or the metadata is derived from one or more of:
a telephone number associated with a party to the call stream;
an identifier present or injected into the call stream;
current time;
a random number; and
a sequence number representing the number of times data has been captured from the call stream.

### Claim 10 (depends on 2, 3, 4, 5, 6, 7, 8, 9)

The method of any one of claims 2 to 9, wherein the call stream is associated with an agent and wherein the first identifier and/or the metadata is derived from an identification number for the agent and/or a telephone number associated with the agent.

### Claim 11 (depends on 2, 3, 4, 5, 6, 7, 8, 9, 10)

The method of any one of claims 2 to 10, wherein the second identifier complies with a predetermined format.

### Claim 12

The method of any one of the preceding claims, further comprising passing a capture identifier to the data capture device.

### Claim 13

A computer-implemented method for preparing a payment service submission, the method comprising:
receiving input data for a payment service submission; and
sending a payment service submission to a server, the payment service submission comprising:
the received input data, and
an identifier associated with a call stream,
optionally wherein the input data comprises said identifier.

### Claim 14 (depends on 13)

The method of claim 13, wherein the identifier is a first identifier, or wherein the identifier is a second identifier generated from a first identifier.

### Claim 15 (depends on 14)

The method of claim 14, further comprising generating the second identifier from the first identifier.

### Claim 16 (depends on 14, 15)

The method of claim 14 or claim 15, wherein the first identifier is derived from one or more of:
a telephone number associated with a party to the call stream;
an identifier present or injected into the call stream;
current time;
a random number; and
a sequence number representing the number of times data has been captured from the call stream.

### Claim 17 (depends on 14, 15, 16)

The method of any one of claims 14 to 16, wherein the call stream is associated with an agent and wherein the first identifier is derived from an identification number for the agent and/or a telephone number associated with the agent.

### Claim 18 (depends on 17)

The method of claim 17, wherein the input data comprises data entered by the agent.

### Claim 19 (depends on 13, 14, 15, 16, 17, 18)

The method of any one of claims 13 to 18, wherein the input data comprises data received from a client management system.

### Claim 20 (depends on 14, 15, 16, 17, 18, 19)

The method of any one of claims 14 to 19, wherein the second identifier complies with a predetermined format.

### Claim 21 (depends on 20)

The method of claim 20, wherein the payment service submission is sent to the server via a payment system, and wherein the predetermined format is imposed by said payment system.

### Claim 22 (depends on 14, 15, 16, 17, 18, 19, 20, 21)

The method of any one of claims 14 to 21, wherein the second identifier is generated prior to the receipt of input data for a payment service submission.

### Claim 23 (depends on 14, 15, 16, 17, 18, 19, 20, 21, 22)

The method of any one of claims 14 to 22, wherein the second identifier is generated posterior to the receipt of input data for a payment service submission.

### Claim 24 (depends on 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23)

The method of any one of claims 13 to 23, further comprising passing a capture identifier to a data capture device.

### Claim 25 (depends on 1, 13)

A computer-implemented method for processing data captured from a call stream, the method comprising:
performing the steps of claim 13; and
performing the steps of claim 1, wherein:
the call stream of claim 1 is the call stream of claim 13;
the identifier of claim 1 is the identifier of claim 13, and
the received payment service submission of claim 1 is the sent payment service submission of claim 13.

### Claim 26 (depends on 1, 13, 25)

The method of claim 25, wherein the identifier of claims 1 and 13 is a first identifier, or wherein the identifier of claims 1 and 13 is a second identifier generated from a first identifier.

### Claim 27 (depends on 26)

The method of claim 26, further comprising generating the second identifier.

### Claim 28 (depends on 25, 26, 27)

The method of any one of claims 25 to 27, wherein determining an association between the identifier and the call stream comprises using metadata for the call stream.

### Claim 29 (depends on 28)

The method of claim 28, wherein the metadata is the identifier or one is algorithmically derivable from the other.

### Claim 30 (depends on 26, 28)

The method of claim 28 when dependent upon claim 26, wherein the identifier is the second identifier, and wherein the metadata is the first identifier or one is algorithmically derivable from the other.

### Claim 31 (depends on 28, 29, 30)

The method of any one of claims 28 to 30, wherein determining an association between the identifier and the call stream comprises using a lookup table comprising metadata for each call stream of a plurality of call streams.

### Claim 32 (depends on 25, 26, 27, 28, 29, 30, 31)

The method of any one of claims 25 to 31, further comprising forwarding the payment service submission with the data captured from the call stream associated with the identifier to an external system and/or storing the payment service submission in memory.

### Claim 33 (depends on 26, 27, 28, 29, 30, 31, 32)

The method of any one of claims 26 to 32, wherein the first identifier and/or the metadata is derived from one or more of:
a telephone number associated with a party to the call stream;
an identifier present or injected into the call stream;
current time;
a random number; and
a sequence number representing the number of times data has been captured from the call stream.

### Claim 34 (depends on 26, 27, 28, 29, 30, 31, 32, 33)

The method of any one of claims 26 to 33, wherein the call stream is associated with an agent and wherein the first identifier and/or the metadata is derived from an identification number for the agent and/or a telephone number associated with the agent.

### Claim 35 (depends on 34)

The method of claim 34, wherein the input data comprises data entered by the agent.

### Claim 36 (depends on 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35)

The method of any one of claims 25 to 35, wherein the input data comprises data received from a client management system.

### Claim 37 (depends on 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36)

The method of any one of claims 26 to 36, wherein the second identifier complies with a predetermined format.

### Claim 38 (depends on 37)

The method of claim 37, wherein the payment service submission is sent to the server via a payment system, and wherein the predetermined format is imposed by said payment system.

### Claim 39 (depends on 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38)

The method of any one of claims 26 to 38, wherein the second identifier is generated prior to the receipt of input data for a payment service submission.

### Claim 40 (depends on 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39)

The method of any one of claims 26 to 39, wherein the second identifier is generated posterior to the receipt of input data for a payment service submission.

### Claim 41 (depends on 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40)

The method of any one of claims 25 to 40, further comprising passing a capture identifier to the data capture device.

### Claim 42 (depends on 2, 12, 14, 24, 26, 41)

The method of claim 12 when dependent on claim 2, the method of claim 24 when dependent on claim 14, or the method of claim 41 when dependent on claim 26, wherein the capture identifier is the first or second identifier.

### Claim 43 (depends on 2, 12, 14, 24, 26, 41)

The method of claim 12 when dependent on claim 2, the method of claim 24 when dependent on claim 14, or the method of claim 41 when dependent on claim 26, wherein the capture identifier is algorithmically derivable from the first or second identifier.

### Claim 44 (depends on 7, 12, 31, 41)

The method of claim 12 when dependent on claim 7, or the method of claim 41 when dependent on claim 31, wherein the capture identifier is derived from a lookup of the first or second identifier in the lookup table.

### Claim 45 (depends on 12, 24, 41, 42, 43, 44)

The method of claim 12, claim 24, claim 41 or any one of claims 42 to 44, wherein the capture identifier is passed as part of a command to modify or capture data from the call stream.

### Claim 46 (depends on 12, 24, 41, 42, 43, 44, 45)

The method of claim 12, claim 24, claim 41 or any one of claims 42 to 45, wherein a command to modify or capture data from the call stream is sent to the data capture device separately from the capture identifier.

### Claim 47 (depends on 12, 24, 41, 42, 43, 44, 45, 46)

The method of claim 12, claim 24, claim 41 or any one of claims 42 to 46, wherein the call stream comprises a signalling stream, and wherein the command and/or capture identifier is passed to the data capture device via the signalling stream as a special message or a message that has been repurposed by special interpretation.

### Claim 48 (depends on 12, 24, 41, 42, 43, 44, 45, 46, 47)

The method of claim 12, claim 24, claim 41 or any one of claims 42 to 47, wherein the call stream comprises an audio stream and wherein the command and/or capture identifier is passed to the device as DTMF tones in the audio stream.

### Claim 49 (depends on 48)

The method of claim 48 further comprising selectively blocking the DTMF tones from being sent to another party present in the audio stream.

### Claim 50 (depends on 12, 24, 41, 42, 43, 44, 45, 46, 47, 48, 49)

The method of claim 12, claim 24, claim 41 or any one of claims 42 to 49, wherein passing the command and/or capture identifier occurs in response to sending or receiving the payment service submission.

### Claim 51 (depends on 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 42, 43, 44, 45, 46, 47, 48, 49, 50)

A server configured to execute the steps of any one of claims 1 to 12, or any one of claims 42 to 50 when dependent on claim 2.

### Claim 52 (depends on 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 42, 43, 44, 45, 46, 47, 48, 49, 50)

An agent computer configured to execute the steps of any one of claims 13 to 24, or any one of claims 42 to 50 when dependent on claim 14.

### Claim 53 (depends on 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 42, 43, 44, 45, 46, 47, 48, 49, 50)

A system comprising:
a data capture device configured to capture data from a call stream;
a server configured to execute the steps of any one of claims 1 to 12, or any one of claims 42 to 50 when dependent on claim 2; and
an agent computer configured to execute the steps of any one of claims 13 to 24, or any one of claims 42 to 50 when dependent on claim 14.

### Claim 54 (depends on 2, 14, 26, 53)

The system of claim 53 when dependent on claim 2, claim 14, or claim 26, wherein the second identifier is constructed at the server and passed to the agent computer.

### Claim 55 (depends on 2, 14, 26, 53)

The system of claim 53 when dependent on claim 2, claim 14 or claim 26, wherein the second identifier is constructed at the agent computer.

### Claim 56 (depends on 53, 54, 55)

The system of any one of claims 53 to 55, wherein the command is passed to the data capture device from the agent computer.

### Claim 57 (depends on 53, 54, 55)

The system of any one of claims 53 to 55, wherein the command is passed to the data capture device from the server.

### Claim 58

A computer-implemented method for capturing data in a call distribution system, the method comprising:
receiving a call stream routed from a telephone network;
sending call metadata associated with the call to a server;
capturing data from the call stream; and
transmitting the data captured from the call stream to the server.

### Claim 59 (depends on 58)

The method of claim 58, comprising receiving an agent identification number and/or an agent telephone or extension number, wherein the call metadata optionally comprises the agent identification number and/or the agent telephone or extension number.

### Claim 60 (depends on 59)

The method of claim 59, wherein the agent identification and/or an agent extension identification is received from an agent.

### Claim 61 (depends on 58, 59, 60)

The method of any one of claims 58 to 60, wherein capturing data from the call comprises continuously capturing data from the call.

### Claim 62 (depends on 58, 59, 60, 61)

The method of any one of claims 58 to 61, wherein capturing data from the call comprises capturing data from the call when it is detected that a call has been put through to an agent.

### Claim 63 (depends on 58, 59, 60, 61, 62)

The method of any one of claims 58 to 62, comprising storing the data captured from the call stream and transmitting the data captured from the call stream in response to receiving a capture identifier associated with the data captured from the call stream.

### Claim 64 (depends on 58, 59, 60, 61, 62, 63)

The method of any one of claims 58 to 63, comprising storing the data captured from the call stream and selectively transmitting the data captured from the call stream to the server based on a rule set comprising a combination of temporal and data content pattern matching.

### Claim 65 (depends on 58, 59, 60, 61, 62, 63, 64)

The method of any one of claims 58 to 64 wherein capturing data from the call comprises capturing data from the call in response to receiving a capture command.

### Claim 66 (depends on 65)

The method of claim 65, wherein the capture command comprises a call identifier associated with the data captured from the call stream, and wherein the call identifier optionally comprises an agent identification number, an agent telephone or extension number, and/or a globally unique identifier.

### Claim 67 (depends on 58, 59, 60, 61, 62, 63, 64, 65, 66)

The method of any one of claims 58 to 66, wherein capturing data from the call comprises capturing DTMF data or capturing audio data using automatic speech recognition.

### Claim 68 (depends on 58, 59, 60, 61, 62, 63, 64, 65, 66, 67)

The method of any one of claims 58 to 67, wherein capturing data from the call comprises capturing data from call signalling or media stream of the call.

### Claim 69 (depends on 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68)

The method of any one of claims 58 to 68, wherein the data is captured from the call stream by means of digit pattern and temporal pattern recognition, optionally wherein received digits are queued before retransmission to allow discernment of patterns.

### Claim 70 (depends on 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69)

The method of any one of claims 58 to 69, wherein the metadata comprises a capture device identification.

### Claim 71 (depends on 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70)

A data capture device configured to execute the method of any one of claims 58 to 70.

### Claim 72 (depends on 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70)

A computer-readable storage medium containing instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 50 or 58 to 70.
