# US 10,503,488 B2 · Updating a payment processing system to conform with a standard

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

- Number: US 10,503,488 B2
- Document ID: US10503488B2
- Status: Granted
- Kind: B2
- Application number: 15/490,302
- Filed: 2017-04-18
- Published: 2018-10-18
- Granted: 2019-12-10
- Earliest claimed: 2017-04-18
- Assignees: NCR Corporation
- Applicants: NCR Corporation
- Inventors: Francesco Maria Lettieri; Mervin Amos; Monish Meiappan
- Web page: https://patentgrep.com/patent/US10503488B2

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 16/23: Updating
- G06Q 20/08: Payment architectures
- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G07F 7/0873: {Details of the card reader}
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- 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
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Examples of a system and method for updating a payment processing system to conform with a standard are generally described. A method may include generating an update code configured to replace or be inserted into an executable code file. The method may include sending the update code to a payment processing system for implementation in the payment processing system. The update code may include validation code or mapping code. The payment processing system may include validation rules or mapping rules.

## Claims

### Claim 1

A method for updating a configuration data structure to conform with a standard, the method comprising:
receiving a standard update;
generating, using information from the standard update, an update code, which is configured to be insertable into an executable code file, wherein the update code replaces a previous version of a standard corresponding to the standard update in the executable code file; and
sending the update code in a configuration code file to a payment processing system for implementation in the payment processing system, wherein the payment processing system includes the executable code file, wherein the payment processing system includes a database with custom validation rules and custom mapping rules, wherein the update code includes validation code and mapping code, and wherein the validation code and the mapping code are configured to be overridden by the custom validation rules and the custom mapping rules, respectively.

### Claim 2 (depends on 1)

The method of claim 1, wherein the validation code, which when executed, causes the payment processing system to determine whether a parsed message includes valid field values.

### Claim 3 (depends on 1)

The method of claim 1, wherein the mapping code, which when executed, causes the payment processing system to convert field values from a parsed message to mapped values.

### Claim 4 (depends on 1)

The method of claim 1, wherein the update code is configured to run automatically on the payment processing system.

### Claim 5 (depends on 1)

The method of claim 1, wherein the update code is changed at the payment processing system to include customizations prior to running on the payment processing system.

### Claim 6 (depends on 1)

The method of claim 1, wherein the update code is configured to, when executed, supplement a configuration customization of the payment processing system while avoiding overwriting the configuration customization of the payment processing system.

### Claim 7 (depends on 1)

The method of claim 1, wherein receiving the standard update includes receiving the standard update from a payment acceptance system, and wherein the update code allows the payment processing system to send a payment in an updated configuration to the payment acceptance system.

### Claim 8

A method comprising:
generating, using information from a standard update, an update code including validation code to validate a financial transaction message and mapping code to convert values in the financial transaction message to mapped values, wherein the update code is configured to replace an executable code file; and
sending the update code in a configuration code file to a payment processing system for implementation in the payment processing system, wherein the payment processing system includes the executable code file, wherein the payment processing system includes a database with a custom validation rule and a custom mapping rule, wherein the validation code is configured to be overridden by the custom validation rule, and wherein the mapping code is configured to be overridden by the custom mapping rule.

### Claim 9 (depends on 8)

The method of claim 8, wherein the update code is configured to parse the financial transaction message before validation.

### Claim 10 (depends on 8)

The method of claim 8, wherein the update code allows the payment processing system to send a payment in an updated configuration to a payment acceptance system.

### Claim 11

A payment processing update system for updating a configuration data structure to conform with a standard, the payment processing update system comprising:
at least one processor; and
a memory storing instructions, which when executed on the at least one processor, configure the at least one processor to:
receive a standard update;
generate, using information from the standard update, an update code, which is configured to be insertable into an executable code file, wherein the update code replaces a previous version of a standard corresponding to the standard update in the executable code file; and
send the update code in a configuration code file to a payment processing system for implementation in the payment processing system, wherein the payment processing system includes the executable code file, wherein the payment processing system includes a database with custom validation rules and custom mapping rules, wherein the update code includes validation code and mapping code, and wherein the validation code and the mapping code are configured to be overridden by the custom validation rules and the custom mapping rules, respectively.

### Claim 12 (depends on 11)

The payment processing update system of claim 11, wherein the validation code, which when executed, causes the payment processing system to determine whether a parsed message includes valid field values.

### Claim 13 (depends on 11)

The payment processing update system of claim 11, wherein the mapping code, which when executed, causes the payment processing system to convert field values from a parsed message to mapped values.

### Claim 14 (depends on 11)

The payment processing update system of claim 11, wherein the update code is configured to run automatically on the payment processing system.

### Claim 15 (depends on 11)

The payment processing update system of claim 11, wherein the update code is changed at the payment processing system to include customizations prior to running on the payment processing system.

### Claim 16 (depends on 11)

The payment processing update system of claim 11, wherein to receive the standard update, the at least one processor is to receive the standard update from a payment acceptance system, and wherein the update code allows the payment processing system to send a payment in an updated configuration to the payment acceptance system.
