How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Till Payments

Till Payments Dispute API

The Dispute API from Till Payments — 4 operation(s) for dispute.

Documentation Provider Profile APIs.io OpenAPI GitHub

Till Payments Dispute API is one of 9 APIs that Till Payments publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Dispute. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 3.0.0.

Requests are made against a single base URL, https://gateway.tillpayments.com/api/v3.

4 operations 4 paths 11 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.0
Base URL
https://gateway.tillpayments.com/api/v3
Authentication
HTTP Basic
License
MIT
Resource Areas
1

Authentication & Security 1

Till Payments Dispute API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Dispute 4
POST
/dispute/{apiKey}/metadata/{uuid}
Fetch metadata
disputeMetadata 2 params body → 200
POST
/dispute/{apiKey}/accept/{uuid}
Accept
accept 2 params body → 200
POST
/dispute/{apiKey}/upload-evidence/{uuid}
Upload Evidence
uploadDisputeEvidence 2 params body → 200
POST
/dispute/{apiKey}/submit-evidence/{uuid}
Submit Evidence
submitDisputeEvidence 2 params body → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are DisputeMetadataResponse (4 properties), TransactionError (4 properties), DisputeResponse (3 properties), DisputeUploadEvidenceRequest (2 properties). Each schema is shown below with its type and property counts.

TransactionError
object
4 properties
DisputeResponseExtraData
object
Object containing key-value pairs (string-to-string) or nested objects, returned by the Provider.
DisputeResponseMetadata
object
Object containing key-value pairs (string-to-string) or nested objects, returned by the Provider.
ExtraData
object
TransactionErrors
array
DisputeMetadataRequest
object
1 property
DisputeMetadataResponse
object
4 properties
DisputeAcceptRequest
object
1 property
DisputeUploadEvidenceRequest
object
2 properties 1 required
DisputeResponse
object
3 properties
DisputeSubmitEvidenceRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

till-payments-dispute-api-openapi.yml Raw ↑

Other APIs Till Payments publishes across the network.

Till Payments Pay By Link API
AE Profile APIs.io
Till Payments Terminal Connect API
AE Profile APIs.io
Till Payments Continue Dcc API
AE Profile APIs.io
Till Payments Options API
AE Profile APIs.io
Till Payments Prepare Transaction API
AE Profile APIs.io
Till Payments Schedule API
AE Profile APIs.io
Till Payments Status API
AE Profile APIs.io
Till Payments Transaction API
AE Profile APIs.io
#Dispute
← Back to T APIs
API Details
ID
till-payments:till-payments-dispute-api
Base URL
https://gateway.tillpayments.com/api/v3
Docs
https://gateway.tillpayments.com/documentation/apiv3
Provider
Till Payments
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=till-payments-dispute-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/till-payments-dispute-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Till Payments Dispute API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.