# US 2022/0092560 A1 · System and method for real-time three-party transaction processing

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

- Number: US 2022/0092560 A1
- Document ID: US20220092560A1
- Status: Published application
- Kind: A1
- Application number: 17/420,935
- Filed: 2020-02-03
- Published: 2022-03-24
- Earliest claimed: 2019-02-11
- Assignees: Amadeus S.A.S.
- Applicants: Amadeus S.A.S.
- Inventors: Maxence Achille Henri MALPARTY; Nicolas Dominique Marcel GUILLON; Jose Vicente DA CRUZ; Jean-Pierre BOUTHERIN; Olivier Alexandre ROTH
- Web page: https://patentgrep.com/patent/US20220092560A1

## CPC

- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 30/04: Billing or invoicing
- G06Q 20/027: {involving a payment switch or gateway}
- G06Q 20/102: {Bill distribution or payments}
- G06Q 20/14: specially adapted for billing systems
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- 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 method of intermediating transactions includes, at an intermediation server: receiving invoice data defining a price payable to a vendor for supplying a product to a customer; extracting, from the invoice data, a vendor identifier corresponding to the vendor; determining, in association with the invoice data, a customer identifier corresponding to the customer; retrieving a payer identifier corresponding to a payer associated with the customer; retrieving, based on at least the payer identifier, a transaction policy; according to the retrieved transaction policy, allocating an eligible portion of the price to the payer identifier, and allocating a remaining portion of the price to the customer identifier; and generating and transmitting payment data for initiating a payment of the eligible portion from the payer to the vendor.

## Claims

### Claim 1

A method of real-time three-party transaction processing, comprising, at an intermediation server:
receiving invoice data defining a price payable to a vendor for supplying a product to a customer;
prior to initiation of a payment to the vendor for supplying the product:
extracting, from the invoice data, a vendor identifier corresponding to the vendor;
selecting, based on the invoice data, a customer identification mechanism;
determining, in association with the invoice data, a customer identifier corresponding to the customer according to the selected customer identification mechanism;
retrieving a payer identifier corresponding to a payer associated with the customer;
retrieving, based on at least the payer identifier, a transaction policy;
according to the retrieved transaction policy, allocating an eligible portion of the price to the payer identifier, and allocating a remaining portion of the price to the customer identifier; and
generating and transmitting payment data for initiating a payment of the eligible portion from the payer to the vendor.

### Claim 2 (depends on 1)

The method of claim 1, wherein receiving the invoice data comprises:
receiving the invoice data from a vendor computing device corresponding to the vendor identifier.

### Claim 3 (depends on 2)

The method of claim 2, wherein determining the customer identifier comprises extracting the customer identifier from the invoice data.

### Claim 4 (depends on 2)

The method of claim 2, wherein determining the customer identifier comprises:
obtaining a unique invoice identifier; and
receiving an association request from a customer computing device corresponding to the customer identifier, the association request containing the unique invoice identifier.

### Claim 5 (depends on 4)

The method of claim 4, wherein obtaining the unique invoice identifier comprises generating the unique identifier and transmitting the unique identifier to the vendor computing device for capture by the customer computing device.

### Claim 6 (depends on 1)

The method of claim 1, wherein receiving the invoice data comprises receiving invoice data from a customer computing device corresponding to the customer identifier.

### Claim 7 (depends on 6)

The method of claim 6, wherein extracting the vendor identifier comprises performing optical character recognition on the invoice data

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
when the remaining portion is non-zero, transmitting a notification to a customer computing device corresponding to the customer identifier, the notification containing an indication of the remaining portion.

### Claim 9 (depends on 1)

The method of claim 1, wherein generating and transmitting the payment data comprises:
requesting the payment data from an external payment system; and
transmitting the payment data to a customer computing device corresponding to the customer identifier for presentation to a vendor computing device corresponding to the vendor identifier to effect the payment.

### Claim 10 (depends on 1)

The method of claim 1, wherein generating and transmitting the payment data comprises:
sending a payment instruction to an external payment system to effect the payment; and
sending payment notifications to each of (i) a customer computing device corresponding to the customer identifier and (ii) a vendor computing device corresponding to the vendor identifier.

### Claim 11

An intermediation server comprising:
a communications interface; and
a processor interconnected with the communications interface, the processor configured to:
receive invoice data defining a price payable to a vendor for supplying a product to a customer;
prior to initiation of a payment to the vendor for supplying the product:
extract, from the invoice data, a vendor identifier corresponding to the vendor;
select, based on the invoice data, a customer identification mechanism;
determine, in association with the invoice data, a customer identifier corresponding to the customer according to the selected customer identification mechanism;
retrieve a payer identifier corresponding to a payer associated with the customer;
retrieve, based on at least the payer identifier, a transaction policy;
according to the retrieved transaction policy, allocate an eligible portion of the price to the payer identifier, and allocate a remaining portion of the price to the customer identifier; and
generate and transmit, via the communications interface, payment data for initiating a payment of the eligible portion from the payer to the vendor.

