Amazon Payment Services

Amazon Payment Services provides payment processing solutions that enable merchants to accept online payments across multiple channels, including credit cards, debit cards, and alternative payment methods. Leveraging Amazon’s global infrastructure, the service offers secure, scalable, and compliant transaction handling, fraud detection, and settlement capabilities for businesses of all sizes. It integrates with e‑commerce platforms, mobile apps, and point‑of‑sale systems, delivering a seamless checkout experience while adhering to PCI DSS standards and regional regulatory requirements.

Amazon Payment Services is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Payments, FinTech, API, and E-commerce.

The Amazon Payment Services catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Amazon Payment Services’ developer surface includes sandbox, authentication, documentation, API reference, pricing, engineering blog, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

31.6/100 thin Agent 33/100 agent ready Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

2 APIs

Company PaymentsFinTechAPIE-commercePaymentsGateway

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 31.6/100 · thin

Contract Quality 5.1 / 21

Developer Ergonomics 9.3 / 17

Access Clarity 1.8 / 17

Operational Transparency 1.2 / 11

Contract Governance 3.6 / 10

Discoverability 4.9 / 9

Regulatory Posture 4.2 / 15

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/amazon-payment-services/"><img src="https://apis.io/badge/amazon-payment-services/card.svg" alt="Amazon Payment Services on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 23.9 — up to +19.0 composite points
Access Clarity scores 10.5 — up to +17.9 composite points
Operational Transparency scores 10.5 — up to +11.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/amazon-payment-services/apis.yml: open an issue on github.com/api-evangelist/amazon-payment-services to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Amazon Payment Services API

API reference for Amazon Payment Services covering payment processing, hosted checkout, tokenization, and related operations.

Amazon Payment Services API

Amazon Payment Services API as documented publicly: 5 operations. Contract generated from the documentation by API Evangelist (2026-10-27); not the provider's own document.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Amazon Payment Services Context

7 classes · 23 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Amazon Payment Services API Rules

8 rules · 6 errors 1 warnings 1 info

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

GetFortapiPaymentapiResponse

11 properties

JSON SCHEMA

PostFortapiBatchapiResponse

11 properties

JSON SCHEMA

PostFortapiPaymentapiRequest

9 properties

JSON SCHEMA

PostFortapiPaymentapiResponse

18 properties

JSON SCHEMA

PostFortapiUploadResponse

10 properties

JSON SCHEMA

PostIntegrationBatchBatchapiResponse

10 properties

JSON SCHEMA

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Amazon Payment Services Authentication

1 scheme

SECURITY

Amazon Payment Services Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Amazon Payment Services Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Sandbox

Sandbox

DeveloperPortal

DeveloperPortal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

SDKs

SDKs

Packages

Packages

Access & Security 5

Authentication, authorization, and security posture

Security

Security

Authentication

Authentication

SecurityTxt

SecurityTxt

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Commercial 1

Pricing, plans, and the legal terms of use

Pricing

Pricing

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 3

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

GetStarted

GetStarted

Source (apis.yml)

aid: amazon-payment-services
name: Amazon Payment Services
image: https://m.media-amazon.com/images/G/01/APS/website/Amazon-Payment-Services-Launched-in-MENA-1-1440x564_c1.png
description: Amazon Payment Services provides payment processing solutions that enable merchants to accept online payments
  across multiple channels, including credit cards, debit cards, and alternative payment methods. Leveraging Amazon’s global
  infrastructure, the service offers secure, scalable, and compliant transaction handling, fraud detection, and settlement
  capabilities for businesses of all sizes. It integrates with e‑commerce platforms, mobile apps, and point‑of‑sale systems,
  delivering a seamless checkout experience while adhering to PCI DSS standards and regional regulatory requirements.
url: https://raw.githubusercontent.com/api-evangelist/amazon-payment-services/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-27 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-27'
modified: '2026-10-27'
tags:
- Company
- Payments
- FinTech
- API
- E-commerce
- PaymentsGateway
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/amazon-payment-services-rules.yml
- type: JSONLD
  url: json-ld/amazon-payment-services-context.jsonld
- type: Vocabulary
  url: vocabulary/amazon-payment-services-vocabulary.yml
