Paytm Payment Gateway

**Unified order discovery:** use this tool both for **listing orders in a date range** (same intent as the former merchant-passbook ``fetch_order_list`` tool) and for **looking up by Paytm EXT serial** (``EXT_SERIAL_NO`` via ``transaction_id``). **Order list (date range):** Retrieves biz orders whose created time falls between ``start_date`` and ``end_date`` (inclusive, **YYYY-MM-DD**). Paginate with ``page_num`` and ``page_size`` (default 20, max 100). This tool supports retrieving orders across any date range; use pagination to navigate through large result sets. **By transaction id:** Pass ``transaction_id`` (maps to **EXT_SERIAL_NO**) together with dates that bracket when the transaction occurred. **Merchant scope:** Each request includes ``searchConditions`` with **MERCHANT_ID** set to the authenticated merchant (from the Bearer token / onboarding). **Order status filter:** Pass ``order_statuses`` to set request body ``orderStatuses`` (a list). Each value must be one of: **PREPARE**, **PROCESSING**, **SUCCESS**, **CLOSE**, **FAILED** (matching is case-insensitive). Examples: only successful orders → ``["SUCCESS"]``; failed or closed → ``["FAILED", "CLOSE"]``. Omit ``order_statuses`` to retrieve orders of all statuses. **Mapping from old passbook filters:** ``order_search_type`` / ``order_search_status`` / ``is_sort`` are not separate fields here; narrow results using date bounds, ``transaction_id``, ``order_statuses``, and pagination. **Output (always tabular):** Do **not** dump raw JSON for order rows. Return **only** a **Markdown pipe table** (one row per order in ``response.body.orders[]``) with these columns: **Transaction ID** (``bizOrderId``), **Order ID** (``merchantTransId``), **Order Status** (``orderStatus``), **Order Created Time** (``orderCreatedTime``), **Order Completed Time** (``orderCompletedTime``), **Amount(Rs)** (``payMoneyAmount.value`` as paisa ÷ 100, two decimals, ₹ prefix), **Pay Mode** (``payMethod``). If a field is missing, null, or blank for an order, leave that cell empty. **Display rule (assistants / clients):** When showing this tool's result to the user, **do not modify the table header row**. Reproduce the Markdown header cells **exactly** as in the tool output—same names, spelling, spacing, punctuation (e.g. **Amount(Rs)**), and column order. Do not rename headers, translate them, abbreviate them, or rebuild the table with different column titles. **Required:** ``start_date``, ``end_date``. **Optional:** ``transaction_id``, ``order_statuses``, ``page_num``, ``page_size``.

**When to call:** The user has a **single Paytm biz order id** and needs **order** and/or **settlement** detail for that id (payment legs, amounts, status, merchant trans id, settlement bill / payout fields when returned by Paytm, etc.). **Completeness:** This tool is **sufficient** for that use case—one successful call returns **orderDetailQuery** payload for the order. **Do not** chain other tools (e.g. ``fetch_all_orders``, ``fetch_order_status``) solely to duplicate the same biz-order settlement/order story unless the user explicitly wants a different channel (e.g. txn status API). **Settlement flags:** Set ``is_settlement_info`` and ``settlement_info`` to **True** when the user asks for settlement / payout / UTR-style context for this biz order; both default to False. **Required:** ``biz_order_id``. **Optional:** ``is_settlement_info``, ``settlement_info``. Merchant id and signature come from config/session.

Fetch transaction status for an order (order_id required). Optional txn_type values: PREAUTH, RELEASE, CAPTURE, WITHDRAW. Optional channel_id values (request head): WEB, WAP. If omitted, server default applies.

