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 Payment Modifications API

The Payment Modifications API from Verifone — 12 operation(s) for payment modifications.

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

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

This API exposes 12 operations across 12 paths, and defines 47 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.

12 operations 12 paths 47 schemas 12 POST

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 Payment Modifications 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 12

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

Payment Modifications 12
POST
/api/v2/transactions/{id}/void
Void authorization
voidAuthorization 1 param → 201400401403404500
POST
/api/v2/transactions/{id}/klarna_complete
Complete a Klarna payment
klarnaPaymentTransaction 2 params body → 200400401403404500
POST
/api/v2/transactions/{id}/adjust
Adjust the preauth transaction amount
Adjust Payment 1 param body → 201400401403404500
POST
/api/v2/transactions/{id}/capture
Capture authorization
captureAuthorization 1 param body → 201400401403404500
POST
/api/v2/transactions/{id}/refund
Refund payment
refundPayment 2 params body → 201400401403404500
POST
/api/v2/transactions/refund
Unmatched refund
unmatchedRefund body → 201400401403404500
POST
/api/v2/transactions/{id}/void_capture
Void capture
voidCapture 1 param → 201400401403404500
POST
/api/v2/transactions/reverse
Reverse Transaction
reverseTransaction 1 param → 201400401403404500
POST
/api/v2/transactions/{id}/release
Release PreAuthorization
ReleasePreAuthorization 2 params body → 201400401403404500
POST
/api/v2/transactions/{id}/extend
Extend preauthorization
extendAuthorization 2 params → 201400401403404500
POST
/api/v2/transactions/{id}/issuer_instalment_selection
Issuer Instalment Selection
issuerInstalmentSelection 1 param body → 201400401403404500
POST
/api/v2/transactions/affirm_complete
Complete a Affirm payment
affirmCompleteTransaction 1 param body → 201400401403404500

Schemas 47

The contract defines 47 schemas that model the data the API accepts and returns. The most detailed are EcomResponse (40 properties), klarnaPaymentCompletionResponse (20 properties), TokenDetails (19 properties), unmatchedRefundBaseRequest (16 properties). Each schema is shown below with its type and property counts.

ecomPaymentResponse_issuer_instalment_result
object
Issuer-managed instalment response. May be used to inform on supported instalment options for the transaction in specific programs (e.g., Mastercard Instalment…
12 properties
affirmPaymentCompletionRequest
object
2 properties
ShippingInformation
object
9 properties 4 required
StoredCredential
object
5 properties
paymentPlanOption
object
An instalment plan option available for the transaction. Instalments are managed by the issuer. To the merchant this is just another transaction.
7 properties
EcomResponse
object
40 properties
UnauthorizedV2Docs
object
5 properties 1 required
Details
object
2 properties
TokenDetails
object
19 properties
settlementDate
string
This will reflect either the desired Merchant settlement date or the actual settlement date depending where the transaction request is within the payment lifec…
MultipleCapturesDto
object
3 properties 1 required
PromoFinancingResults
object
Details of the special financing offer returned from the issuer.
7 properties
ForbiddenV2Docs
object
5 properties 1 required
klarnaPaymentCompletionResponse
object
20 properties
AdditionalData
object
Additional payment result data, which may be required to return in a particular payment response.
7 properties
amountDecimal
number
Amount including decimal place.
initiatorTraceId
string
A number assigned by a transaction initiator(originator) to assist in identifying a transaction uniquely. The trace identifier remains unchanged for all messag…
DetailedAmount
object
A structure that represents a breakdown all of the different amounts that may appear on a single transaction.
3 properties
PromoFinancingDetails
object
Additional details of the special financing offers to customers using private label cards, typically in combination with promocode field.
3 properties
acquirerResponseMessage
string
The response description generated by the acquirer corresponding to the acquirer response code.
instalment
object
The details on the instalment-scheme that should be enacted by the issuer.
9 properties 1 required
UnmatchedLineItem
object
The description of item(s) that was included in a transaction or purchase.
12 properties 2 required
unmatchedRefundEncryptedCardRequest
object
acquirerAuthorizingNetworkID
string
The Network ID returned in the original authorization response.
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…
PaymentProductType
string
The payment product type corresponding to this transaction. Fees applied to the transaction, is based on the payment product
unmatchedRefundTokenRequest
object
acquirerAuthorizingNetworkIdDescriptor
string
The name or descriptor that corresponds with the acquirerauthorizingnetworkid returned in the original authorization response.
klarnaPaymentCompletionRequest
object
3 properties
ReleasePreauthDto
object
1 property
CaptureCardTransactionDto
object
8 properties 1 required
klarnaPaymentCompletionResponse_authorized_payment_method
object
3 properties
unmatchedRefundBaseRequest
object
16 properties 3 required
EcomReverseTransactionResponse
object
2 properties 2 required
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…
ecomPaymentResponse_details
object
2 properties
NotFoundV2Docs
object
5 properties 1 required
affirmPaymentCompletionResponse
object
15 properties
issuerInstalmentSelectionRequest
object
1 property
TokenDetailsRequestBody
object
The details related to the token. For Third-Party Reuse tokens, these elements might be required as additional information together with the Reuse token itself…
2 properties
InternalErrorV2Docs
object
5 properties 1 required
BadRequestV2Docs
object
5 properties 1 required
RefusalReason
string
The reason a transaction has been refused within the payment ecosystem by the client/Verifone/acquirer. This needs to be set by the component that is refusing…
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 ------|-------------…
AdjustDto
object
2 properties 1 required
RefundCardTransactionDto
object
7 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

verifone-payment-modifications-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 Payment Modifications 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.