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
Paymentsense

Paymentsense PAC Transactions API

The PAC Transactions API from Paymentsense — 6 operation(s) for pac transactions.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 8 operations across 6 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://your-host-here.test.connect.paymentsense.cloud/, https://dev-heisenberg.test.connect.paymentsense.cloud.

8 operations 6 paths 18 schemas 2 DELETE2 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Paymentsense PAC Transactions 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 6 paths, the API surfaces 8 operations — 2 DELETE, 2 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

PAC Transactions 8
POST
/pac/terminals/{tpi}/transactions
Starts a transaction on the terminal with the given TPI.
TransactionOnTPI 1 param body → 201401401 404 422 422500
GET
/pac/terminals/{tpi}/transactions/{requestId}
Gets data for the transaction with the given requestId.
GetTransactionWithRequestId 2 params → 200401401 404404 500
DELETE
/pac/terminals/{tpi}/transactions/{requestId}
Attempts to cancel the transaction with the given requestId.
CancelTransactionWithRequestId 2 params → 204401401 404 422 500
PUT
/pac/terminals/{tpi}/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 → 202401401 404 404 422 422 500
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

Schemas 18

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

receiptLine
object
3 properties 1 required
currency
string
Currency of the request. The textual representation from ISO 4217 is used.
verifySignature
object
1 property
notifications
string
transactionType
string
Type of the transaction.
transactionRequest
object
3 properties
verifySignatureResponse
object
1 property
receiptLineList
array
signatureRequest
object
1 property 1 required
transaction
object
24 properties 2 required
requestLocationResponse
object
2 properties
format
string
requestLocationResponse_2
object
2 properties
notifications_2
string
transaction_2
object
25 properties 2 required
transactionType_2
string
Type of the transaction. The DUPLICATE type is only supported on Ingenico terminals.
transactionRequest_2
object
7 properties
userMessage
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Paymentsense publishes across the network.

Paymentsense Connect WebSockets API
AE Profile APIs.io
Paymentsense Access Token API
AE Profile APIs.io
Paymentsense Cross Reference Payment API
AE Profile APIs.io
Paymentsense Hospitality Reports API
AE Profile APIs.io
Paymentsense Hospitality Tables API
AE Profile APIs.io
Paymentsense PAC Reports API
AE Profile APIs.io
Paymentsense PAC Reports (Ingenico Only) API
AE Profile APIs.io
Paymentsense PAC Terminals API
AE Profile APIs.io
Paymentsense PAT Reports API
AE Profile APIs.io
Paymentsense PAT Tables API
AE Profile APIs.io
Paymentsense Payment Details API
AE Profile APIs.io
Paymentsense Payment Methods API
AE Profile APIs.io
#PAC Transactions
← Back to P APIs
API Details
ID
paymentsense:paymentsense-pac-transactions-api
Base URL
https://your-host-here.connect.paymentsense.cloud
Docs
https://docs.connect.paymentsense.cloud/rest/api
Provider
Paymentsense
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=paymentsense-pac-transactions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/paymentsense-pac-transactions-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 Paymentsense PAC 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.