NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist · #1984 most downloaded on Packagist
Amazon Pay API SDK (PHP)
Last release 13 days ago
24 Sep 2026
Release timing varies
gaps range from 1 weeks to 13 months
Most releases are documented
notes for 24 of 29 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
29 releases · first in 2020
One column per quarter.
Narrowed the phpseclib/phpseclib dependency constraint to ^3.0.34 to prevent installation of phpseclib v4, which renames the phpseclib3 namespace and
phpseclib/phpseclib dependency constraint to ^3.0.34 to prevent installation of phpseclib v4, which renames the phpseclib3 namespace and breaks signature generation (#57)region value in the Client constructor, throwing a descriptive exception for missing, empty, or unsupported regions instead of failing later at the first API call (#56)Introducing CreateStore and UpdateStore APIs for managing stores within merchant accounts
CreateStore and UpdateStore APIs for managing stores within merchant accountsReplaced deprecated curl_close() calls with unset() for PHP 8.5 compatibility
curl_close() calls with unset() for PHP 8.5 compatibilityIntroducing GetDispute API which is used to retrieve details of a chargeback dispute associated with a specific order
GetDispute API which is used to retrieve details of a chargeback dispute associated with a specific orderPaymentServiceProviderClientInterface to DisputeClientInterface to align with current Amazon Pay support for both PSP (Payment Service Provider) and 1PP (Standard) merchants in the Disputes and Files APIs.PaymentServiceProviderClientInterface, please update your implementation to use DisputeClientInterface. The previous interface has been removed as of this release.Introducing new v2 Dispute APIs for PSPs (Payment Service Provider). Buyers can create a dispute by filing an Amazon Pay A-to-z Guarantee claim or by
createDispute API is used to notify Amazon of a newly created chargeback dispute by a buyer on a transaction processed by the PSP (Payment Service Provider), ensuring the dispute is properly accounted for in the Amazon Pay systems.updateDispute API is used to notify Amazon of the closure status of a chargeback dispute initiated by a buyer for orders processed by a partner PSP (Payment Service Provider), ensuring proper accounting within the Amazon systems.contestDispute API is used by the partner, on behalf of the merchant, to formally contest a dispute managed by Amazon, requiring the submission of necessary evidence files within the specified Dispute Window (11 days for Chargeback, 7 days for A-Z Claims).uploadFile API is utilised by PSPs (Payment Service Provider) to upload file-based evidence when a merchant contests a dispute, providing the necessary reference ID to the evidence file as part of the Update Dispute API process.updateCharge API which enables you to update the charge status of any PSP (Payment Service Provider) processed payment method (PPM) transactions.Introducing the getDisbursements API.
getDisbursements API enables you to retrieve disbursement details based on a specified date range for settlement dates.Introducing new Account Management APIs that allow partners to programmatically onboard merchants onto the Amazon Pay.
Avoid calling the php_uname function if it's disabled in the php.ini configuration
Introducing new Merchant Onboarding & Account Management APIs, which allows our partners to onboard merchants programatically and as part of account m
Introducing new API called finalizeCheckoutSession which validates critical attributes in merchantMetadata then processes payment. Use this API to pro
Added optional headers to APIs. These are intended to be used by solution providers to send their platform/plugin id’s and versions.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Enabled Proxy Support for HttpCurl
Fixed Deprecation error for PHP version 8 - Passing null to parameter ($data) of type string is deprecate
Applied patch to address issues occurred in Version 2.3.0.
Migrated signature generating algorithm from AMZN-PAY-RSASSA-PSS to AMZN-PAY-RSASSA-PSS-V2 & increasing salt length from 20 to 32
Changing loose comparison operators to strict comparison operators to reduce unexpected behaviors and vulnerabilities
Added API Retry mechanism for error codes 502 & 504
Enabled support for environment specific keys (i.e Public key & Private key). The changes are fully backwards-compatible, where merchants can also use
* Removing deprecated API calls
Underlying endpoint for getBuyer API changed
Fix issue with API call failures when request payload arrays contain character encodings other than UTF-8
Added generateButtonSignature() helper function to generate static signature for amazon.Pay.renderButton used by checkout.js
For /v2/ pay-api.amazon.com|eu|jp endpoints
For /v2/ pay-api.amazon.com|eu|jp endpoints
New completeCheckoutSession API: POST to v2/checkoutSessions/{checkout_session_id}/complete
There are subtle changes in the back-end API between v1/ and v2/, please check online integration changelog for complete details
Any references in code to webCheckoutDetail, paymentDetail, and statusDetail need to be pluarized to webCheckoutDetails, paymentDetails, and statusDetails before moving to the new SDK
Billing address is a top-level node now instead of being in PaymentPreference
There are also non-subtle workflow changes between v1/ and v2/ as the completeCheckoutSession API call will be required now before funds can be captured. See the API Release notes for more details.
Underlying API is going to be versioned; refactoring SDK to realign with API major version numbering
Your coding agent can read these notes before it upgrades. Set up the MCP server →