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

Visa Payment Service API

The Payment web service is used for processing payments and sending payment remittance information to the appropriate suppliers.

Visa Payment Service API is one of 84 APIs that Visa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payment Service. The published artifact set on APIs.io includes an OpenAPI specification, a getting-started guide, authentication docs, and API documentation.

This API exposes 6 operations across 6 paths, and defines 5 schemas. It is described by OpenAPI 3.0.1, at version 1.

Requests are made against a single base URL, https://sandbox.api.visa.com.

6 operations 6 paths 5 schemas 6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1
Server
https://sandbox.api.visa.com
Resource Areas
1

Paths & Operations 6

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

Payment Service 6

The Payment web service is used for processing payments and sending payment remittance information to the appropriate suppliers.

POST
/vpa/v1/payment/GetPaymentDetailURL
Get Payment Detail URL
Get Payment Detail URL body → 201400
POST
/vpa/v1/payment/GetPaymentDetails
Get Payment Details
Get Payment Details body → 201400
POST
/vpa/v1/payment/ResendPayment
Resend Payment
Resend Payment body → 201400
POST
/pop/v1/recipes/processPayment
Process Payment - Recipe
body → 200201401403404
POST
/vpa/v1/payment/CancelPayment
Cancel Payment
Cancel Payment body → 201400
POST
/vpa/v1/payment/ProcessPayments
Process Payments
Process Payments body → 201400

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Payment-1 (11 properties), Supplier-1 (11 properties), Invoices-1 (5 properties), ProcessPaymentRequestDTO (4 properties). Each schema is shown below with its type and property counts.

AlternateEmailAddr
object
1 property
Supplier-1
object
11 properties 1 required
ProcessPaymentRequestDTO
object
4 properties 4 required
Invoices-1
object
5 properties
Payment-1
object
11 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

visa-payment-service-api-openapi.yml Raw ↑

Other APIs Visa publishes across the network.

Visa Government Insights Hub
Visa Payment Account Reference Inquiry
Visa Pilot Program Enablement
Visa Underwriting Intelligence Solutions
VCA Data Exchange
Visa Practical Money Skills Financial Education Platform
Visa Resolve Online
Visa Europe Payment Stop Service
Visa Subscription Manager
Order Insight Digital
Visa dCVV2 Generate
Visa Risk Manager
Where this information came from

This is an independent, third-party profile of Visa Payment Service 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.