- type: DataModel
  url: data-model/amazon-payment-services-data-model.yml
- type: Sandbox
  url: sandbox/amazon-payment-services-sandbox.yml
- type: Security
  url: https://hackerone.com/amazonvrp
- type: Authentication
  url: authentication/amazon-payment-services-authentication.yml
- type: Conformance
  url: conformance/amazon-payment-services-conformance.yml
- type: LLMsTxt
  url: llms/amazon-payment-services-llms.txt
- type: SecurityTxt
  url: well-known/amazon-payment-services-aws-security.txt
- type: WellKnown
  url: well-known/amazon-payment-services-well-known.yml
- type: Hosts
  url: hosts/amazon-payment-services-hosts.yml
- type: Vendors
  url: vendors/amazon-payment-services-vendors.yml
- type: SDKs
  url: packages/amazon-payment-services-packages.yml
- type: Packages
  url: packages/amazon-payment-services-packages.yml
- type: VulnerabilityDisclosure
  url: security/amazon-payment-services-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/amazon-payment-services-domain-security.yml
- type: Website
  url: https://paymentservices.amazon.com/
- type: DeveloperPortal
  url: https://paymentservices.amazon.com/
- type: Documentation
  url: https://paymentservices.amazon.com/docs/
- type: APIReference
  url: https://paymentservices.amazon.com/docs/api
- type: Pricing
  url: https://paymentservices.amazon.com/pricing
- type: Blog
  url: https://paymentservices.amazon.com/blog
- type: GetStarted
  url: https://paymentservices.amazon.com/get-started/dashboard
apis:
- name: Amazon Payment Services API
  description: API reference for Amazon Payment Services covering payment processing, hosted checkout, tokenization, and related
    operations.
  humanURL: https://paymentservices.amazon.com/docs/api
  aid: amazon-payment-services:amazon-payment-services-api-2
- aid: amazon-payment-services:amazon-payment-services-api
  name: Amazon Payment Services API
  description: 'Amazon Payment Services API as documented publicly: 5 operations. Contract generated from the documentation
    by API Evangelist

    (2026-10-27); not the provider''s own document.'
  humanURL: https://paymentservices.amazon.com/docs/api/services/batch
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/amazon-payment-services-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/amazon-payment-services-post-fortapi-paymentapi-response-schema.json
  - type: JSONSchema
    url: json-schema/amazon-payment-services-get-fortapi-paymentapi-response-schema.json
  - type: JSONSchema
    url: json-schema/amazon-payment-services-post-fortapi-batchapi-response-schema.json
  - type: JSONSchema
    url: json-schema/amazon-payment-services-post-fortapi-upload-response-schema.json
  - type: JSONSchema
    url: json-schema/amazon-payment-services-post-integration-batch-batchapi-response-schema.json
  - type: JSONSchema
    url: json-schema/amazon-payment-services-post-fortapi-paymentapi-request-schema.json
x-submission-probe: 200, 2026-10-26
x-coverage:
  state: unreadable
  reason: js-rendered-docs
  detail: API documentation is rendered via JavaScript and provides no machine‑readable OpenAPI spec.
  evidence:
  - url: https://paymentservices.amazon.com/docs/api
    status: 200
  checked: '2026-10-27'
x-enrichment:
  date: '2026-10-27'
  status: enriched
  artifacts_added: 27
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Amazon Payment Services API — frequently asked questions

Does Amazon Payment Services have an API?

Yes. APIs.io lists 2 APIs from Amazon Payment Services, including Amazon Payment Services API and Amazon Payment Services API.

Is there an OpenAPI specification for the Amazon Payment Services API?

Yes. APIs.io indexes 1 OpenAPI specification for Amazon Payment Services, each linked for download from this page.

How do I authenticate with the Amazon Payment Services API?

Amazon Payment Services documents its authentication (1 scheme). The details are profiled on APIs.io as Amazon Payment Services Authentication.

Is the Amazon Payment Services API ready for AI agents?

Amazon Payment Services has a Kin Score of 31.6 out of 100 (thin) and an Agent Readiness score of 33.3 (agent-ready), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/amazon-payment-services"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/amazon-payment-services/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/amazon-payment-services/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.