### Claim 12

(canceled)

### Claim 13

A system for real-time three-party transaction processing, comprising:
(i) a vendor computing device associated with a vendor, and configured to generate invoice data defining a price payable to the vendor for supplying a product to a customer;
(ii) an intermediation server configured to:
receive the invoice data via a network;
extract, from the invoice data, a vendor identifier corresponding to the vendor;
determine, in association with the invoice data, a customer identifier corresponding to the customer;
retrieve a payer identifier corresponding to a payer associated with the customer;
retrieve, based on at least the payer identifier, a transaction policy;
according to the retrieved transaction policy, allocate an eligible portion of the price to the payer identifier, and allocate a remaining portion of the price to the customer identifier;
generate and transmit payment data, via the network, for initiating a payment of the eligible portion from the payer to the vendor; and
(iii) a customer computing device associated with the customer, the customer computing device configured to:
receive the payment data from the intermediation server via the network; and
present the payment data for receipt by the vendor computing device to execute the payment of the eligible portion.

### Claim 14 (depends on 13)

The system of claim 13, wherein the intermediation server is further configured, to generate the payment data, to request a virtual card number (VCN) from a payment subsystem connected with the intermediation server via the network; and
wherein the customer computing device is configured to receive and present the VCN to the vendor computing device.

### Claim 15 (depends on 14)

The system of claim 14, wherein the vendor computing device is configured to execute the payment of the eligible portion by transmitting the VCN to the payment subsystem.

### Claim 16 (depends on 13)

The system of claim 13, wherein the vendor computing device is configured to transmit the invoice data to the intermediation server via the network.

### Claim 17 (depends on 16)

The system of claim 16, wherein the intermediation server is configured, responsive to receiving the invoice data from the vendor computing device, to obtain a unique invoice identifier and transmit the unique invoice identifier to the vendor computing device for presentation to the customer computing device;
wherein the customer computing is configured to capture the unique invoice identifier and transmit an association request containing the customer identifier and the unique invoice identifier to the intermediation server via the network; and
wherein the intermediation server is configured to determine the customer identifier by retrieving the customer identifier from the association request.

### Claim 18 (depends on 13)

The system of claim 13, wherein the customer computing device is configured to capture the invoice data and transmit the invoice data to the intermediation server via the network.

### Claim 19 (depends on 11)

The intermediation server of claim 11, wherein the processor is configured to receive the invoice data by:
receiving the invoice data from a vendor computing device corresponding to the vendor identifier.

### Claim 20 (depends on 19)

The intermediation server of claim 19, wherein the processor is configured to determine the customer identifier by extracting the customer identifier from the invoice data.

### Claim 21 (depends on 19)

The intermediation server of claim 19, wherein the processor is configured to determine the customer identifier by:
obtaining a unique invoice identifier; and
receiving an association request from a customer computing device corresponding to the customer identifier, the association request containing the unique invoice identifier.

### Claim 22 (depends on 21)

The intermediation server of claim 21, wherein the processor is configured to obtain the unique invoice identifier by generating the unique identifier and transmitting the unique identifier to the vendor computing device for capture by the customer computing device.

### Claim 23 (depends on 11)

The intermediation server of claim 11, wherein the processor is configured to receive the invoice data by receiving invoice data from a customer computing device corresponding to the customer identifier.

### Claim 24 (depends on 23)

The intermediation server of claim 23, wherein the processor is configured to extract the vendor identifier by performing optical character recognition on the invoice data.

### Claim 25 (depends on 11)

The intermediation server of claim 11, the processor is further configured to:
when the remaining portion is non-zero, transmit a notification to a customer computing device corresponding to the customer identifier, the notification containing an indication of the remaining portion.

### Claim 26 (depends on 11)

The intermediation server of claim 11, wherein the processor is configured to generate and transmit the payment data by:
requesting the payment data from an external payment system; and
transmitting the payment data to a customer computing device corresponding to the customer identifier for presentation to a vendor computing device corresponding to the vendor identifier to effect the payment.

### Claim 27 (depends on 11)

The intermediation server of claim 11, wherein the processor is configured to generate and transmit the payment data by:
sending a payment instruction to an external payment system to effect the payment; and
sending payment notifications to each of (i) a customer computing device corresponding to the customer identifier and (ii) a vendor computing device corresponding to the vendor identifier.
