Curlec · Authentication Profile

Curlec Authentication

Authentication

Curlec secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

CompanyPaymentsPayment GatewayRecurring PaymentsSubscriptionsDirect DebitFinTechMalaysiaDuitNowFPXWebhooksRazorpay
Methods: http, oauth2 Schemes: 2 OAuth flows: authorizationCode, clientCredentials API key in:

Security Schemes

basicAuth http
scheme: basic
oauth2 oauth2
· flows: authorizationCode, clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: derived
source: openapi/curlec-razorpay-openapi.json
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: basicAuth
  type: http
  scheme: basic
  description: HTTP Basic authentication using your Razorpay API key pair. Use key_id as the
    username and key_secret as the password. Encode as Base64(key_id:key_secret). Keys are environment-scoped
    (Test vs Live). Obtain keys at https://dashboard.razorpay.com/app/keys. Keys are case-sensitive.
  sources:
  - openapi/curlec-razorpay-openapi.json
- name: oauth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mcp.razorpay.com/authorize
    tokenUrl: https://mcp.razorpay.com/token
    scopes: 1
  - flow: clientCredentials
    tokenUrl: https://mcp.razorpay.com/token
    scopes: 1
  description: OAuth 2.0 via the Razorpay MCP server (mcp.razorpay.com). Supports Authorization
    Code with PKCE (S256) for user-delegated access and Client Credentials for server-to-server
    access. Tokens expire in 3600 seconds. Dynamic Client Registration available at the registration
    endpoint. For integration setup see https://razorpay.com/docs/build/llm-docs/mcp-server/oauth.md.
  sources:
  - openapi/curlec-razorpay-openapi.json