# US 2025/0094968 A1 · System and Method for Payment Hardware System Module (HSM) Integration

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

- Number: US 2025/0094968 A1
- Document ID: US20250094968A1
- Status: Published application
- Kind: A1
- Application number: 18/471,242
- Filed: 2023-09-20
- Published: 2025-03-20
- Earliest claimed: 2023-09-20
- Assignees: Marvell Asia Pte Ltd
- Applicants: Marvell Asia Pte Ltd
- Inventors: Dhanalakshmi Saravanan; Ganeswara Rao Karri; Rajeshekhar Murtinty
- Web page: https://patentgrep.com/patent/US20250094968A1

## CPC

- G06Q 20/3829: {involving key management}
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06Q 20/341: {Active cards, i.e. cards including their own processing means, e.g. including an IC or chip}
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system and corresponding method integrate a payment application and at least one payment hardware system module (HSM). The system comprises a payment system interface (PSI) interposed between a payment application and at least one payment hardware system module (HSM). The PSI implements a standard, payment HSM application programming interface (API) that is payment HSM vendor-agnostic. The PSI enables communication between the payment application and the at least one payment HSM based on the standard, payment HSM API implemented. Since the standard, HSM payment API is payment HSM vendor-agnostic, development effort otherwise expended to develop a connector for each vendor payment HSM integration is avoided.

## Claims

### Claim 1

A system comprising:
a payment system interface (PSI) interposed between a payment application and at least one payment hardware system module (HSM), the PSI configured to implement a standard, payment HSM application programming interface (API) that is payment HSM vendor-agnostic,
the PSI further configured to enable communication between the payment application and the at least one payment HSM based on the standard, payment HSM API implemented.

### Claim 2 (depends on 1)

The system of claim 1, wherein the communication enabled includes bi-directional communications.

### Claim 3 (depends on 1)

The system of claim 1, wherein a payment HSM of the at least one payment HSM is configured to implement a native API, wherein the native API is a payment HSM vendor-specific API, wherein the payment HSM includes at least one memory, wherein the at least one memory is configured to store a PSI library, wherein the PSI library is based on the standard, payment HSM API, and wherein the payment HSM is further configured to use the PSI library stored to:
convert at least one standard, payment HSM API request of the standard, payment HSM API to at least one native API request of the native API and vice versa; and
convert at least one native API response of the native API to at least one standard, payment HSM API response of the standard, payment HSM API and vice versa.

### Claim 4 (depends on 1)

The system of claim 1, wherein the at least one payment HSM includes a plurality of payment hardware system modules (HSMs) with respective native application programming interfaces (APIs) and respective PSI libraries and wherein the respective PSI libraries are based on the standard, payment HSM API.

### Claim 5 (depends on 1)

The system of claim 1, wherein a payment HSM of the at least one payment HSM is a cloud HSM.

### Claim 6 (depends on 1)

The system of claim 1, wherein the standard, payment HSM API is a representational state transfer (REST) API or other type of API.

### Claim 7 (depends on 1)

The system of claim 1, wherein the standard, payment HSM API is based on JavaScript Object Notation (JSON) or another format.

### Claim 8 (depends on 1)

The system of claim 1, wherein the standard, payment HSM API includes at least one standard, payment HSM API request or API response that is based on a tag-length-value (TLV) construction.

### Claim 9 (depends on 1)

The system of claim 1, wherein the system is a cloud-based system.

### Claim 10 (depends on 1)

The system of claim 1, wherein the system is implemented on an integrated circuit (IC) chip.

### Claim 11 (depends on 1)

The system of claim 1, wherein the IC chip is configured to store subscriber identity data or other data, securely, based on at least one standard, payment HSM API request of the standard, payment HSM API.

### Claim 12

A method comprising:
implementing a standard, payment hardware system module (HSM) application programming interface (API) at a payment system interface (PSI), the PSI interposed between a payment application and at least one payment HSM, the payment HSM API being payment HSM vendor-agnostic; and
enabling, at the PSI, communication between the payment application and the at least one payment HSM, the enabling based on the standard, payment HSM API implemented.

### Claim 13 (depends on 12)

The method of claim 12, wherein the communication enabled includes bi-directional communications.

### Claim 14 (depends on 12)

The method of claim 12, further comprising:
implementing a native API by a payment HSM of the at least one payment HSM, wherein the native API is payment HSM vendor-specific API;
storing a PSI library and, based on the PSI library stored:
converting, by the payment HSM, at least one standard, payment HSM API request of the standard, payment HSM API to at least one native API request of the native API and vice versa; and
converting, by the payment HSM, at least one native API response of the native API to at least one standard, payment HSM API response of the standard, payment HSM API and vice versa.

### Claim 15 (depends on 12)

The method of claim 12, wherein the at least one payment HSM includes a plurality of payment hardware system modules (HSMs) with respective native application programming interfaces (APIs) and respective PSI libraries and wherein the respective PSI libraries are based on the standard, payment HSM API.

### Claim 16 (depends on 12)

The method of claim 12, wherein a payment HSM of the at least one payment HSM is a cloud HSM.

### Claim 17 (depends on 12)

The method of claim 12, wherein the standard, payment HSM API is a representational state transfer (REST) API or other type of API.

### Claim 18 (depends on 12)

The method of claim 12, wherein the standard, payment HSM API is based on JavaScript Object Notation (JSON) or another format.

### Claim 19 (depends on 12)

The method of claim 12, wherein the standard, payment HSM API includes at least one standard, payment HSM API request or API response that is based on a tag-length-value (TLV) construction.

### Claim 20 (depends on 12)

The method of claim 12, further comprising implementing the PSI and enabling the bi-directional communications on a cloud-based system.

### Claim 21 (depends on 12)

The method of claim 12, further comprising implementing the PSI and enabling the communication on an integrated circuit (IC) chip.

### Claim 22 (depends on 23)

The method of claim 23, further comprising storing subscriber identity data or other data, securely, on the IC chip based on at least one standard, payment HSM API request of the standard, payment HSM API.

### Claim 23

A non-transitory computer-readable medium having encoded thereon a sequence of instructions which, when loaded and executed by at least one processor, causes the at least one processor to:
implement a standard, payment hardware system module (HSM) application programming interface (API) at a payment system interface (PSI), the PSI interposed between a payment application and at least one payment HSM, the payment HSM API being payment HSM vendor-agnostic; and
enable, at the PSI, communication between the payment application and the at least one payment HSM, the enabling based on the standard, payment HSM API implemented.

### Claim 24

An apparatus comprising:
means for implementing a standard, payment hardware system module (HSM) application programming interface (API) between a payment application and at least one payment HSM, the payment HSM API being payment HSM vendor-agnostic; and
means for enabling communication between the payment application and the at least one payment HSM, the enabling based on the standard, payment HSM API implemented.
