Amazon Pay: Merchant Acceptance, Integration and Operations Guide

How Amazon Pay works

Amazon Pay lets an eligible shopper use payment and address information associated with an Amazon account on a participating merchant’s website. The merchant remains the seller and is responsible for the order, fulfilment, customer support, returns and legal obligations. Amazon Pay is a wallet-style checkout layer; the underlying payment method, merchant agreement and regional product determine authorization, settlement, disputes and fees. Displaying this guide does not establish that FixPays integrates Amazon Pay or that a particular business is eligible.

Merchants should confirm current availability for their legal entity, country, website, product category and integration platform. Amazon Pay documentation varies by region, and some features or fees may not apply everywhere. Before development, obtain the applicable merchant agreement and production account. Keep sandbox success separate from approval to process live transactions.

Integration and checkout states

The current Amazon Pay Checkout documentation uses checkout sessions, charge permissions, charges and refunds. Design the order system around provider identifiers and explicit states rather than a single paid flag. Handle approval, decline, pending authorization, capture, cancellation and timeout. Make create and capture requests idempotent so a customer refresh or network retry cannot produce a duplicate charge.

Asynchronous processing requires special care. Amazon Pay says some authorizations, delayed captures and all refunds may remain initiated before completing or declining. Use Instant Payment Notifications or polling to obtain the final state. Do not fulfil from a browser return page alone, and do not tell a customer a refund is complete until the provider status supports that statement.

Fees and settlement dependencies

Amazon Pay publishes transaction-based pricing that can include processing and authorization components, and its US help material describes an additional cross-border processing fee for a payment method issued outside the United States. It also explains that fee treatment changes for certain platform arrangements such as Amazon Pay with Shopify Payments. Merchants must use the schedule attached to their own region and integration rather than copy an example rate.

Model authorization fees, processing, cross-border treatment, disputes, refunds, taxes and platform costs. Amazon’s US fee page says certain processing fees may be returned on a refund while authorization and disputed-chargeback fees are not. Settlement timing, reserves, deductions and bank-account eligibility should be confirmed in the merchant account. Reconcile gross charge, fees, refund and net settlement using provider reports.

Recurring and automatic payments

Amazon Pay documents recurring Charge Permissions and states that the merchant is responsible for creating each charge for the billing cycle. The merchant must disclose amount, frequency and duration, and variable recurring payments may require advance notice options under Amazon’s policy. Documentation also identifies restrictions and approval requirements for some automatic-payment uses. Do not assume a successful one-time integration permits every future or usage-based charge.

Store the customer authority, terms version, plan, frequency and cancellation state. Send receipts and required renewal communication. Keep service cancellation separate from revoking the wallet permission, while making both effects clear. Test expired permissions, changed payment methods, declined recurring charges and customer cancellation. Avoid repeated retries that could look abusive or create duplicates.

Refunds, disputes and customer support

Amazon Pay’s API permits full or partial refunds against a captured charge and describes refunds as asynchronous. Preserve the refund identifier and monitor it to completion or decline. For digital goods, the documentation advises confirming that the good has not been used and cannot continue to be used before refunding. Apply local law and the merchant’s disclosed policy; do not use that operational note to deny mandatory remedies.

Use a recognisable seller identity and provide accessible support. A dispute file should connect checkout consent, order, shipment or digital fulfilment, communications, cancellation and refund state. Follow the applicable Amazon Pay and underlying payment rules. Never ask a customer to withdraw a dispute as a condition of support. Analyse dispute reasons to improve descriptions, delivery and billing controls.

Practical launch checklist

Confirm account approval, region, currencies, domains, product eligibility, recurring scope, settlement account and fees. Test success, decline, pending authorization, duplicate retry, delayed capture, cancellation, partial refund, full refund, refund decline, notification loss and report export. Make sure the order system can recover state by querying the API.

Train support to distinguish merchant order status from wallet payment status. Monitor authorization, pending duration, refunds, disputes, settlement and customer enquiries. Review official documentation after platform changes. Keep Amazon branding and button presentation within current guidelines, and advertise the method only where the production account actually supports it.

A useful launch exercise is to place one test order and follow it through every internal system. Confirm that support can locate the Checkout Session, the relevant Charge Permission, the charge and any refund from the merchant order number. Then simulate a lost notification and recover the state through the documented API. The exercise should establish that a missed event creates an investigation task rather than an automatic second charge.

For recurring orders, assign ownership of both the billing schedule and customer cancellation. A permission to charge is not the schedule itself. Before each billing run, check that the merchant's subscription remains active and that the amount and timing match the customer's agreement. After a cancellation, verify that future scheduled requests are stopped. Keep the customer-facing outcome clear even when the wallet permission and merchant subscription are managed in different systems.