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 Token Management API

The Token Management API from Verifone — 4 operation(s) for token management.

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

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

This API exposes 6 operations across 4 paths, and defines 15 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.

6 operations 4 paths 15 schemas 1 DELETE1 GET3 PATCH1 PUT

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 Token Management 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 6

Across 4 paths, the API surfaces 6 operations — 1 DELETE, 1 GET, 3 PATCH, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Token Management 6
PUT
/api/v2/card
Create/Update Token Details
createUpdateToken body → 200400401403404500
GET
/api/v2/card/{id}
Get Token Details
getToken 1 param → 200400401403404500
DELETE
/api/v2/card/{id}
Delete Token
deleteToken 1 param → 204400401403404500
PATCH
/api/v2/card/{id}
Update Token Details
updateToken 1 param body → 200400401403404500
PATCH
/api/v2/card/{id}/suspend
Suspend Token
suspendToken 1 param → 204400401403404500
PATCH
/api/v2/card/{id}/activate
Activate Token
activateToken 1 param → 204400401403404500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are TokenResponse (21 properties), CardResponse (17 properties), PatchTokenResponse (14 properties), PatchDto (9 properties). Each schema is shown below with its type and property counts.

SchemeToken
object
This object is returned only if schemetokens were created already or schemetokenaction indicated creation (ACTIVATE) of new or suspension (SUSPEND) or deletion…
5 properties
NotFoundV2Docs
object
5 properties 1 required
ForbiddenV2Docs
object
5 properties 1 required
CardResponse
object
17 properties
InternalErrorV2Docs
object
5 properties 1 required
BadRequestV2Docs
object
5 properties 1 required
TokenResponse
object
21 properties
PatchDto
object
9 properties
BinDetails
object
7 properties
PatchTokenResponse
object
14 properties
issuerCountryEnum
string
The [ISO 3166-1 alpha-3](https://en.wikipedia.org/wiki/ISO3166-1alpha-3) country code. Note: The country code for Great Britain is GB and not UK as is used in…
TokenContextDto
object
The context and identifiers related to the token request. Mandatory for external Third-Party tokens. Use of the /v2/card endpoint: If reusetokentype = INTERNAL…
2 properties
UnauthorizedV2Docs
object
5 properties 1 required
CurrencyCodeEnum
string
Three-letter ISO 4217 alphabetical currency code. e.g. USD. Values correspond to [ISO 4217](https://wikipedia.org/wiki/ISO4217). Deprecated: BYR (replaced by B…
PutDto
object
8 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

verifone-token-management-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 Token Management 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.