amzn/amazon-pay-api-sdk-php

Version 2.7.2 - July 2025

• Introducing CreateStore and UpdateStore APIs for managing stores within merchant accounts
• Note: These APIs are restricted to allowlisted Solution Providers only

Version 2.7.1 - June 2025

• Replaced deprecated curl_close() calls with unset() for PHP 8.5 compatibility

Version 2.7.0 - May 2025

• Introducing GetDispute API which is used to retrieve details of a chargeback dispute associated with a specific order
• Introducing retry logic for HTTP Code 425
• Renamed PaymentServiceProviderClientInterface 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.
• Note: If you are directly using PaymentServiceProviderClientInterface, please update your implementation to use DisputeClientInterface. The previous interface has been removed as of this release.

Version 2.6.8 - February 2025

• 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 filing a chargeback with their bank.
• The 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.
• The 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.
• The 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).
• The 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.
• Introducing the updateCharge API which enables you to update the charge status of any PSP (Payment Service Provider) processed payment method (PPM) transactions.
• Upgraded phpseclib/phpseclib & phpunit version to meet security requirements
• Removed utf8_encode as it depreacted, instead used mb_convert_encoding method for encoding

Version 2.6.7 - September 2024

• Introducing the getDisbursements API.
• The getDisbursements API enables you to retrieve disbursement details based on a specified date range for settlement dates.

Version 2.6.6 - July 2024

• Introducing new Account Management APIs that allow partners to programmatically onboard merchants onto the Amazon Pay.
   

Version 2.6.5 - March 2024

• Avoid calling the php_uname function if it's disabled in the php.ini configuration

Version 2.6.4 - September 2023

• Introducing new Merchant Onboarding & Account Management APIs, which allows our partners to onboard merchants programatically and as part of account management offer them creation, updation and deletion/dissociation capability.
• Added the Sample Code snippets for the Charge APIs, Charge Permission APIs and Refund APIs.

Version 2.6.3 - September 2023

• Introducing new API called finalizeCheckoutSession which validates critical attributes in merchantMetadata then processes payment. Use this API to process payments for JavaScript-based integrations.
• Corrected README.md file related to finalizeCheckoutSession API.

Version 2.6.2 - June 2023

• Added optional headers to APIs. These are intended to be used by solution providers to send their platform/plugin id’s and versions.
• Corrected README.md file related to Reporting APIs.

• 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.
• Please dont use 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
• Upgraded phpseclib version from "2.0" to "3.0"
• Note : From this SDK version, "algorithm" need to be provided as additional field in "createCheckoutSessionConfig" while rendering Amazon Pay button.

• 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 non environment specific keys

• Removing deprecated API calls

• Underlying endpoint for getBuyer API changed

• Added getBuyer() API call
• 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

• 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