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 Cross Reference Payment API

The Cross Reference Payment API from Paymentsense — 1 operation(s) for cross reference payment.

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

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

This API exposes 1 operation across 1 path, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

1 operations 1 paths 2 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://your-host-here.connect.paymentsense.cloud
Authentication
API Key, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Paymentsense Cross Reference Payment API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (api_key). An API key is passed in the header as Authorization (access_token). It accepts HTTP bearer tokens (JWT) (jwt).

  • access_token — This authorization is deprecated and only used on the POST /v1/cross-reference-payments endpoint. Please only use the apikey for new integrations.

Paths & Operations 1

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

Cross Reference Payment 1
POST
/v1/cross-reference-payments/{access-token}
Execute a transaction using the cross reference from a previous transaction. To execute this request, pass the id from creating an access token as {access-token} in the path. This token can only be u…
/v1/cross-reference-payments/access-token 1 param body → 200400401500

Schemas 2

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

paymentCrossReferenceRequest
object
2 properties 1 required
crossReferenceResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paymentsense-cross-reference-payment-api-openapi.yml Raw ↑

Other APIs Paymentsense publishes across the network.

Paymentsense Connect WebSockets API
Paymentsense Access Token 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
Paymentsense Payment Methods API
Where this information came from

This is an independent, third-party profile of Paymentsense Cross Reference Payment 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.