Till Payments · Authentication Profile

Till Payments Authentication

Authentication

Till Payments secures its APIs with http across 3 declared security schemes, as derived from its OpenAPI definitions.

PaymentsAustraliaPayment GatewayPayment ProcessingAcquiringMerchant ServicesCard PaymentsIn-Person Payments

Methods: http Schemes: 3 OAuth flows: API key in: path

Security Schemes

basicAuth http

scheme: basic

apiKey apiKey

· in: path (apiKey)

requestSignature signature

Source

Authentication Profile

generated: '2026-07-24'
method: searched
source: openapi/till-payments-direct-pci.yml, openapi/till-payments-gateway.yml
docs: https://gateway.tillpayments.com/documentation/apiv3
summary:
  types:
  - http
  http_schemes:
  - basic
  api_key_in:
  - path
  request_signing: optional
notes: >-
  Every Till Payments Gateway and Direct PCI request authenticates with HTTP
  Basic credentials over TLS 1.2+. The API username and password are joined by a
  colon and Base64-encoded into the Authorization: Basic header (docs example:
  anyApiUser:myPassword -> Authorization: Basic YW55QXBpVXNlcjpteVBhc3N3b3Jk). In
  addition, every transaction endpoint carries a per-connector apiKey as a path
  parameter (/api/v3/transaction/{apiKey}/debit). Request signing is optionally
  available and recommended: an HMAC-SHA512 signature (Base64) enabled per
  connector via the "API: Enable Request Signing" setting. No OAuth2/OIDC surface
  is exposed, so there is no scope model.
schemes:
- name: basicAuth
  type: http
  scheme: basic
  sources:
  - openapi/till-payments-direct-pci.yml
  - openapi/till-payments-gateway.yml
- name: apiKey
  type: apiKey
  in: path
  parameter: apiKey
  description: Per-connector API key embedded as a path segment on every transaction endpoint.
  sources:
  - openapi/till-payments-gateway.yml
  - openapi/till-payments-direct-pci.yml
- name: requestSignature
  type: signature
  algorithm: HMAC-SHA512
  encoding: base64
  required: false
  description: >-
    Optional, connector-enabled request signing ("API: Enable Request Signing").
    Recommended for production integrations to verify request integrity.
  source: https://gateway.tillpayments.com/documentation/apiv3

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/till-payments-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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