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

Till Payments Transaction API

Process transactions

Till Payments Transaction 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 Transaction. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against 2 base URLs: https://secure.tillpayments.com/api/v3, https://gateway.tillpayments.com/api/v3.

9 operations 9 paths 56 schemas 9 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 Transaction API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 9

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

transaction 9

Process transactions

POST
/transaction/{apiKey}/debit
Process a debit
processDebit 1 param body → 200
POST
/transaction/{apiKey}/preauthorize
Process a preauthorize: reserves the payment amount on the customer's payment instrument
processPreauthorize 1 param body → 200
POST
/transaction/{apiKey}/incrementalAuthorization
Increases or prolongs the authorization on a customer's payment instrument (made with Preauthorize before)
processIncrementalAuthorization 1 param body → 200
POST
/transaction/{apiKey}/capture
Process a capture: completes a payment previously authorized through Preauthorize
processCapture 1 param body → 200
POST
/transaction/{apiKey}/void
Process a void: cancels a previously authorized Preauthorize
processVoid 1 param body → 200
POST
/transaction/{apiKey}/register
Process a register: registers a customer's payment instrument for future use (Debit or Preauthorize)
processRegister 1 param body → 200
POST
/transaction/{apiKey}/deregister
Process a deregister: deletes a previously registered payment instrument
processDeregister 1 param body → 200
POST
/transaction/{apiKey}/refund
Process a refund
processRefund 1 param body → 200
POST
/transaction/{apiKey}/payout
Process a payout
processPayout 1 param body → 200

Schemas 56

The contract defines 56 schemas that model the data the API accepts and returns. The most detailed are ThreeDSecureData_2 (73 properties), ThreeDSecureData (73 properties), Preauthorize (36 properties), Debit (34 properties). Each schema is shown below with its type and property counts.

Payout
object
25 properties 3 required
Register
object
23 properties 1 required
DccData
object
8 properties
WalletData
object
1 property
ExternallyProvisionedNetworkToken
object
5 properties
Customer
object
29 properties
Date
string
CardDetailsUpdateData
object
2 properties
BaseExternallyProvisionedToken
object
7 properties 4 required
Items
array
PspPassthroughData
object
L2L3Data
object
9 properties
Schedule
object
7 properties 4 required
Deregister
object
8 properties 1 required
Country
string
ReturnIbanData
object
9 properties
Splits
array
Preauthorize
object
36 properties 3 required
IbanData
object
1 property
DateTimeZone
string
ReturnPhoneData
object
4 properties
Currency
string
ReturnWalletData
object
4 properties
ReturnData
ExternallyProvisionedApplePayToken
object
2 properties 2 required
PaymentData
TransactionResponse
object
19 properties
Void
object
10 properties 2 required
ExtraData
object
ScheduleStatus
string
DateTime
string
ExternallyProvisionedGooglePayToken
object
Amount
string
Refund
object
15 properties 4 required
CustomerProfileData
object
3 properties
IncrementalAuthorization
object
18 properties 4 required
Debit
object
34 properties 3 required
TaxDetails
array
ScheduleData
object
4 properties
ReturnCardData
object
22 properties
CardData
object
5 properties
Capture
object
15 properties 4 required
ThreeDSecureData
object
73 properties
Payout_2
object
25 properties 3 required
Register_2
object
21 properties 1 required
PayByLink
object
2 properties
Deregister_2
object
9 properties 1 required
Splits_2
array
Preauthorize_2
object
33 properties 3 required
Refund_2
object
16 properties 4 required
CustomerProfileData_2
object
4 properties
IncrementalAuthorization_2
object
18 properties 4 required
Debit_2
object
32 properties 3 required
ReturnCardData_2
object
29 properties
Capture_2
object
14 properties 4 required
ThreeDSecureData_2
object
73 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Till Payments publishes across the network.

Till Payments Pay By Link API
Till Payments Terminal Connect API
Till Payments Continue Dcc API
Till Payments Dispute API
Till Payments Options API
Till Payments Prepare Transaction API
Till Payments Schedule API
Till Payments Status API
Where this information came from

This is an independent, third-party profile of Till Payments Transaction 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.