NovoPayment · OAuth Scopes

NovoPayment OAuth Scopes

OAuth 2.0 derived

NovoPayment uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://sandbox-api.novopayment.com/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

PaymentsBanking as a ServiceEmbedded FinanceCard IssuingDigital WalletTokenizationReal-Time PaymentsOnboardingKYCLatin AmericaFintechDigital Banking
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://sandbox-api.novopayment.com/oauth2/token
Flows
clientCredentials

Scopes (0)

NovoPayment implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

NovoPayment declares an OAuth2 clientCredentials flow with an EMPTY scopes map in all 12 specs that carry it, and publishes no scope or permission reference page. Access is partitioned by which APIs a project selects in the developer hub dashboard, not by scope on the token — so a token cannot be least-privileged within a project.

📄 Provider scope reference: https://developer.novopayment.com/api/data-encryption/oauth2-data-encryption-api-v1.0

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-17'
method: derived
source: openapi/novopayment-accounts-openapi.yml, openapi/novopayment-alias-directory-openapi.yml, openapi/novopayment-cards-openapi.yml,
  openapi/novopayment-compliance-openapi.yml, openapi/novopayment-customers-openapi.yml, openapi/novopayment-mastercard-issuer-tokenization-openapi.yml,
  openapi/novopayment-merchant-presented-qr-openapi.yml, openapi/novopayment-onboarding-openapi.yml, openapi/novopayment-operations-openapi.yml,
  openapi/novopayment-profile-openapi.yml, openapi/novopayment-push-provisioning-openapi.yml, openapi/novopayment-real-time-payments-openapi.yml
schemes:
- name: oAuth2ClientCredentials
  source: openapi/novopayment-accounts-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-alias-directory-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-cards-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-compliance-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-customers-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-mastercard-issuer-tokenization-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-merchant-presented-qr-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-onboarding-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-operations-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-profile-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-push-provisioning-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
- name: oAuth2ClientCredentials
  source: openapi/novopayment-real-time-payments-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://sandbox-api.novopayment.com/oauth2/token
  description: See [Oauth2 API](https://developer.novopayment.com/api/authentication-method-and-encryption/oauth2-api)
scopes: []
docs: https://developer.novopayment.com/api/data-encryption/oauth2-data-encryption-api-v1.0
scope_count: 0
note: NovoPayment declares an OAuth2 clientCredentials flow with an EMPTY scopes map in all 12 specs that carry
  it, and publishes no scope or permission reference page. Access is partitioned by which APIs a project selects
  in the developer hub dashboard, not by scope on the token — so a token cannot be least-privileged within a project.
searched:
- url: https://developer.novopayment.com/api/data-encryption/oauth2-data-encryption-api-v1.0
  status: 200
  result: token issuance documented; no scopes
- url: https://developer.novopayment.com/guides/how-it-works/get-access-token
  status: 200
  result: no scope or permission reference

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • 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 scope set 
curl "https://apis.io/api/v1/scopes/novopayment-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

GitHub Google LinkedIn

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