Curlec Payments API
A payment is created when a customer completes checkout. Payments can be auto-captured or manually captured. Fetch payment details to reconcile and diagnose failures.
Curlec Payments API is one of 30 APIs that Curlec publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.
This API exposes 4 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://api.razorpay.com/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Curlec Payments API declares
2 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basicAuth).
It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows, exposing 1 scope.
By default, every request must be authenticated.
basicAuth— HTTP Basic authentication using your Razorpay API key pair. Use keyid as the username and keysecret as the password. Encode as Base64(keyid:keysecret). Keys ar…oauth2— 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 ser…
Paths & Operations 4
Across 3 paths, the API surfaces 4 operations — 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
A payment is created when a customer completes checkout. Payments can be auto-captured or manually captured. Fetch payment details to reconcile and diagnose failures.
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Payment (33 properties), CardDetails (9 properties), AcquirerData (4 properties), Collection (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Curlec 12
Other APIs Curlec publishes across the network.
This is an independent, third-party profile of Curlec Payments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.