Add Amazon Pay to Commercetools to speed up checkout with stored cards, addresses, and biometric authentication, while keeping orders, refunds, tokens, taxes, shipping, and multi-currency mapping accurate.
• Amazon Pay is exposed in the commercetools checkout as a wallet option, and payment authorization is handled via tokenized credentials rather than raw card data stored on the site.
• Buyer identity, shipping address, and selected shipping method data are mapped into commercetools carts and orders, with validation against locale-specific address rules.
• Order totals are recalculated after shipping and tax resolution, and the payable amount is aligned between commercetools and Amazon Pay before capture to avoid mismatches.
• Payment objects and transactions in commercetools store Amazon Pay references (order ID, charge/authorization IDs), supporting traceable state transitions and reconciliation.
• Capture, void, and refund events are synchronized to commercetools order and payment states, with partial refunds supported where business rules allow.
• Multi-currency and rounding behavior is handled through explicit amount mapping per currency, and edge cases are logged when tax, discounts, or shipping changes occur post-authorization.
• Webhook or polling flows ingest Amazon Pay status changes, and idempotency keys prevent duplicate captures when retries, timeouts, or shopper back-button scenarios happen.
.png)
We implement the Amazon Pay buttons and flows in your storefront, then map payment, address, and authentication tokens into Commercetools payment and order objects. The goal is a short, PCI-aligned path from cart to authorization and capture.
At minimum you need consistent mapping for authorization, capture, refunds, and order state updates, plus customer and address references. Missing details here usually show up later as reconciliation issues and support tickets.
Yes, but it depends on how totals, tax lines, shipping methods, and rounding are calculated and passed during authorization. We validate these edge cases in sandbox and stage to prevent “authorized but not shippable” orders.
Refunds and partial captures require clean linkage between the Commercetools payment transactions and Amazon Pay charge permissions. We also cover failure states so your OMS and customer service team see accurate statuses.
Small checkout details move revenue, and we treat this as a payment, UX, and performance project, not just an API task. scandiweb has delivered 2,100+ eCommerce projects and runs CRO programs with 1,000+ A/B tests launched.




