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

OpenAPI 3.0 REST API for online / e-commerce card payments. Issues access-tokens, processes and resumes payments, runs cross-reference (repeat) payments, and lists supported payment methods against the Connect-E host (e..connect.paymentsense.cloud).

Documentation Provider Profile APIs.io OpenAPI GitHub

Paymentsense Connect-E 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, Online Payments, Card Payments, and E-Commerce. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 6 operations across 6 paths, organized into 6 resource areas, and defines 9 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

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

6 operations 6 paths 9 schemas 2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://e.test.connect.paymentsense.cloud
Authentication
API Key, API Key, HTTP Bearer
Resource Areas
6

Authentication & Security 3

Paymentsense Connect-E REST 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 6

Across 6 paths, the API surfaces 6 operations — 2 GET, 4 POST. They span 6 resource areas: Access Token, Payment Details, Resume Payment, Cross Reference Payment, Revoke Access Token, Payment Methods. Each is listed below with its method, path, parameters, and response codes.

Access Token 1
POST
/v1/access-tokens
Create a one time use access token to make a payment.
/v1/access-tokens body → 200400401500
Payment Details 1
GET
/v1/payments/{access-token}
Get details of the payment with this access token
/v1/payments/ 1 param → 200400401404500
Resume Payment 1
POST
/v1/payments/{access-token}/resume
Resume a paused wait pre-execute transaction using the id.
/v1/payments/resume 1 param → 200400401500
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
Revoke Access Token 1
POST
/v1/access-tokens/{access-token}/revoke
Revoke an access token
1 param → 200400401500
Payment Methods 1
GET
/v1/payment-methods
Get supported payment methods for authenticated merchant.
→ 200500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are accessTokenRequest (27 properties), paymentInfo (13 properties), address (8 properties), crossReferenceResponse (3 properties). Each schema is shown below with its type and property counts.

paymentMethods
object
2 properties
resumePaymentResponse
object
3 properties
crossReferenceResponse
object
3 properties
paymentCrossReferenceRequest
object
2 properties 1 required
paymentInfo
object
13 properties
shippingDetails
object
2 properties
address
object
8 properties
accessTokenRequest
object
27 properties 5 required
accessToken
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paymentsense-connect-e-v0.json Raw ↑

Other APIs Paymentsense publishes across the network.

Paymentsense Connect REST API
AE Profile APIs.io
Paymentsense Connect WebSockets API
AE Profile APIs.io
#Payments#Online Payments#Card Payments#E-Commerce
← Back to P APIs
API Details
ID
paymentsense:connect-e-rest-api
Base URL
https://e.test.connect.paymentsense.cloud
Docs
https://docs.connect.paymentsense.cloud/ConnectE/RestApi
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=connect-e-rest-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/connect-e-rest-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 Connect-E 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.