Install Jentic One Beta

Connect the Razorpay API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Razorpay API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frazorpay.com%2Frazorpay" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frazorpay.com%2Frazorpay" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Razorpay API.

Create an order with amount and currency, then list the payments made against it via /orders/{id}/payments

Capture an authorized payment by passing amount and currency to /payments/{id}/capture

Refund a payment in full or in part through /payments/{id}/refund, or raise a standalone refund with a payment_id

Send a payment link with an amount, customer details, an expire_by time, and a callback_url, and cancel it if plans change

GET STARTED

Start building with Razorpay API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Razorpay API for, with concrete tasks.

★ Payment operations from an AI agent through Jentic

A support or operations agent often needs to look up a payment and act on it: capture a held payment, refund a disputed one, or check an order's payments. Through Jentic the agent searches for 'refund a Razorpay payment', receives the refund operation with its amount, speed, and notes inputs, and calls it with your key_id and key_secret injected by your self-hosted Jentic One instance. A rule can keep it to reads and refunds, away from transfers.

Call GET /payments/{id} for payment 'pay_29QQoUBi66xm2f', confirm it is captured, then POST /payments/{id}/refund with amount 50000

Order-based checkout

Razorpay checkout starts from an order. A backend creates the order with an amount in paise, a currency, and an optional receipt reference, hands the order id to the checkout, and later reads the order's payments to confirm what was paid. Payments that arrive authorized can be captured with the same amount and currency.

POST /orders with amount 49900, currency 'INR', and receipt 'rcpt_1042', then call GET /orders/{id}/payments to list payments made on the returned order

Collect payments by link or QR code

Businesses without a website collect money by sharing a link or showing a QR code. The payment links operation takes an amount, a description, customer details, notify settings, and an expire_by time, and can be cancelled later. QR codes are created, listed, and closed through their own operations, and virtual accounts give each customer a dedicated receiving account.

POST /payment_links with amount 149900, currency 'INR', description 'Workshop seat', and reference_id 'WS-2207', then share the returned short_url

Subscription billing

Recurring products are modelled as plans, and each customer subscription points at a plan_id with a total_count of billing cycles. The API pauses, resumes, updates, and cancels subscriptions, and addons attach one-off charges to the next cycle. Listing subscriptions accepts a plan_id filter to see everyone on a given plan.

Call GET /subscriptions with plan_id 'plan_00000000000001' to find the customer's subscription, then POST /subscriptions/{id}/pause on it

Settlement reconciliation

Finance teams match bank deposits to the payments, refunds, and fees behind them. The settlements operations list and fetch settlements, and the combined reconciliation report takes year, month, and optional day parameters to return the transactions settled in that window.

Call GET /settlements/recon/combined with year 2026, month 11, and day 11, then total the settled amounts by entity type

Key Endpoints

65 endpoints — the razorpay api accepts and captures payments, issues refunds, and organises the money flow around them for businesses selling in india.

METHOD

PATH

DESCRIPTION

POST

/orders

Create an order

GET

/payments/{id}

Fetch a payment

POST

/payments/{id}/capture

Capture a payment

POST

/payments/{id}/refund

Refund a payment

POST

/payment_links

Create a payment link

POST

/subscriptions

Create a subscription

POST

/invoices/{id}/issue

Issue a draft invoice

GET

/settlements/recon/combined

Combined settlement reconciliation report

POST

/orders

Create an order

GET

/payments/{id}

Fetch a payment

POST

/payments/{id}/capture

Capture a payment

POST

/payments/{id}/refund

Refund a payment

POST

/payment_links

Create a payment link

POST

/subscriptions

Create a subscription

POST

/invoices/{id}/issue

Issue a draft invoice

GET

/settlements/recon/combined

Combined settlement reconciliation report

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Razorpay by hand means building Basic auth from your key_id and key_secret, converting every amount to paise, and paging list endpoints with count and skip. Through Jentic you install once, import the Razorpay API from the API Directory, store the key pair once, and your agent calls it.

Permission scoping

Razorpay puts the target id in the URL path on its fetch and action operations (/payments/{id}/refund, /subscriptions/{id}/pause, /customers/{id}/tokens), so a rule can pin your agent to one customer's tokens or one subscription as well as to chosen operations. You choose the operations it may call, so money-moving ones like transfers or refunds are not included unless you add them.

Credential isolation

Your Razorpay key_id and key_secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'refund a Razorpay payment' or 'create a payment link', and Jentic returns the matching Razorpay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Razorpay API through Jentic.

What authentication does the Razorpay API use?

Per its OpenAPI spec, the Razorpay API uses HTTP Basic authentication with your key_id as the username and key_secret as the password. Through Jentic, the pair is stored encrypted by your own Jentic One instance and injected at execution time, so neither value enters the agent's prompt or logs.

Is there a Razorpay MCP server?

You don't need an MCP server to give your agent the Razorpay API. Jentic connects it directly from the API Directory: import it, store your key_id and key_secret once, and your agent calls it. Operations are discovered on demand, so the agent loads only the Razorpay operation it needs rather than a full set of tool definitions.

Can I limit what my agent is allowed to do with the Razorpay API?

Yes. A support agent could get a rule allowing GET /payments/{id}, GET /orders/{id}/payments, and POST /payments/{id}/refund, so it can look up a payment and refund it while transfers, fund accounts, and invoice deletion stay out of reach. Every call it makes is logged.

Why are Razorpay amounts so large?

The spec states that all amounts are integers in paise, the smallest currency unit. An order for 499 rupees is sent as amount 49900 with currency INR, and the same rule applies to captures, refunds, payment links, and transfers.

Can I issue a partial refund with the Razorpay API?

Yes. POST /payments/{id}/refund accepts an optional amount, so passing less than the captured amount refunds part of the payment, and a speed field sets the refund speed. POST /refunds does the same from a payment_id in the body, and GET /refunds/{id} reads back the refund.

What are the rate limits for the Razorpay API?

The OpenAPI spec does not specify rate limits. Check https://razorpay.com/docs/api for current limits before running bulk jobs such as paging through GET /payments with count and skip.

How do I refund a Razorpay payment through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Razorpay API from the API Directory, and store your key_id and key_secret. Your agent searches for 'refund a Razorpay payment', receives POST /payments/{id}/refund with its input schema, and calls it with the payment id and amount. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Razorpay API

AI ReadinessFoundational (D-)41/100

See full scorecard

PaymentsPayment Processingbasic65 EndpointsREST

For Agents

Create orders, capture and refund payments, send payment links and invoices, run subscriptions, and reconcile settlements on Razorpay, with all amounts in paise.

Use for: I need to capture an authorized Razorpay payment, Refund 50000 paise on a customer's payment, Create a payment link for 1499 rupees that expires tomorrow, List all payments made against an order

Not supported: Does not handle storefront product listings, shipping, tax filing, or accounting ledgers. Use for collecting, refunding, and settling payments on Razorpay only.

The Razorpay API accepts and captures payments, issues refunds, and organises the money flow around them for businesses selling in India. It covers orders, customers and their saved tokens, invoices and items, subscriptions with plans and addons, payment links, QR codes, virtual accounts, transfers with reversals, and settlements with a combined reconciliation report. Every amount is an integer in paise, the smallest currency unit, so 49900 means 499 rupees.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

20%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

48%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

92%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

10%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

76%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Razorpay API to your agent

Capabilities

Start building with Razorpay API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Razorpay API

Jentic AI Readiness Score

Razorpay API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness