LLPROBeta

Home / Businesses / Card Surcharge Cap Check

Card Surcharge Cap Check

Check a credit card surcharge against the cap you send and your cost of acceptance, with debit and prepaid cards at 0: highest allowed, each breach, the excess in money, signed.

Testing

What it does
Check a credit card surcharge against the cap you send and your cost of acceptance, with debit and prepaid cards at 0: highest allowed, each breach, the excess in money, signed.
Who it is for
Businesses.
Start in one step
Ask your agent to call surcharge_cap_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

Card Surcharge Cap Check is for agents that set up card checkout or pass card fees on for a business and must keep a surcharge inside the network cap and the real cost of acceptance. Check a credit card surcharge before you charge it. Send the surcharge percent, the cap that applies to you (from your card network's rules, your acquirer or state law; send 0 where surcharges are banned) and your cost of acceptance in percent (your effective card fee rate for that card brand). Optionally the card kind and a sale amount. Get back the highest surcharge allowed (the lower of the cap and the cost of acceptance, 0 on debit or prepaid cards), every breach by name, how far over, and in money for the sale amount: the surcharge, the most allowed and the excess. It is one of the Payments department tools LLPRO builds for the work agents do across business software (Stripe, Square, PayPal, 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 set up card checkout or pass card fees on for a business and must keep a surcharge inside the network cap and the real cost of acceptance.
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. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not know your network's, acquirer's or state's cap or whether your state bans surcharges: send the cap that applies (0 where banned). Does not work out your cost of acceptance from statements; send it. Does not check the other surcharge rules (advance notice to the network and acquirer, signs at the entrance and point of sale, the surcharge shown on the receipt, surcharging by brand or by product, no surcharge on top of a convenience fee). Not legal or financial advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "surcharge_cap_check", "arguments": {"surcharge_percent": 3, "cap_percent": 3, "cost_of_acceptance_percent": "2.5", "sale_amount": 200}}}

For agents

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

Public key (base64): av8Ck/aQYuYRQltK2XQVNge56vgzBSy6cghuSoN5H2w=

For agents that search MCP registries for credit card surcharge, surcharge cap, cost of acceptance 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