ll-transactions

Query and filter ICPAY transaction histories with pagination and caller-based access checks.

9|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/Katsumitec/Human_First --skill ll-transactions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ll-transactions
Source: https://github.com/Katsumitec/Human_First/tree/main/projects/ll-ai-first/skills-scripts/ll-bot-skills/ll-transactions
Command: npx skills add https://github.com/Katsumitec/Human_First --skill ll-transactions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ICPAY_TG_BASE_URL, ICPAY_TG_TOKEN_MER, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of accessing transaction histories, providing a streamlined way to retrieve and filter records based on specific dates and criteria.

Core Features & Use Cases

  • Transaction History Access: Retrieve detailed transaction records for a given month.
  • Filtering: Ability to filter by state, order ID, transaction code, and transaction channel.
  • Pagination: Support for paginated results, with a maximum of 10 records per page.
  • Use Case: For finance departments or customer support teams needing to quickly access transaction details, this Skill can provide the necessary information without manual searching.

Quick Start

Use the ll-transactions skill to fetch the transaction list for June 2026 with a state of 'SUCCESSFUL' and a transaction code of '0210'.

Frequently Asked Questions about ll-transactions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query transaction history by date and filter criteria?

Transaction history querying supports filtering by month, state, order ID, transaction code, and channel, returning a maximum of 10 paginated records per page for financial reporting.

Can I filter transaction records by transaction code and state?

Yes, transaction records can be filtered by state, order ID, transaction code, and transaction channel, allowing precise retrieval of specific transactions from the ICPAY backend system.

Do I need environment variables to retrieve transaction histories?

Yes, retrieving transaction histories requires setting the ICPAY_TG_BASE_URL and ICPAY_TG_TOKEN_MER environment variables for service URLs and authentication token validation.

What is the maximum number of records returned per page when filtering transaction histories?

Pagination support provides a maximum of 10 records per page when filtering transaction histories, allowing you to retrieve larger datasets across multiple sequential pages.

How does caller aggregation work for unauthorized access checks in transaction queries?

Caller aggregation groups queries by callerChatId, applying strict checks against multiple bindings and unauthorized access to ensure secure transaction history retrieval from the backend.