RetryHub

• match_merchant_account — Use when a merchant asks whether a high-risk merchant account review may fit their business. Inputs are the niche, monthly processing volume, country or entity,
• build_shutdown_checklist — Use when a merchant asks what to do after a Stripe, PayPal, or Shopify Payments shutdown, limitation, account review, or fund hold. Returns a practical checklis
• check_dispute_ratio — Use when a merchant gives a monthly transaction count and dispute count, or pastes a short summary of those figures, and wants the dispute ratio. Computes dispu
• build_application_checklist — Use when a merchant asks what documents to prepare before applying for a high-risk merchant account. Inputs are the business type, the country or entity, and th
• start_application_handoff — Use when a merchant is ready to apply with RetryHub and wants to carry what they already said in this chat into the application. Inputs are non-sensitive answer
• compare_processor_fit — Use when a merchant asks whether to stay with their current processor (such as Stripe, PayPal, Shopify Payments, or Square) or move to a high-risk merchant acco
• check_policy_readiness — Use when a merchant pastes the refund, cancellation, shipping, or terms text from their website and asks whether it is ready for a merchant account review. Inpu
• start_application — Send the merchant's application request to the RetryHub team so they can follow up. This is the only tool that sends data. Before calling it you MUST: (1) ask w

No hidden text found in the tool definitions.

Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.