Nttdatapay NTT DATA Payments API
Agent-ready OpenAPI document · curated by JenticPaymentsPayment ProcessingapiKey3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Process card and wallet payments, query payment status, and issue refunds through the NTT DATA payment gateway.
Use for: Process a card payment through NTT DATA, Get the current status of a payment by ID, Issue a refund for a completed NTT DATA payment, Check whether an INR payment cleared on the NTT DATA gateway
Not supported: Does not handle accounting, KYC onboarding, or merchant settlement reporting - use for capturing payments and issuing refunds only.
Jentic publishes the only available OpenAPI specification for NTT DATA Payments API, keeping it validated and agent-ready. NTT DATA Payments is a payment gateway used widely across the Indian market for processing card, UPI, netbanking, and wallet payments for merchants. The API exposes endpoints to create a payment, query payment status, and process refunds against a prior transaction. It is typically integrated by e-commerce checkouts, billing platforms, and SaaS subscriptions that need INR-denominated card and wallet acceptance.
Install Jentic One Beta
Connect the NTT DATA Payments API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NTT DATA Payments 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.
1
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%2Fnttdatapay.com%2Fnttdatapay" | sh2
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%2Fnttdatapay.com%2Fnttdatapay" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 NTT DATA Payments API.
Submit a new payment for capture through the NTT DATA gateway
Query the current status of a previously submitted payment by ID
Issue a refund against a captured payment for full or partial amounts
Reconcile checkout flows by polling payment status until terminal state
Wire NTT DATA payment results into order management and ledger systems
Trigger refunds programmatically for cancelled orders or chargeback-prevention flows
Use Cases
Patterns agents use NTT DATA Payments API for, with concrete tasks.
★ E-Commerce Checkout for India
Indian e-commerce sites accept card, netbanking, UPI, and wallet payments at checkout by submitting a payment to the NTT DATA gateway and polling status until the transaction is captured or fails. The API returns a payment record with status, amount, and method that the storefront uses to mark the order as paid. Integration usually completes within a couple of days for card and wallet flows.
Call POST /payments with INR amount and order reference, then poll GET /payments/{id} until status is captured
Order Cancellation and Refunds
Operations teams handle cancellations and disputes by issuing a refund through POST /refunds with the original payment reference. The NTT DATA gateway pushes the refund back to the customer's source instrument. This flow is used for return-merchandise, fraud-cancellations, and partial-shipment refunds.
Call POST /refunds with the original payment ID and the refund amount, then confirm the refund record was created
Agent-Driven Payment Reconciliation
An AI agent watching a queue of pending orders polls NTT DATA payment status, marks orders paid in the ERP, and triggers fulfilment. Through Jentic the agent searches for 'check payment status', loads the GET /payments/{id} schema, and executes the call without bespoke gateway code.
Search Jentic for 'check NTT DATA payment status', load the schema for GET /payments/{id}, and execute for each pending order ID
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for ntt data payments api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/payments
Process a new payment
GET
/payments/{id}
Get payment status by ID
POST
/refunds
Process a refund
POST
/payments
Process a new payment
GET
/payments/{id}
Get payment status by ID
POST
/refunds
Process a refund
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the NTT DATA Payments API by hand means passing your merchant key in the Authorization header on every call to api.nttdatapay.com and mapping the payment capture, lookup, and refund operations yourself. Through Jentic you install once, import the NTT DATA Payments API from the API Directory, store the merchant key once, and your agent calls it.
Permission scoping
This API puts the payment id in the URL path (/payments/{id}), so a rule can pin your agent to reading one payment. You choose the operations it may call, so capturing payments and issuing refunds are not included unless you add them.
Credential isolation
Your NTT DATA merchant API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'process a card payment in India' or 'refund a captured payment', and Jentic returns the matching NTT DATA operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Global card processor with broader currency and method coverage than NTT DATA
Choose Stripe for international or non-INR flows; choose NTT DATA when the merchant of record sits in India and needs domestic UPI and netbanking acceptance.
FAQs
Specific to using NTT DATA Payments API through Jentic.
Why is there no official OpenAPI spec for NTT DATA Payments API?
NTT DATA Payments does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NTT DATA Payments API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the NTT DATA Payments API use?
The spec declares an API key scheme. Through Jentic the merchant API key is stored encrypted in the vault and injected at execution time, so it never lands in agent prompts or chat history.
Can I check the status of a payment after submission?
Yes. Call GET /payments/{id} with the payment identifier returned from POST /payments. The response includes the current state of the transaction, which you should poll until it reaches a terminal status.
How do I issue a refund through the NTT DATA Payments API?
Call POST /refunds with the original payment identifier and the refund amount. The gateway processes the refund back to the customer's source instrument. Through Jentic, search for 'issue NTT DATA refund' and execute the loaded schema.
What are the rate limits for the NTT DATA Payments API?
The OpenAPI spec does not declare explicit rate limits. NTT DATA enforces production limits per merchant agreement; check your gateway dashboard or contact your account manager for the quota that applies to your merchant ID.
How do I process a payment through Jentic?
Run pip install jentic, then search for 'process a card payment', load the schema for POST /payments, and execute with your order reference and amount. Jentic injects the API key from the vault and returns the parsed payment record.
Can I limit what my agent is allowed to do with the NTT DATA Payments API?
Yes. Jentic One is self-hosted, so your own rules decide which NTT DATA operations the agent may call and which credentials it may use. Because the payment id sits in the URL path at GET /payments/{id}, you can pin the agent to reading a single payment's status while leaving POST /payments and POST /refunds off unless you explicitly allow them. That means capturing payments and issuing refunds happen only when you have granted those operations.
GET STARTED