PayTR Payment API

Name: PayTR Payment API
Brand: PayTR Payment API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey6 EndpointsREST

For Agents

Query transaction statuses, process refunds, look up BIN details, and retrieve installment rates for Turkish payment processing.

Install Jentic One Beta

Connect the PayTR Payment API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PayTR Payment 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 PayTR Payment API.

Query payment status and transaction details by merchant order ID

Process full and partial refunds for completed transactions

Look up BIN details to identify card issuer, type, and brand

GET STARTED

Start building with PayTR Payment API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use PayTR Payment API for, with concrete tasks.

★ Transaction Status Monitoring

Check the real-time status of payments processed through PayTR. Merchants query the status endpoint with their merchant order ID to confirm whether a payment succeeded, failed, or is pending. This is critical for order fulfillment systems that need to verify payment completion before shipping goods or activating services in the Turkish e-commerce market.

Query the payment status for merchant order ID 'ORDER-2024-5678' via POST /odeme/durum-sorgu and return the transaction status and amount

Refund Processing

Issue refunds for completed PayTR transactions. The API supports full and partial refunds via POST /odeme/iade with the original transaction reference and refund amount. Refunds are processed back to the original payment method and appear on the customer's statement within 5-10 business days depending on the issuing bank.

Submit a partial refund of 150 TRY for merchant order ID 'ORDER-2024-1234' via POST /odeme/iade and confirm the refund status

Installment Rate Lookup

Retrieve available installment options for Turkish bank cards before checkout. The API returns installment rates (2, 3, 6, 9, 12 months) with associated commission percentages based on the card BIN. This enables merchants to display accurate installment pricing to customers at checkout, a common expectation in Turkish e-commerce.

Look up available installment rates for BIN 454360 via POST /odeme/taksit-oranlari and return the available month options with commission rates

AI Agent Payment Operations via Jentic

AI agents use the PayTR API through Jentic to check transaction statuses, process refunds, and look up card details for Turkish merchants. Agents search by intent, receive typed schemas with HMAC token generation handled by Jentic, and execute calls without managing the complex token computation from merchant_id, merchant_key, and merchant_salt.

Search Jentic for 'check PayTR transaction status', load the schema for POST /odeme/durum-sorgu, and execute with merchant_oid 'ORDER-2024-9999'

Key Endpoints

6 endpoints — paytr payment api provides payment processing services for turkish merchants.

METHOD

PATH

DESCRIPTION

POST

/odeme/durum-sorgu

Query transaction status by merchant order ID

POST

/odeme/iade

Process a full or partial refund

POST

/odeme/api/bin-detail

Look up BIN details for card identification

POST

/odeme/taksit-oranlari

Retrieve installment rates by card BIN

POST

/rapor/odeme-detayi/

Get payment detail report

POST

/rapor/odeme-dokumu/

Export bulk payment data

POST

/odeme/durum-sorgu

Query transaction status by merchant order ID

POST

/odeme/iade

Process a full or partial refund

POST

/odeme/api/bin-detail

Look up BIN details for card identification

POST

/odeme/taksit-oranlari

Retrieve installment rates by card BIN

POST

/rapor/odeme-detayi/

Get payment detail report

Why Jentic?

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

Credential isolation

PayTR merchant credentials (merchant_id, merchant_key, merchant_salt) are stored encrypted in the Jentic vault. Jentic computes the HMAC-SHA256 paytr_token for each request so agents never handle raw signing material.

Intent-based discovery

Agents search by intent (e.g., 'check payment status in Turkey') and Jentic returns matching PayTR operations with typed schemas and automatic token generation.

Time to first call

Direct PayTR integration: 2-3 days for HMAC token implementation, callback handling, and testing. Through Jentic: under 1 hour — search, load schema, execute with automatic token computation.

FAQs

Specific to using PayTR Payment API through Jentic.

What authentication does the PayTR API use?

The PayTR API uses HMAC-SHA256 token authentication. Each request requires a paytr_token computed from your merchant_id, merchant_key, merchant_salt, and request-specific parameters, then base64-encoded. Through Jentic, this token generation is handled automatically so agents never manage the raw merchant credentials.

Can I process partial refunds with the PayTR API?

Yes. The POST /odeme/iade endpoint accepts a refund amount that can be less than the original transaction total. You provide the merchant order ID and the partial amount in TRY to refund back to the customer's original payment method.

What are the rate limits for the PayTR API?

PayTR applies per-merchant rate limits based on your integration tier. Standard integrations support up to 60 requests per minute. The reporting endpoints (payment detail and bulk export) have lower limits due to heavier processing.

How do I look up installment rates through Jentic?

Search Jentic for 'PayTR installment rates', load the schema for POST /odeme/taksit-oranlari, and execute with the card BIN. Jentic computes the HMAC token automatically and returns the available installment months with their commission percentages.

Does the PayTR API support multiple currencies?

PayTR primarily processes transactions in Turkish Lira (TRY). For international transactions, the conversion is handled at the payment page level. The API endpoints for status, refund, and reporting all return amounts in TRY.

PayTR Payment API

Connect the PayTR Payment API to your agent

Capabilities

Start building with PayTR Payment API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs