Redotpay · OAuth Scopes

Redotpay OAuth Scopes

OAuth 2.0 searched

Redotpay 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.

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.

CompanyPaymentsFintechStablecoinCryptocurrencyWalletAgentic PaymentsMachine Payments Protocolx402OAuth

Scopes: 0 Flows: Method: searched

Scopes (0)

Redotpay 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.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: https://github.com/redotpay/redotpay-cli (config.example.toml, SKILL.md CLI appendix)
description: >-
  OAuth2 scopes used by RedotPay agentic payments. Derived from the first-party redotpay CLI /
  redotpay-payment configuration and skill (no public OpenAPI or scopes reference page is published).
oauth_flow: device_authorization
scopes:
- name: mpp_charge
  description: >-
    Authorize the client/agent to settle Machine Payments Protocol (MPP) charges on the user's behalf
    (e.g. `redotpay-payment auth start --scope mpp_charge`). Grants the ability to obtain a payment
    credential and complete 402 payments.