NovoPayment Life Cycle Management API

The Life Cycle Management API from NovoPayment — 5 operation(s) for life cycle management.

GitHub OpenAPI

Operations 5

POST /itsp/{clientID}/vtis/v1/pan/lifecycle PAN Lifecycle #
POST /itsp/{clientID}/vtis/v1/tokens/lifecycle Token Lifecycle #
POST /itsp/{clientID}/vtis/v1/pan/retrieveTokenInfo Token Inquiry by PAN #
POST /itsp/{clientID}/vtis/v1/tokens/details Token Inquiry #
POST /itsp/{clientID}/vtis/v1/updateCardMetadata Update card Metadata #

Documentation

📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
Documentation
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0
📖
APIReference
https://developer.novopayment.com/api/tokenization/issuer-tokenization-api-v1.0

Specifications

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/novopayment:novopayment-life-cycle-management-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

novopayment-life-cycle-management-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  description: 'NovoPayment, as a Token Service Provider, has a collection of APIs that enables Issuers to participate in the Tokenization ecosystem; we are responsible for the interaction between the Issuer and the franchises. Providing security in the process, ease of implementation and support for your development teams throughout the project. The integration between the Issuer and this portfolio services are with API Rest, all these services are useful for the Issuer, who is responsible for providing the cards and carrying out the process of validation and approval of the tokens. The set of APIs that the Issuer needs to develop are listed below, depending on the relation between Novo and the client. When an issuer is a client of our issuance services, the verification and approval processes are performed by us. For that reason, only need to develop

    this set of APIs:

    - Sendpasscode

    - Notification

    - Token Inquiry

    - Token Inquiry by PAN

    - Token Lifecycle

    - PAN Lifecycle

    - Update card metadata


    If the Issuer has its own system to issued and manage cards, also will need

    to develop these APIs:


    - Check Eligibility

    - Approve Provisioning

    - Get Cardholder Verification Methods

    - Device Token Binding


    ## Header Params


    HTTP headers allow the client and server to pass additional information with

    the request or response. ### HTTP Header fields


    | Name| Description| Data Type| Required/

    Optional/

    Conditional|

    |-|-|-|-|

    | X-REQUEST-ID | Unique ID for the API request. This ID is the reference in all the API’s processes.| String (1-36)| Required|

    | Accept | Content types that are acceptable related to this operation. Sample: application / json; charset = UTF-8 | String | Required|

    | Content-Type | Response body type. Operation related information. Sample: application / json; charset = UTF-8 | String | It is not required if the body of the request is empty, like a “GET” request.|

    | Accept-Language | Language accepted in the response. Sample: en-US. The default value is "en-US". | String | Optional|

    | Content-Language | Language of the request. Sample: en-US. The default value is "en-US". | String | Optional|

    | apikey | Obtained Client ID in NovoPayment’s developer hub, that identifies the client that sends the request. Sample: dbhCR5oPkopFI7OXmGkYFDVpmABxuWMx | String | Required|


    ## Security


    This section describes the encryption and decryption strategies to protect

    sensitive information. ### Data Encryption


    The body fields sent by the issuer to the I-TSP in the request have

    confidential information that must be encrypted with JWE (JSON Web Encryption)

    and JWS( JSON Web Signature)


    ### JWE Composition


    The following format specifies the encrypted body fields of the plain text

    representation. Base64URL (UTF8 (header JWE)) || ''.'' || Base64URL (encrypted key JWE) ||

    ''.''|| Base64URL (initialization vector JWE) ||

    ''.'' || Base64URL (encrypted text JWE) || ''.'' || Base64URL (JWE authentication tag)


    ### JWE Header


    The JWE Header contains the following metadata for the encryption and decryption. | Name | Description | Data type | Required/

    Optional/

    Conditional |

    |-|-|-|-|

    | alg | The value is RSA-OAEP-256 | Enum | Required |

    | kid | Identifier of the key to be used. | String (64) | Optional |

    | typ | The value is JOSE | String (32) | Required |

    | enc | The value is A256GCM | Enum | Required |


    ### JWS Composition


    The following format specifies the encrypted body fields of the plain text

    representation. Base64URL (UTF-8 (header JWS)) || ''.'' || Base64URL (JWE) || ''.'' ||

    Base64URL (signature JWS)


    ### JWS Header


    The JWS Header contains the following metadata for the encryption and

    decryption. | Name | Description | Data type | (length) | Required/

    Optional/

    Conditional |

    |-|-|-|-|-|

    | alg | The value is PS256 | Enum | | Required |

    | kid | Identifier of the key used to signed.'
  version: v1.0
  title: Issuer Tokenization Life Cycle Management API
servers:
- description: UAT
  url: https://cert-api.novopayment.com
tags:


# --- truncated at 32 KB (87 KB total) ---
# Full source: https://artifacts.apis.io/novopayment/openapi/novopayment-life-cycle-management-api-openapi.yml