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
Verifone

Verifone Transaction API

The Transaction API from Verifone — 3 operation(s) for transaction.

Documentation Provider Profile APIs.io OpenAPI GitHub

Verifone Transaction API is one of 27 APIs that Verifone publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 3 paths, and defines 25 schemas. It is described by OpenAPI 3.0.1, at version 3.43.0.

Requests are made against 5 base URLs: https://emea.gsc.verifone.cloud/oidc/3ds-service, https://us.gsc.verifone.cloud/oidc/3ds-service, https://nz.gsc.verifone.cloud/oidc/3ds-service, https://cst.test-gsc.vfims.com/oidc/3ds-service, https://uscst-gb.gsc.vficloud.net/oidc/3ds-service.

3 operations 3 paths 25 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
3.43.0
Base URL
https://us.gsc.verifone.cloud/oidc/checkout-service
Authentication
HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 2

Verifone Transaction API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

  • BearerAuth — JWT Bearer token. Pass as: Authorization: Bearer . The JWT must be signed with your Verifone-provisioned private key and must include entityid, sub (userid), a…
  • BasicAuth — HTTP Basic authentication. Pass base64-encoded username:password as: Authorization: Basic .

Paths & Operations 3

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

Transaction 3
GET
/api/v2/transaction/{id}
Read transaction
readTransaction 1 param → 200400401403404500
GET
/api/v2/transactions
List transactions
listTransactions 25 params → 200400401403404500
GET
/api/v2/transactions/count
Count transactions
countTransactions 19 params → 200400401403404500

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are GatewayTransactions (47 properties), GatewayTransaction (47 properties), CustomerDetailsDto (10 properties), ShippingInformation (9 properties). Each schema is shown below with its type and property counts.

amountString
string
Amount including decimal place.
ThreeDSecure
object
8 properties
ShippingInformation
object
9 properties 4 required
TransactionState
string
This represents the available states that a transaction may have. At any given point it may only have a single state.
BillingDto
object
8 properties
ListDetailedAmount
object
A structure that represents a breakdown all of the different amounts that may appear on a single transaction.
5 properties
UnauthorizedV2Docs
object
5 properties 1 required
TransactionType
string
A type indicator for the main operation or service that was performed as part of the transaction event.
TokenDetailsPartial
object
3 properties
ForbiddenV2Docs
object
5 properties 1 required
amountDecimal
number
Amount including decimal place.
CustomerDetailsDto
object
Customer information containing billing and shipping details.
10 properties
acquirerResponseMessage
string
The response description generated by the acquirer corresponding to the acquirer response code.
acquirerAuthorizingNetworkID
string
The Network ID returned in the original authorization response.
PaymentProductType
string
The payment product type corresponding to this transaction. Fees applied to the transaction, is based on the payment product
acquirerAuthorizingNetworkIdDescriptor
string
The name or descriptor that corresponds with the acquirerauthorizingnetworkid returned in the original authorization response.
GatewayTransaction
object
47 properties
CustomerDetailsShippingInformationDto
object
The address where the purchased goods should be delivered to.
9 properties 4 required
CountTransactionResponse
object
1 property
NotFoundV2Docs
object
5 properties 1 required
InternalErrorV2Docs
object
5 properties 1 required
BadRequestV2Docs
object
5 properties 1 required
GatewayTransactions
object
47 properties
acquirerResponseCode
string
Acquirer response returned during the authorisation.
CardBrand
string
Represents a Card type or brand. It should correspond to a consistent name, the list of standard names is as follows: Value | Description ------|-------------…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

verifone-transaction-api-openapi.yml Raw ↑

Other APIs Verifone publishes across the network.

Verifone eCommerce API
AE Profile APIs.io
Verifone 3D Secure API
AE Profile APIs.io
Verifone Reporting API
AE Profile APIs.io
Verifone PayPal eCommerce API
AE Profile APIs.io
Verifone VHQ Device Management API
AE Profile APIs.io
Verifone 3DS Authentication API
AE Profile APIs.io
Verifone Batch API
AE Profile APIs.io
Verifone Billing Agreement API
AE Profile APIs.io
Verifone Billing Plans API
AE Profile APIs.io
Verifone Checkout API
AE Profile APIs.io
Verifone Customer API
AE Profile APIs.io
Verifone Ecom Payments API
AE Profile APIs.io
#Transaction
← Back to V APIs
API Details
ID
verifone:verifone-transaction-api
Base URL
https://us.gsc.verifone.cloud/oidc/checkout-service
Docs
https://docs.verifone.com/api-reference/open-api-references/checkout
Provider
Verifone
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=verifone-transaction-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/verifone-transaction-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 Verifone Transaction 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.