Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    CheckSlip — Thai Bank Transfer Slip Verification

    1

    Verify Thai payment slips against order details with CheckSlip MCP. Free skill; verification billed separately.

    Free

    1 useSecurity scanned
    CheckSlip — Thai Bank Transfer Slip Verification

    CheckSlip — Thai Bank Transfer Slip Verification

    Example session with this skill installed

    Check the attached Thai bank transfer slip against my order for 1,500 THB. The expected recipient account ends in 1234.

    Confirm whether the amount and recipient match, and check whether this slip was previously marked as used in my store's records.

    Do not mark it as used or fulfill the order.

    • Read your context and instructions
    • Compiled the checkslip

    Illustrative example — not a live verification

    This is a fictional example of how the agent can explain a successful CheckSlip response. No real payment was checked for this demo.

    Payment verification summary

    In this example, CheckSlip returned verified with ok: true. The amount and recipient account's last four digits matched the supplied order expectations.

    CheckExample outcome
    Provider verificationPassed
    Expected amountMatched: 1,500 THB
    Recipient accountMatched: ending in 1234
    Previously marked as usedNo duplicate found in the store's retained records
    Recipient nameNot checked — no expected name supplied
    Transfer dateNot checked — no expected date supplied

    Actions taken

    The slip was checked but was not marked as used, as requested. No order was fulfilled and no money was transferred.

    A successful verification does not check order details that were not supplied. Duplicate detection is limited to the store's retained used-slip records; it is not a bank-wide guarantee.

    Next steps

    Review the result against the intended order before accepting payment. If you later authorize marking the slip as used, another verification call may consume an additional credit.

    This skill is free. A CheckSlip account is required, and verification usage is billed separately by CheckSlip.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Help your AI agent verify Thai bank transfer slips using CheckSlip's remote MCP service, rather than relying on a screenshot's appearance alone.

    This skill is free. A CheckSlip account is required. Slip verification usage is billed separately by CheckSlip.

    What it does

    • Slip verification: Submit an original PNG/JPEG slip image, raw QR payload, or transaction reference to CheckSlip.
    • Order matching: Compare the transfer with an expected amount, recipient name, recipient account's last four digits, and transfer date.
    • Used-slip detection: Check whether a slip was previously marked as used within your store's retained records.
    • Connection and credit status: Request the service's configuration status and remaining credits when available.
    • History lookup: Search previous verification records and retrieve their details without performing another paid verification.

    How it works

    1. Connect your AI client to https://thaibankslip.com/mcp and authenticate through CheckSlip's OAuth flow.
    2. Provide a slip image, QR payload, or transaction reference.
    3. Supply the expected order details so the agent can check whether the transfer matches your order.
    4. The agent calls CheckSlip and explains the returned result, including any failed checks or service errors.
    5. If you authorize it, the agent can request that a successfully verified slip be marked as used.

    Installing the skill and connecting the MCP server are separate steps. Enter your merchant credentials only on CheckSlip's authorization page, not in an AI conversation or shared configuration file.

    Example uses

    • Check a customer's payment slip before deciding whether to ship an order.
    • Compare a transfer with the expected amount and recipient account.
    • Investigate a slip reported as previously used.
    • Find an earlier verification result by order ID or transaction reference.

    What's included

    • SKILL.md with tool-use instructions and safety guidance.
    • Setup instructions with documentation-based Claude Code and Cursor examples.
    • A credential-free Cursor MCP configuration template.
    • A synthetic verification-request example and tool reference.

    Requirements and pricing

    You need your own CheckSlip account, available verification credits, and an AI client supporting remote MCP over Streamable HTTP with OAuth authentication.

    The skill is free to download. Account management and verification billing remain with CheckSlip. Current pricing is available at https://thaibankslip.com.

    Client examples are documentation-based. End-to-end compatibility has not been verified across all clients or versions.

    Important limitations

    • A verified transfer does not automatically prove it paid the intended order. Only supplied expectations are checked.
    • Duplicate detection is store-scoped and depends on slips previously marked as used and retained records. It is not a permanent or bank-wide guarantee.
    • Marking a slip as used requires authorization. Rechecking a slip to mark it as used may consume another credit.
    • Bank and payment-type coverage depends on the verification provider; not every slip or QR code is guaranteed to be supported.
    • A provider error, configuration issue, or insufficient credits is not proof that a payment is invalid.
    • This skill does not transfer money, initiate payments, or fulfill orders.

    Review CheckSlip's terms and privacy policy before submitting payment data.

    Documentation

    https://thaibankslip.com/docs

    Requires a CheckSlip account and available credits; verification usage is billed separately from this free skill.

    Only supplied order expectations are checked. A verified transfer alone does not prove it paid the intended order.

    Duplicate detection is limited to slips previously marked as used within your store's retained records. It is not a permanent or bank-wide guarantee. Rechecking to mark a slip as used may consume another credit.

    Bank and slip coverage depends on the verification provider. Not every slip or QR code is supported. Service errors or insufficient credits do not prove a payment is invalid.

    Requires a compatible remote MCP client with OAuth. Compatibility has not been tested across all clients or versions.

    Does not transfer money, initiate payments, or fulfill orders.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    Thaibankslip

    Permissions

    Network Access
    Read Files

    Allowed Hosts

    thaibankslip.com

    File Scopes

    examples/**
    references/**
    SKILL.md
    SETUP.md

    Network access is used to connect to the CheckSlip remote MCP service and submit user-authorized slip verification requests. File access is limited to the bundled skill documentation/examples and specific slip images supplied or selected by the user. The skill does not require scanning unrelated files. Terminal access may be used for the documented Claude Code setup command or local base64 encoding of a selected image. It is not required when the client provides these capabilities directly or the user supplies a QR payload or transaction reference. Authentication is completed by the user through CheckSlip's OAuth flow. The skill does not need to read environment secrets or write files. Verification may consume CheckSlip credits. Marking a slip as used changes the store's records and requires user authorization. The skill cannot transfer money or fulfill orders.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    The skill calls CheckSlip's remote MCP service to verify the transaction using the slip's QR payload or transaction reference. It does not judge authenticity from the screenshot's appearance alone. You can supply an expected amount, recipient name, recipient account's last four digits, and transfer date to check whether the transfer matches your order.

    The skill is free to download. A CheckSlip account and available verification credits are required to check slips. Verification usage is billed separately by CheckSlip. Connect the remote MCP server through your AI client's OAuth flow. Enter your merchant credentials only on CheckSlip's authorization page, never in an AI conversation or a shared configuration file.

    CheckSlip can detect slips previously marked as used within your store's retained records. A verification alone does not automatically mark a slip as used; that requires the mark_as_used option and your authorization. Duplicate detection is store-scoped and depends on retained records. It is not a permanent or bank-wide guarantee. Rechecking a slip to mark it as used may consume another credit.

    Coverage depends on CheckSlip's verification provider and the transaction information available on the slip. The skill accepts an original PNG/JPEG slip image, a raw QR payload, or a transaction reference. Not every bank, payment type, or QR code is guaranteed to be supported. A payment-request QR code is not proof of a completed transfer. Check the current documentation at https://thaibankslip.com/docs before relying on a particular payment workflow.

    New in APIs & Backend