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 Connect REST API

Cloud REST API for driving Paymentsense card terminals from EPOS software. Covers Pay-At-Counter (/pac) transactions and reports and Pay-At-Table (/pat) hospitality flows against a per-merchant Connect host. Published in versions v0 (Swagger 2.0, 3.0-beta), v1 (Swagger 2.0, 3.1) and v2 (OpenAPI 3.0, 3.2, current). Authenticates with HTTP Basic using the merchant API key as the password.

Paymentsense Connect REST API is one of 3 APIs that Paymentsense publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments, Point-of-Sale, Card Payments, and Pay at Table. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 8 operations across 7 paths, organized into 3 resource areas, and defines 31 schemas. It is described by OpenAPI 3.0.0, at version 3.2.

Requests are made against a single base URL, https://dev-heisenberg.test.connect.paymentsense.cloud.

8 operations 7 paths 31 schemas 1 DELETE4 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
3.2
Base URL
https://your-host-here.connect.paymentsense.cloud
Authentication
HTTP Basic
Resource Areas
3

Authentication & Security 1

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

Paths & Operations 8

Across 7 paths, the API surfaces 8 operations — 1 DELETE, 4 GET, 2 POST, 1 PUT. They span 3 resource areas: PAC Terminals, PAC Transactions, PAC Reports (Ingenico Only). Each is listed below with its method, path, parameters, and response codes.

PAC Terminals 2
GET
/pac/terminals
Gets a list of all card terminals that are currently connected. This can be filtered by currency and status.
PACTerminals 2 params → 200401422500
GET
/pac/terminals/{tid}
Gets details for a specific terminal.
PACTerminalsByTID 1 param → 200401404422500
PAC Transactions 4
POST
/pac/terminals/{tid}/transactions
Starts a transaction on the terminal with the given TID.
TransactionOnTID 1 param body → 201401404422500
GET
/pac/terminals/{tid}/transactions/{requestId}
Gets data for the transaction with the given requestId.
GetTransactionWithRequestId 2 params → 200401404422500
DELETE
/pac/terminals/{tid}/transactions/{requestId}
Attempts to cancel the transaction with the given requestId.
CancelTransactionWithRequestId 2 params → 202401404422500
PUT
/pac/terminals/{tid}/transactions/{requestId}/signature
Attempts to apply signature verification on the transaction with the given requestId. If the signature is declined, the card terminal will attempt to reverse the transaction.
VerifySignature 2 params body → 202401404422500
PAC Reports (Ingenico Only) 2
POST
/pac/terminals/{tid}/reports
Starts a report on the terminal with the given TID.
PACReportRequest 1 param body → 201401422500
GET
/pac/terminals/{tid}/reports/{requestId}
Gets data for the report with the given requestId.
PACReportDetails 2 params → 200401404422500

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are transaction (25 properties), reportBalances (13 properties), reportResponse (10 properties), transactionRequest (7 properties). Each schema is shown below with its type and property counts.

currency
string
Currency of the request. The textual representation from ISO 4217 is used.
format
string
issuerTotals
object
A dictionary of totals split by issuer. {issuerName} is an example key.
1 property
messageList
array
notifications
string
paymentMethod
string
receiptLine
object
3 properties 1 required
receiptLineList
array
reportBalances
object
Local totals for the current terminal session. Only contained in XBALANCE, ZBALANCE and ENDOFDAY.
13 properties 13 required
reportBanking
object
7 properties 7 required
reportRequest
object
1 property
reportResponse
object
10 properties 3 required
reportsBanking
object
Banking totals for the current terminal session (these are reset in line with the banking window). Only contained in BANKING and ENDOFDAY. Consists of a dictio…
1 property
reportType
string
Type of the report.
requestLocationResponse
object
2 properties
signatureRequest
object
1 property 1 required
terminal
object
4 properties 4 required
terminalList
array
terminalWrapper
object
1 property
totalsBreakdown
object
6 properties 6 required
transaction
object
25 properties 2 required
transactionRequest
object
7 properties
saleRequest
object
5 properties
refundRequest
object
4 properties
preAuthRequest
object
4 properties
completionRequest
object
5 properties
duplicateRequest
object
2 properties
accountVerificationRequest
object
2 properties
transactionType
string
Type of the transaction. The DUPLICATE type is only supported on Ingenico terminals.
userMessage
object
1 property
waiterTotals
object
A dictionary of totals split by waiter. {waiterId} is an example key.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paymentsense-connect-v2.json Raw ↑

Other APIs Paymentsense publishes across the network.

Paymentsense Connect-E REST API
Paymentsense Connect WebSockets API
Where this information came from

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