LLPROBeta

Home / Businesses / Refund Window and Dispute Limit Check

Refund Window and Dispute Limit Check

Check a refund request against your refund window and the card dispute time limit you send, in calendar days: last day of each, inside or outside, days left or past, with a signed record.

Testing

What it does
Check a refund request against your refund window and the card dispute time limit you send, in calendar days: last day of each, inside or outside, days left or past, with a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call refund_window_check at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

Refund Window and Dispute Limit Check is for agents that handle refund requests and chargebacks for a business and need the refund window and dispute deadline counted the same way every time. Check whether a refund request falls inside your refund window and inside the card-network dispute (chargeback) time limit you send, counted in calendar days. Send the purchase date, the request date, refund_window_days (your policy, for example 30) and, if you want the dispute side, dispute_limit_days (the limit for the reason code, for example 120). The refund window can run from the purchase or from the delivery date; the dispute limit runs from the purchase date unless you send dispute_start_date (for example the expected delivery date for goods not received). Get back the last day of each, inside or outside, and the days left or days past. It is one of the Payments department tools LLPRO builds for the work agents do across business software (Stripe, PayPal, Square, Shopify, QuickBooks). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that handle refund requests and chargebacks for a business and need the refund window and dispute deadline counted the same way every time.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not know any card network's limits, reason codes or how a network counts a specific case: send the limit and start date that apply (from your network rules or acquirer). Does not move a last day off a weekend or holiday. Does not decide whether a refund is owed under consumer law, a state refund-policy statute or the card-network rules; it only counts the days. Not legal or financial advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "refund_window_check", "arguments": {"purchase_date": "2026-01-15", "request_date": "2026-02-14", "refund_window_days": 30, "dispute_limit_days": 120}}}

For agents

Tool refund_window_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:5ei4p3dhiwzttakxthox3xtr3m): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): YUHlyjwNgNHAw7FbJEiwVAzQuhU2q+Zs2xDi0jILR2E=

For agents that search MCP registries for refund window, chargeback time limit, dispute deadline tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card