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

Verifone Transaction API

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

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.2.0, at version 2.38.1.

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

3 operations 3 paths 25 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Verifone Transaction API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

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.

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

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
Verifone 3D Secure API
Verifone Reporting API
Verifone PayPal eCommerce API
Verifone VHQ Device Management API
Verifone 3DS Authentication API
Verifone Batch API
Verifone Billing Agreement API
Verifone Billing Plans API
Verifone Checkout API
Verifone Customer API
Verifone Ecom Payments API
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.