Skip to content

Amazon Pay Balance Integration Checklist

This checklist outlines the key integration steps and configurations required to integrate Amazon Pay Balance.

Checklist Item Details
Merchant Account Configuration
  • Register merchant accounts in Amazon Seller Central portal
    Note: Two separate accounts required for Amazon Pay Balance and Amazon Pay Later with a unique email ID
  • Refer this to fetch MID, Access key and Secret key
  • Upload the merchant logo via Amazon Seller Central
Developer Account Configuration
Client-Side Integration
URL Configuration & Safelisting
  • Share Redirect / Callback URLs (Sandbox & Production) for safelisting
  • Share Webhook / IPN URLs (Sandbox & Production) for safelisting
Server-Side API Integration
  • Implement Access Token and Refresh Token API
  • Implement Instrument API
  • Implement Charge API
  • Implement Charge Status API
  • Implement Refund API
  • Implement Refund Status API
Transaction Validation
  • Validate the transaction and refund status response received at the safelisted webhook URL
  • Validate transactions using webhook/IPN response and Status API
  • Note: Don't rely only on UI Callback for web-based integration and Result Code in case of Android
Android-Specific Considerations
  • Call init() in MainActivity.onCreate() to initialise Amazon Pay SDK
  • Call getPaymentMetaData() on the payment screen, just before triggering the Charge API and pass the returned string directly to the Charge API request body
UI Requirements
  • Add the Amazon Pay logo on the payment method selection page. Find Amazon Pay logo here
  • Ensure logo visibility on consent page – Upload the logo on Developer portal under Security Profile Management
  • Display as 'Amazon Pay Balance' for Wallet and 'Amazon Pay Later' for Pay Later
  • Implement KFS (Key Fact Statement) link for APL (First time & every transaction).
    Display a message like "By proceeding, I understand and agree to the Key Fact Statement"
  • Grey out APL option based on eligibility response received in Instrument API call
  • Display Available Balance under Amazon Pay Balance option and Available Credit under Amazon Pay Later. To know more refer to this
Account Linking & Flow Validation
  • Handle Account linking Successful and Failed scenarios
  • Handle insufficient balance scenario by invoking amazonPayUrl returned in response to Charge API
  • Validate end-to-end flows for Amazon Pay Balance and Amazon Pay Later
App Signing & API Key Validation (Android)
  • Generate separate API keys for Debug and Release builds
  • Confirm the app signing method (e.g., Play App Signing or self-managed signing)
  • Generate the API key using the correct signing key — use the Play signing key if Play App Signing is enabled
  • Generate the API key before uploading to the Play Store
Restrictions on APB/APL
  • Amazon Pay Balance should not be available for Gift Card purchases or Subscription-based payments
  • Amazon Pay Later should not be available for wallet loads, Gift Card purchases (including third-party Gift Cards), Subscription-based payments, or purchases of gold and silver ornaments/coins

⚠️ Critical Points to Note
  • Two separate merchant accounts (one for Amazon Pay Balance, another for Amazon Pay Later) must be created using unique email IDs
  • Separate MerchantId (MID) and credentials must be used for each product (do not interchange)
  • Implementation of the KFS (Key Fact Statement) link for Amazon Pay Later is mandatory
  • In API calls, the client-id in the header refers to the MerchantId (MID)
  • Security Profile ID, redirect and webhook URLs must be shared with integration POC for safelisting
  • Webhooks/IPNs must be configured and validated
  • Transaction status must be verified via IPN/Status API (do not rely only on browser response)
  • paymentMetaData must be passed correctly for Android-based transactions when calling the Charge API
  • API key must match the app signing key