Visa Acceptance
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VISA_ACCEPTANCE_TOOLS | No | Comma-separated list of tools to enable, or 'all' to enable all tools | all |
| VISA_ACCEPTANCE_API_KEY_ID | Yes | Your Visa Acceptance API key ID | |
| VISA_ACCEPTANCE_SECRET_KEY | Yes | Your Visa Acceptance secret key | |
| VISA_ACCEPTANCE_ENVIRONMENT | No | When SANDBOX, points to apitest.visa-acceptance.com (non-production). When PRODUCTION, points to api.visa-acceptance.com (production) | SANDBOX |
| VISA_ACCEPTANCE_MERCHANT_ID | Yes | Your Visa Acceptance merchant ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_invoiceC | This tool will create an invoice in Visa Acceptance. |
| update_invoiceD | This tool will update an invoice in Visa Acceptance. |
| get_invoiceB | This tool will get a specific invoice from Visa Acceptance. |
| list_invoicesC | This tool will list invoices from Visa Acceptance. |
| send_invoiceC | This tool will send an invoice to the customer from Visa Acceptance. |
| cancel_invoiceB | This tool will cancel an invoice in Visa Acceptance. |
| create_payment_linkC | This tool will create a payment link in Visa Acceptance. |
| update_payment_linkC | This tool will update a payment link in Visa Acceptance. |
| get_payment_linkB | This tool will get a specific payment link from Visa Acceptance. |
| list_payment_linksC | This tool will list payment links from Visa Acceptance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct resource (invoice vs payment_link) with clear actions (create, get, list, update, cancel, send). No overlap in purpose.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_invoice, list_payment_links), making them predictable and easy to understand.
10 tools cover two main resources with essential CRUD and lifecycle operations. The count is well-scoped without being excessive or insufficient.
Invoices have full lifecycle coverage (create, get, list, update, cancel, send). Payment links cover create, get, list, update, but missing delete or refund functionality, a minor gap.