AI tools — Payments

6 tools. The latest schema is always in payment_tool_catalog once connected.

Payment request details

ReadScope: payment:read

payment_intents_get

Details of one payment request: amount, payment channel, status and reference document.

Parameter	Type	Required	Description
`id`	string	yes	Payment request id

Or call over REST with an API key

curl -X POST https://api.nextx.vn/api/v1/ai/tools/payment/payment_intents_get/read \
  -H "X-Api-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"id":"0199a1b2-c3d4-7e5f-8a9b-0c1d2e3f4a5b"}'

MCP call example (for AI assistants)

AI assistants send this call themselves when you ask in plain words; you only need it when debugging an MCP connection.

{
  "name": "payment_intents_get",
  "arguments": {
    "args": {
      "id": "0199a1b2-c3d4-7e5f-8a9b-0c1d2e3f4a5b"
    }
  }
}

Refunds

ReadScope: payment:read

payment_refunds_search

List refunds filtered by status, date range and keyword; paginated.

Parameter	Type	Required	Description
`status`	string	no	Refund status
`from`	string	no	From date (yyyy-MM-dd)
`to`	string	no	To date (yyyy-MM-dd)
`search`	string	no	Keyword
`page`	integer	no	Page, starting at 1
`pageSize`	integer	no	Rows per page, max 50

Or call over REST with an API key

curl -X POST https://api.nextx.vn/api/v1/ai/tools/payment/payment_refunds_search/read \
  -H "X-Api-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"from":"2026-10-01","to":"2026-10-27","pageSize":20}'

MCP call example (for AI assistants)

AI assistants send this call themselves when you ask in plain words; you only need it when debugging an MCP connection.

{
  "name": "payment_refunds_search",
  "arguments": {
    "args": {
      "from": "2026-10-01",
      "to": "2026-10-27",
      "pageSize": 20
    }
  }
}

Payment overview

ReadScope: payment:read

payment_reports_overview

Payment overview for a date range: transaction count and amount by channel and by status. Defaults to the last month.

Parameter	Type	Required	Description
`from`	string	no	From date (yyyy-MM-dd)
`to`	string	no	To date (yyyy-MM-dd)

Or call over REST with an API key

curl -X POST https://api.nextx.vn/api/v1/ai/tools/payment/payment_reports_overview/read \
  -H "X-Api-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"from":"2026-10-01","to":"2026-10-27"}'

MCP call example (for AI assistants)

AI assistants send this call themselves when you ask in plain words; you only need it when debugging an MCP connection.

{
  "name": "payment_reports_overview",
  "arguments": {
    "args": {
      "from": "2026-10-01",
      "to": "2026-10-27"
    }
  }
}

Recurring subscriptions

ReadScope: payment:read

payment_subscriptions_search

List recurring payment subscriptions filtered by status, document type and channel; paginated.

Parameter	Type	Required	Description
`status`	string	no	Subscription status
`referenceType`	string	no	Source document type
`providerCode`	string	no	Payment channel code
`page`	integer	no	Page, starting at 1
`pageSize`	integer	no	Rows per page, max 50

Or call over REST with an API key

curl -X POST https://api.nextx.vn/api/v1/ai/tools/payment/payment_subscriptions_search/read \
  -H "X-Api-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"status":"ACTIVE"}'

MCP call example (for AI assistants)

AI assistants send this call themselves when you ask in plain words; you only need it when debugging an MCP connection.

{
  "name": "payment_subscriptions_search",
  "arguments": {
    "args": {
      "status": "ACTIVE"
    }
  }
}

Payment transaction details

ReadScope: payment:read

payment_transactions_get

Details of one payment transaction.

Parameter	Type	Required	Description
`id`	string	yes	Transaction id (from payment_transactions_search)

Or call over REST with an API key

curl -X POST https://api.nextx.vn/api/v1/ai/tools/payment/payment_transactions_get/read \
  -H "X-Api-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"id":"0199a1b2-c3d4-7e5f-8a9b-0c1d2e3f4a5b"}'

MCP call example (for AI assistants)

AI assistants send this call themselves when you ask in plain words; you only need it when debugging an MCP connection.

{
  "name": "payment_transactions_get",
  "arguments": {
    "args": {
      "id": "0199a1b2-c3d4-7e5f-8a9b-0c1d2e3f4a5b"
    }
  }
}

Payment transactions

ReadScope: payment:read

payment_transactions_search

List payment transactions filtered by channel, document type, date range and keyword; paginated.

Parameter	Type	Required	Description
`providerCode`	string	no	Payment channel code (e.g. VIETQR, VNPAY)
`referenceType`	string	no	Source document type (e.g. sales order, contract)
`fromDate`	string	no	From date (yyyy-MM-dd)
`toDate`	string	no	To date (yyyy-MM-dd)
`search`	string	no	Keyword
`page`	integer	no	Page, starting at 1
`pageSize`	integer	no	Rows per page, max 50

Or call over REST with an API key

curl -X POST https://api.nextx.vn/api/v1/ai/tools/payment/payment_transactions_search/read \
  -H "X-Api-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"providerCode":"VIETQR","fromDate":"2026-10-01","toDate":"2026-10-27"}'

MCP call example (for AI assistants)

AI assistants send this call themselves when you ask in plain words; you only need it when debugging an MCP connection.

{
  "name": "payment_transactions_search",
  "arguments": {
    "args": {
      "providerCode": "VIETQR",
      "fromDate": "2026-10-01",
      "toDate": "2026-10-27"
    }
  }
}