# US 12,118,536 B2 · Systems and methods for card tokenization via API

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

- Number: US 12,118,536 B2
- Document ID: US12118536B2
- Status: Granted
- Kind: B2
- Application number: 16/809,103
- Filed: 2020-03-04
- Published: 2021-09-09
- Granted: 2024-10-15
- Earliest claimed: 2020-03-04
- Assignees: JPMorgan Chase Bank, N.A.
- Applicants: Jpmorgan Chase Bank, N.A.
- Inventors: Navneet K. Kang; John D. Moore
- Web page: https://patentgrep.com/patent/US12118536B2

## CPC

- G06Q 20/354: {Card activation or deactivation}
- G06Q 10/10: Office automation; Time management
- G06Q 20/321: {using wearable devices}
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/3265: {characterised by personalisation for use}
- G06Q 20/363: {with the personal data of a user}
- G06Q 20/3672: {initialising or reloading thereof}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/401: {Transaction verification}
- G06Q 20/403: {Solvency checks}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- 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

Systems and methods for card tokenization via API are disclosed. In one embodiment, in a financial institution backend comprising at least one computer processor, a method for card provisioning is provided using a digital enablement service via API may include: (1) receiving, from a digital enablement service and using a first API, a provisioning request from a digital wallet executed by an electronic device, the provisioning request identifying an account for tokenizing; (2) decisioning the provisioning request; (3) communicating the decision to the digital enablement service using a second API; (4) receiving, from the digital enablement service via a third API, a token; and (5) updating a cardholder provide with provisioned status for the token.

## Claims

### Claim 1

A method for card provisioning using a digital enablement service via API, comprising:
receiving, at a financial institution backend and from a digital enablement service for a card association via an Application Programming Interface (API), a provisioning request to tokenize an account to a digital wallet executed by an electronic device, the provisioning request comprising an identification of the account, the digital enablement service interfacing with both a third-party wallet provider backend for the digital wallet and the financial institution backend;
approving, by the financial institution backend, the provisioning request;
communicating, by the financial institution backend and to the digital enablement service, the approval;
generating, by the digital enablement service, a payment token for the account in response to receiving the approval;
communicating, by the digital enablement service, the payment token to the third-party wallet provider, wherein the third-party wallet provider provides the payment token to the digital wallet;
presenting, by the financial institution backend and via the digital enablement service to the digital wallet, terms and conditions;
generating, by the digital enablement service, a token activation notice in response to acceptance of the terms and conditions;
sending, by the digital enablement service, the token activation notice to the financial institution backend; and
updating, by the financial institution backend, a cardholder card status for the account with a token provisioned status.

### Claim 2 (depends on 1)

The method of claim 1, wherein the provisioning request is received from the digital wallet via the digital enablement service and a digital wallet provider for the digital wallet.

### Claim 3 (depends on 1)

The method of claim 1, wherein the step of approving the provisioning request comprises determining that the account is eligible for tokenization.

### Claim 4

A method for card provisioning using a digital enablement service via API, comprising:
receiving, at a digital enablement service for a card association and from a third-party wallet provider backend, a provisioning request to tokenize an account to a digital wallet executed by an electronic device, the digital enablement service interfacing with both the third-party wallet provider backend and a financial institution backend and an acquirer;
communicating, by the digital enablement service via an Application Programming Interface (API), the provisioning request to the financial institution backend for a financial institution issuer of the account;
receiving, by the digital enablement service and from the financial institution backend, approval of the provisioning request;
generating, by the digital enablement service, a payment token for the account in response to receiving the approval;
communicating, by the digital enablement service, terms and conditions to the digital wallet;
receiving, by the digital enablement service, acceptance of the terms and conditions from the digital wallet; and
communicating, by the digital enablement service and via the API, a token activation notice in response to the acceptance of the terms and conditions, wherein the financial institution backend updates a cardholder card status for the account with a provisioned status.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
communicating, by the digital enablement service and via the API, the acceptance of the terms and conditions to the financial institution backend.