juspay_alert_details
ChatGPTGet details for a specific configured alert by its task UID.
juspay_alert_details
ChatGPTGet details for a specific configured alert by its task UID.
juspay_analyze_success_rate
ChatGPTReturns a Markdown playbook for investigating a payment-transaction success-rate drop by comparing an analysis window against a baseline period. Use when the user is debugging an SR dip, conversion decline, gateway-performance shift, or rise in failures. The playbook covers dual-period queries, dimensional drilldowns, error-pattern checks, outage cross-references, and a final report outline; each window must be 7 days or less, in ISO-8601 UTC.
juspay_analyze_success_rate
ChatGPTReturns a Markdown playbook for investigating a payment-transaction success-rate drop by comparing an analysis window against a baseline period. Use when the user is debugging an SR dip, conversion decline, gateway-performance shift, or rise in failures. The playbook covers dual-period queries, dimensional drilldowns, error-pattern checks, outage cross-references, and a final report outline; each window must be 7 days or less, in ISO-8601 UTC.
juspay_field_value_discovery
ChatGPTBatch distinct-value lookup for analytics filter dimensions: fuzzy string matching against merchant data for a domain and time window (shape-compatible with Genius DimensionLookupRequest). Inputs: domain matches analytics query domains; requests lists filter fields (not metrics or the time-bucket column) with optional string queries—one ranked row per query, or empty queries to sample up to the first default_limit distincts as one row. Response: results hold nested lists ranked with the closest matches first. When feeding analytics filters, the first token in each inner list is usually the one to use; later entries help confirm alternatives with the user. Passing the same JSON object through as field_discovery_results on the analytics query request keeps validation tied to that ranked list. Often unnecessary when there are no categorical string filters, only numeric thresholds, or the field is high-cardinality / free-text (e.g. order IDs, raw error text)—prefer exact literals there.
juspay_field_value_discovery
ChatGPTBatch distinct-value lookup for analytics filter dimensions: fuzzy string matching against merchant data for a domain and time window (shape-compatible with Genius DimensionLookupRequest). Inputs: domain matches analytics query domains; requests lists filter fields (not metrics or the time-bucket column) with optional string queries—one ranked row per query, or empty queries to sample up to the first default_limit distincts as one row. Response: results hold nested lists ranked with the closest matches first. When feeding analytics filters, the first token in each inner list is usually the one to use; later entries help confirm alternatives with the user. Passing the same JSON object through as field_discovery_results on the analytics query request keeps validation tied to that ranked list. Often unnecessary when there are no categorical string filters, only numeric thresholds, or the field is high-cardinality / free-text (e.g. order IDs, raw error text)—prefer exact literals there.
juspay_get_analytics_schema
ChatGPTLive metrics, dimension names, and filter field names for one analytics domain (portal-backed). Use these strings verbatim when building queries; availability and spelling are domain-specific. Domains: kvorders, kvtxns, kvrefundtxns, kvoffers, mandateexecutionkv, fulfillmentorders. For request shape (UTC, granularity, filter JSON) see the readonly markdown analytics guide in this connector. Categorical filter values generally match merchant distincts better when a distinct-value lookup is applied for the same window before querying.
juspay_get_analytics_schema
ChatGPTLive metrics, dimension names, and filter field names for one analytics domain (portal-backed). Use these strings verbatim when building queries; availability and spelling are domain-specific. Domains: kvorders, kvtxns, kvrefundtxns, kvoffers, mandateexecutionkv, fulfillmentorders. For request shape (UTC, granularity, filter JSON) see the readonly markdown analytics guide in this connector. Categorical filter values generally match merchant distincts better when a distinct-value lookup is applied for the same window before querying.
juspay_get_conflict_settings
ChatGPTGet conflict settings for payment processing
juspay_get_conflict_settings
ChatGPTGet conflict settings for payment processing
juspay_get_gateway_details
ChatGPTGet detailed info for a configured gateway by MGA ID
juspay_get_gateway_details
ChatGPTGet detailed info for a configured gateway by MGA ID
juspay_get_gateway_scheme
ChatGPTGet configuration schema for a specific gateway
juspay_get_gateway_scheme
ChatGPTGet configuration schema for a specific gateway
juspay_get_general_settings
ChatGPTGet general merchant settings
juspay_get_general_settings
ChatGPTGet general merchant settings
juspay_get_mandate_settings
ChatGPTGet mandate/recurring payment settings
juspay_get_mandate_settings
ChatGPTGet mandate/recurring payment settings
juspay_get_merchant_gateways_payment_methods_details
ChatGPTGet all gateways and payment methods configured for merchant
juspay_get_merchant_gateways_payment_methods_details
ChatGPTGet all gateways and payment methods configured for merchant
juspay_get_offer_details
ChatGPTGet details for specific offers
juspay_get_offer_details
ChatGPTGet details for specific offers
juspay_get_order_details
ChatGPTFetch a single order's full details from the dashboard API using the exact Juspay order ID only. Use when the user already has a concrete order_id (e.g. ord_*). Do not pass phone numbers or email—those are not supported here. If the user only has phone or email, ask them to share the exact order ID from receipts, the merchant dashboard, or support.
juspay_get_order_details
ChatGPTFetch a single order's full details from the dashboard API using the exact Juspay order ID only. Use when the user already has a concrete order_id (e.g. ord_*). Do not pass phone numbers or email—those are not supported here. If the user only has phone or email, ask them to share the exact order ID from receipts, the merchant dashboard, or support.
juspay_get_priority_logic_settings
ChatGPTGet priority logic rules configuration
juspay_get_priority_logic_settings
ChatGPTGet priority logic rules configuration
juspay_get_routing_settings
ChatGPTGet success rate-based routing thresholds and settings
juspay_get_routing_settings
ChatGPTGet success rate-based routing thresholds and settings
juspay_get_webhook_settings
ChatGPTGet webhook configuration
juspay_get_webhook_settings
ChatGPTGet webhook configuration
juspay_list_alerts
ChatGPTList all alerts configured by merchant
juspay_list_alerts
ChatGPTList all alerts configured by merchant
juspay_list_configured_gateway
ChatGPTList all payment gateways configured for the merchant
juspay_list_configured_gateway
ChatGPTList all payment gateways configured for the merchant
juspay_list_gateway_scheme
ChatGPTList all available payment gateways that can be configured
juspay_list_gateway_scheme
ChatGPTList all available payment gateways that can be configured
juspay_list_offers
ChatGPTList all offers configured by merchant
juspay_list_offers
ChatGPTList all offers configured by merchant
juspay_list_outages
ChatGPTList recent payment-gateway and bank outages within a time range. The window between startTime and endTime must be 7 days or less.
juspay_list_outages
ChatGPTList recent payment-gateway and bank outages within a time range. The window between startTime and endTime must be 7 days or less.
juspay_list_payment_links_v1
ChatGPTList payment links in a time range
juspay_list_payment_links_v1
ChatGPTList payment links in a time range
juspay_list_report
ChatGPTList all reports configured by merchant
juspay_list_report
ChatGPTList all reports configured by merchant
juspay_list_surcharge_rules
ChatGPTList all configured surcharge rules
juspay_list_surcharge_rules
ChatGPTList all configured surcharge rules
juspay_prefetch_analytics_query_guide
ChatGPTReturns bundled markdown: UTC interval rules, granularity objects, filter JSON shape, and how ranked distinct-value rows map to filter tokens. Pairing this with live schema and distinct-value lookup improves field names and categorical token accuracy.
juspay_prefetch_analytics_query_guide
ChatGPTReturns bundled markdown: UTC interval rules, granularity objects, filter JSON shape, and how ranked distinct-value rows map to filter tokens. Pairing this with live schema and distinct-value lookup improves field names and categorical token accuracy.
juspay_query_analytics
ChatGPTMerchant analytics aggregates: metrics, dimensions, optional filters; chart-friendly responses. Fits well: Trends, counts, success rate or volume, comparisons across gateways, methods, or time periods. Domains: kvorders, kvtxns, kvrefundtxns, kvoffers, mandateexecutionkv, fulfillmentorders. Filters on categorical fields (e.g. payment_gateway, bank, payment_method_type): labels people use often differ from stored tokens. Including field_discovery_results alongside filters helps the service line up val entries with merchant-specific distinct values and return validation context when something still does not match the sampled set. The first entry in each ranked inner list from that lookup is usually the right token to filter on. No categorical string filters (time range and breakdowns only, or purely numeric thresholds): field_discovery_results can stay unset. Payload shape and UTC rules: the readonly markdown analytics guide in this connector goes into intervals and JSON shape in more detail.
juspay_query_analytics
ChatGPTMerchant analytics aggregates: metrics, dimensions, optional filters; chart-friendly responses. Fits well: Trends, counts, success rate or volume, comparisons across gateways, methods, or time periods. Domains: kvorders, kvtxns, kvrefundtxns, kvoffers, mandateexecutionkv, fulfillmentorders. Filters on categorical fields (e.g. payment_gateway, bank, payment_method_type): labels people use often differ from stored tokens. Including field_discovery_results alongside filters helps the service line up val entries with merchant-specific distinct values and return validation context when something still does not match the sampled set. The first entry in each ranked inner list from that lookup is usually the right token to filter on. No categorical string filters (time range and breakdowns only, or purely numeric thresholds): field_discovery_results can stay unset. Payload shape and UTC rules: the readonly markdown analytics guide in this connector goes into intervals and JSON shape in more detail.
juspay_report_details
ChatGPTGet details for a specific scheduled report by its task UID.
juspay_report_details
ChatGPTGet details for a specific scheduled report by its task UID.
juspay_search_docs
ChatGPTSearch Juspay integration documentation using AI-powered semantic search (RAG). Well suited when the user asks about: - How to integrate Juspay payment products (hyper-checkout, payment-links, ec-api, ec-headless, payment-form, payout) - API endpoints, request/response formats, or field descriptions - SDK usage, webhooks, or event handling - Step-by-step integration guides or troubleshooting - Any "how does X work" or "what is the API for Y" questions about Juspay Returns a detailed AI-generated answer with links to the official Juspay documentation.
juspay_search_docs
ChatGPTSearch Juspay integration documentation using AI-powered semantic search (RAG). Well suited when the user asks about: - How to integrate Juspay payment products (hyper-checkout, payment-links, ec-api, ec-headless, payment-form, payout) - API endpoints, request/response formats, or field descriptions - SDK usage, webhooks, or event handling - Step-by-step integration guides or troubleshooting - Any "how does X work" or "what is the API for Y" questions about Juspay Returns a detailed AI-generated answer with links to the official Juspay documentation.