NTT DATA Payments API

Name: NTT DATA Payments API API
Brand: NTT DATA Payments API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey3 EndpointsREST

For Agents

Process card and wallet payments, query payment status, and issue refunds through the NTT DATA payment gateway.

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 NTT DATA Payments API 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

GET STARTED

Start building with NTT DATA Payments API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for NTT DATA Payments API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use NTT DATA Payments API 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 though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

NTT DATA merchant API keys are stored encrypted in the Jentic vault. Agents call /payments and /refunds via scoped tokens, so the merchant key is never exposed to the model context.

Intent-based discovery

Agents search Jentic with intents like 'process a card payment in India' or 'refund a captured payment' and Jentic returns the matching NTT DATA operation with its input schema.

Time to first call

Direct NTT DATA integration: 2-3 days for auth, status polling, and refund handling. Through Jentic: under an hour — search, load, execute.

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.

Alternative

Adyen Checkout

Global checkout API used by enterprise merchants

Pick Adyen when the merchant needs unified global acquiring; pick NTT DATA for India-first deployments with local payment methods.

Complementary

PayPal Invoicing

Send and collect invoices via PayPal alongside gateway-captured card payments

Use PayPal Invoicing for B2B invoice collection while NTT DATA captures consumer card and UPI payments at checkout.

FAQs

Specific to using NTT DATA Payments API 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 at https://app.jentic.com/sign-up.

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.