Retrieves ONE page of payment links (10 per page from Paytm). One tool call = one page only. Triggers and behavior: - "Fetch all links", "list my links", "show my payment links" → call with page_no=1 only. Do NOT automatically fetch page 2, 3, … . The string response includes a line telling the user they can ask for page 2 (e.g. "show me page 2") if this page has 10 links. - "Page 2", "next page", "show more links" → set page_no=2 (or 3, …) as the user requests. - If the user implies a payment status (paid, pending, …), pass the mapped `status`; still one page per call unless they ask for another page. Paytm returns only resultInfo, links, and mid—no total count. A full page (10 links) means more pages may exist; fewer than 10 usually means this was the last page for that filter. Present results as a Markdown table: Link ID | Short URL | Status | Created | Expiry, and include the pagination footer from the tool result for the user. Parameters: status: Optional filter: PAID, PENDING, EXPIRED, INIT (map user phrases accordingly). page_no: 1-based page index. Default 1. Increase only when the user asks for the next page.

Fetch available payment options for the merchant. Uses only an ACCESS token from initiate_transaction (tokenType=ACCESS in the request head) and the token ``referenceId`` in the body and query — no merchant ``orderId`` / ``initiate_transaction`` context is required. Returns payment modes (UPI, cards, wallet, net banking, etc.), saved instruments, and merchant details.

Check the status of a previously initiated refund. Parameters: order_id: Original order ID of the transaction. refund_reference_id: Merchant refund reference (refId) from initiation or from fetch_refunds. PENDING from Paytm is a valid in-progress status, not an error. If the user does not know refund_reference_id, use fetch_refunds (by date) to list refId values per order.

Refunds completed between two dates (Paytm Refund List API). Date format: yyyy-MM-ddTHH:mm:ss+05:30. This is a paginated API: - page_num specifies which page of results to retrieve (starting from 1). - page_size specifies the number of refunds per page (maximum 50). - Each tool call returns only the requested page. - To retrieve additional results, call the tool again with a higher page_num. Date filtering: - start_date and end_date are required. - The underlying API requires the date range between start_date and end_date to be no more than 31 days. - Requests exceeding the 31-day limit are not supported and should be split into multiple queries. Returns refund details including order ID, refund ID, reference ID, refund amount, refund status, and refund timestamps.

settlement bill list by date range. Equivalent to legacy SettlementDetail. Returns settlement bill list for the given settled date range. Required: start_date, end_date (YYYY-MM-DD). Optional: page_num (default: 1), page_size (default: 20, maximum: 50). Merchant and signature from config/session. **For the assistant:** Response amounts are typically in **paisa**. For user-facing output, **convert to rupees** (paisa ÷ 100, display with ₹). Leave non-currency fields (IDs, statuses, counts) as returned unless the user asks otherwise.

Settlement Transaction List (by Date Range) Fetch settlement transactions within a given date range (equivalent to legacy SettlementSummary). Inputs: - start_date (YYYY-MM-DD) — required - end_date (YYYY-MM-DD) — required - page_num — optional (default: 1) - page_size — optional (default: 20 , maximum:50) - settlement_order_id — optional (filter by settlement/payout order ID) - Merchant credentials & signature are taken from config/session IMPORTANT (Amount Handling): The API returns amounts in raw paisa. You must convert these to Rupees (₹) before finalizing your output. For EVERY transaction, follow this exact thought process internally before outputting the final list: - Extract the value specifically from the "transactionAmount.value" key for each transaction. - The API returns this value as a string representing paisa (e.g., "100" or "1000"). - You MUST convert this specific paisa value to rupees (₹) by dividing by 100. - Example: If transactionAmount.value is "100", the output must be ₹1.00. - Example: If transactionAmount.value is "1000", the output must be ₹10.00. - NEVER return the raw string value from the JSON. Always do the math. Output Format Requirement: - Do NOT output the raw paisa value in the final response. Only output the calculated Rupee value. - Show all monetary values only in rupees (₹) - Keep IDs, statuses, timestamps, and counts unchanged

Fetch subscription status using Paytm Subscription ID. Inputs: - subs_id (required) Returns subscription details including status, frequency, amount, customer information, expiry date, and latest order details. If subs_id is invalid or not found, the API returns HTTP 400. Only valid Paytm subscription IDs are accepted