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

Paymentsense Retail Transactions API

The Retail Transactions API from Paymentsense — 3 operation(s) for retail transactions.

Paymentsense Retail Transactions API is one of 18 APIs that Paymentsense publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 3 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 3.0-beta.

Requests are made against a single base URL, https://your-host-here.test.connect.paymentsense.cloud/.

4 operations 3 paths 18 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0-beta
Base URL
https://your-host-here.connect.paymentsense.cloud
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Paymentsense Retail Transactions API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (connectBasicAuth). By default, every request must be authenticated.

Paths & Operations 4

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

Retail Transactions 4
POST
/retail/terminals/{tpi}/transactions
Starts a transaction on the given TPI
TransactionOnTPI 1 param body → 201401401 404 422 422500
GET
/retail/terminals/{tpi}/transactions/{requestId}
Gets the transaction data for the given request
TransactionsByRequestId 2 params → 200401401 404404 500
DELETE
/retail/terminals/{tpi}/transactions/{requestId}
Attempts to cancel the transaction for the given request.
TransactionsByRequestId 2 params → 204401401 404 422 500
PUT
/retail/terminals/{tpi}/transactions/{requestId}/signature
Verifies the signature for a given request.
VerifySignature 2 params body → 202401401 404 404 422 422 500

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are transaction (24 properties), transactionRequest (3 properties), receiptLine (3 properties), requestLocationResponse (2 properties). Each schema is shown below with its type and property counts.

receiptLine
object
3 properties 1 required
currency
string
format
string
verifySignature
object
1 property
notifications
string
messageList
array
transactionType
string
transactionTypeResult
string
transactionRequest
object
3 properties
cardholderVerificationMethod
string
receiptLineList
array
verifySignatureResponse
object
1 property
receiptLineTypeRetail
string
signatureRequest
object
1 property 1 required
requestLocationResponse
object
2 properties
transaction
object
24 properties
paymentMethod
string
transactionResult
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paymentsense-retail-transactions-api-openapi.yml Raw ↑

Other APIs Paymentsense publishes across the network.

Paymentsense Connect WebSockets API
Paymentsense Access Token API
Paymentsense Cross Reference Payment API
Paymentsense Hospitality Reports API
Paymentsense Hospitality Tables API
Paymentsense PAC Reports API
Paymentsense PAC Reports (Ingenico Only) API
Paymentsense PAC Terminals API
Paymentsense PAC Transactions API
Paymentsense PAT Reports API
Paymentsense PAT Tables API
Paymentsense Payment Details API
Where this information came from

This is an independent, third-party profile of Paymentsense Retail Transactions 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.