HSBC Merchant Services: acquirer terms — MerchantHQ Card Acquirer Index MCP Resource
HSBC Merchant Services: acquirer terms
is one of 45 resources on the
MerchantHQ Card Acquirer Index
MCP server. Connect the server and your client can attach it as context.
by client
How to attach HSBC Merchant Services: acquirer terms from your client
- Claude Code MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms run in your project directory
- Claude Desktop MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms ~/.cursor/mcp.json
- VS Code MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms .vscode/mcp.json
- Zed MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms ~/.config/zed/settings.json
- Windsurf MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms ~/.codeium/windsurf/mcp_config.json
- Cline MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms ~/.gemini/settings.json
- Grok MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms .mcp.json (in your project root)
- ChatGPT MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms Settings → Connectors → Advanced → Developer mode
- Claude.ai MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms Settings → Connectors → Add custom connector
- LangChain MerchantHQ Card Acquirer Index Resource/HSBC Merchant Services: acquirer terms pip install langchain-mcp-adapters
Other resources on this server
- UK Card Acquirer Index (metadata)
- UK card-payment fees snapshot
- UK high-risk merchant-account matrix
- Dojo: acquirer terms
- SumUp: acquirer terms
- Square: acquirer terms
- PayPal Zettle: acquirer terms
- Stripe: acquirer terms
- Tide: acquirer terms
- Revolut Business: acquirer terms
- Teya: acquirer terms
- Adyen: acquirer terms
- Worldpay (FIS): acquirer terms
- Tyl by NatWest: acquirer terms
- Barclaycard Payments: acquirer terms
- Elavon: acquirer terms
- Lloyds Cardnet: acquirer terms
- Santander (via Worldpay): acquirer terms
- Global Payments UK: acquirer terms
- Take Payments: acquirer terms
- Handepay: acquirer terms
- Cardstream: acquirer terms
- Trust Payments: acquirer terms
- Castles Technology: acquirer terms
- MyPOS: acquirer terms
- Truevo: acquirer terms
- GoDaddy Payments: acquirer terms
- Shopify Payments: acquirer terms
- PayPal Checkout: acquirer terms
- Klarna: acquirer terms
- Clearpay (Afterpay): acquirer terms
- GoCardless: acquirer terms
- Opayo (formerly Sage Pay): acquirer terms
- Mollie: acquirer terms
- Tipalti: acquirer terms
- HighRisk-Pay: acquirer terms
- SecurionPay: acquirer terms
- eMerchantBroker: acquirer terms
- Easy Pay Direct: acquirer terms
- Soar Payments: acquirer terms
Read from the server itself, by connecting to it and calling resources/list on 21 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.