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

Apple Pay Payment Processing API

Endpoints for receiving and processing Apple Pay payment tokens

Apple Pay Payment Processing API is one of 5 APIs that Apple Pay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Payment Processing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, an API reference, and 2 JSON Schemas.

This API exposes 1 operation across 1 path, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://{merchantServer}.

1 operations 1 paths 8 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://apple-pay-gateway.apple.com
Terms of Service
Resource Areas
1

Paths & Operations 1

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

Payment Processing 1

Endpoints for receiving and processing Apple Pay payment tokens

POST
/payments/apple-pay
Process an Apple Pay payment
processApplePayPayment body → 200400401422500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are PaymentContact (14 properties), PaymentResult (6 properties), PaymentDataHeader (5 properties), PaymentMethod (4 properties). Each schema is shown below with its type and property counts.

PaymentToken
object
The Apple Pay payment token containing encrypted payment credentials. This token is generated by the Secure Element on the user's device after biometric or pas…
3 properties 3 required
PaymentMethod
object
Information about the payment card used
4 properties
PaymentResult
object
Result of payment processing
6 properties
ApplePayPaymentSubmission
object
3 properties 1 required
PaymentDataHeader
object
Header fields for the payment data encryption
5 properties
PaymentContact
object
Billing or shipping contact information
14 properties
PaymentData
object
Encrypted payment data. The structure depends on the token version (ECv1 or RSAv2). The data field contains the encrypted payment credentials that must be decr…
4 properties 4 required
PaymentError
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

apple-pay-payment-processing-api-openapi.yml Raw ↑

Other APIs Apple Pay publishes across the network.

PassKit Framework (Apple Pay)
Apple Pay Merchant Registration API
Apple Pay Merchant Validation API
Apple Pay Payment Status API
Where this information came from

This is an independent, third-party profile of Apple Pay Payment Processing 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.