How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Curlec website screenshot

Curlec

Curlec (Razorpay Curlec) is a Malaysian online payment solution and part of Razorpay, the RBI-authorised full-stack payment platform. Curlec lets businesses in Malaysia accept one-time and recurring payments through a Payment Gateway, Payment Links, Payment Pages, Payment Buttons, hosted Checkout, DuitNow real-time payments, FPX online banking, cards and e-wallets, plus Subscriptions and direct-debit recurring billing. It runs on the shared Razorpay REST API (https://api.razorpay.com/v1) — a RESTful, JSON, Basic-Auth API covering Orders, Payments, Refunds, Settlements, Disputes, Customers, Invoices, Plans, Subscriptions, Payment Links, QR Codes, Virtual Accounts, Transfers/Route, and the RazorpayX business-banking and payouts suite. Curlec exposes official server SDKs, webhooks, a sandbox test mode, a public Postman workspace, and an official hosted MCP server for AI-agent access.

agent native

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Curlec the way a machine reads it — 97 machine-readable artifacts across 30 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Curlec scores 61.7/100 (strong), with a separate agent-readiness read of 62/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 61.7/100 · strong
Contract Quality 17.6 / 25
Developer Ergonomics 16.0 / 20
Commercial Clarity 10.5 / 20
Operational Transparency 6.8 / 13
Governance 2.5 / 12
Discoverability 8.2 / 10
Regulatory · Payments 9.4 / 15
Agent readiness — 62/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract derived 2.5 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9.0 / 9
Stable Error Semantics documented 4.0 / 8
Request/Response Examples partial 3.5 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills derived 1.3 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card flavored 2.0 / 8
Dry-Run / Simulate Mode 0 / 4
Curlec Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Curlec's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/curlec/"
   title="Curlec on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/curlec.svg"
       alt="Curlec Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Curlec

Each block below is one kind of artifact we hold for Curlec. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 30

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Curlec Bills API

Razorpay Billme digital receipts and bills for retail, food & beverage, events, and ecommerce.

Curlec Customers API

Customer profiles store contact information for recurring billing, saved cards, and personalised checkout. Each email+contact combination must be unique.

Curlec Disputes API

Disputes (chargebacks) are raised by customers via their bank. You can accept (lose) or contest (challenge with evidence) each dispute. Monitor respond_by timestamp — missing th...

Curlec Documents API

Document uploads for dispute evidence. Upload JPEG, PNG, or PDF files and receive a document ID to reference in dispute contest submissions.

Curlec Instant Settlements API

On-demand settlements let you transfer your available Razorpay balance to your bank account immediately, outside the normal settlement cycle. Fees apply. Requires Instant Settle...

Curlec Invoices API

Invoices and payment pages for one-time or partial-payment collection. Create in draft, issue to the customer, and track payment status. Cannot be used for GST invoices (use the...

Curlec Items API

Reusable catalog items that can be referenced in invoice line items. Defining items once avoids repeating price and description on each invoice.

Curlec Linked Accounts API

Sub-merchant accounts (Linked Accounts) created under a Route marketplace. Includes account creation, stakeholder KYC, and Route product activation. Uses /v2/ API base path. Onl...

Curlec Orders API

Orders are the starting point for accepting a payment. Create an order with the amount and currency, pass the order_id to Razorpay Checkout, then verify the payment signature af...

Curlec Partner Accounts API

Sub-merchant account lifecycle management via Partners API (Aggregator/Platform model). Uses OAuth access_token authentication.

Curlec Partner Documents API

Upload and fetch KYC documents for sub-merchant accounts and their stakeholders.

Curlec Partner Stakeholders API

Manage stakeholders (directors/executives) for sub-merchant accounts. Multiple stakeholders allowed per account.

Curlec Partner Webhooks API

Configure webhooks for sub-merchant accounts to receive payment events. Maximum 30 per account.

Curlec Payment Downtimes API

Scheduled and live downtime information for card, netbanking, and UPI. Poll or subscribe to payment.downtime webhooks to detect degraded methods and adjust your checkout UI.

Curlec Payment Links API

Payment Links are shareable URLs to collect payments without a website. Share via SMS, email, or any channel. Supports partial payments, expiry, reminders, UPI-only mode, offers...

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 Plans API

Billing plan definitions for recurring subscriptions. A plan sets the billing period, interval, and per-cycle charge. Plans are reusable across multiple subscriptions and cannot...

Curlec QR Codes API

QR Codes enable offline and digital payment collection. Customers scan with any UPI or card app. Supports fixed-amount and variable-amount codes, single-use and multiple-use modes.

Curlec Refunds API

Refunds return captured payment amounts to customers. Normal refunds take 5-7 business days. Instant (optimum) refunds settle immediately but may fall back to normal. Use X-Refu...

Curlec Settlements API

Settlements represent batch transfers of collected payment funds to your bank account. Use the recon endpoint for transaction-level reconciliation reports mapping each payment, ...

Curlec Subscriptions API

Recurring billing subscriptions. Customers must authorize a payment mandate (UPI Autopay, NACH, or card-on-file) via the short_url before charges begin. Supports pause/resume, p...

Curlec Transfers API

Fund transfers from a merchant, payment, or order to a Linked Account (Route). Supports payment-based splits, direct on-demand transfers, settlement hold controls, and full/part...

Curlec Virtual Accounts API

Virtual bank accounts and UPI VPAs that accept NEFT/RTGS/IMPS/UPI payments (Smart Collect). Each incoming payment creates a BankTransfer entity. Supports Third Party Validation ...

Curlec X Account Validation API

Penny drop and reverse penny drop bank/VPA validation

Curlec X Banking Balances API

Fetch RazorpayX account balances

Curlec X Contacts API

RazorpayX payout recipients — create, fetch, update contacts

Curlec X Fund Accounts API

Payout destination accounts (bank, VPA, card) linked to contacts

Curlec X Payout Links API

Payout links for recipients without saved fund accounts

Curlec X Payouts API

Disbursements via NEFT, RTGS, IMPS, UPI, card — includes composite and approval flows

Curlec X Transactions API

Fetch RazorpayX transaction records — credits (bank_transfer inflows) and debits (payout outflows)

Scroll within the panel for all 30 ·

Postman Collections 30

A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.

Ready-to-run Postman collections for exercising this provider's APIs.

Scroll within the panel for all 30 ·

Open Collections 31

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 31 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

curlec-mcp.yml

MCP SERVER

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Curlec Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Curlec Authentication

http/oauth2 · 2 schemes

SECURITY

Curlec Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Curlec Scopes

1 scope · authorizationCode/clientCredentials

1 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Curlec Agentic Access

136 operations · 73 acting

136 operations · 73 acting

AGENTIC

Resources

Every other property we hold for Curlec — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 2

Reference material describing how the API behaves

Access & Security 3

Authentication, authorization, and security posture

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/curlec · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Curlec, 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.