Amazon Pay for WooCommerce

Typical turnaround is 5 to 10 business days from the point we receive your Amazon Pay merchant credentials and staging access. Simple installs (standard theme, no subscriptions) land at the faster end; Subscriptions, WPML, or multisite integration adds time. We confirm a firm lead time in writing during scoping before you pay, and we build and validate everything in your sandbox first.

Every build includes a support window for bug fixes and configuration help after go-live. Because you receive the full source in your own repository, you're never locked in. For ongoing WooCommerce and Amazon Pay SDK version compatibility — for example when a WooCommerce major release or HPOS change lands — we offer an optional maintenance retainer. We scope that with you separately so you only pay for what you need.

Yes. Amazon Pay requires an approved merchant account in a supported selling region, and you provide the API keys, merchant ID, and store ID. We cannot create that account for you, but we guide you through registration. If Amazon Pay is not available in your country, we tell you honestly during scoping rather than after purchase.

Yes. The plugin is built HPOS-ready, reading and writing through the WooCommerce CRUD layer so it works with custom order tables. We test the Amazon Pay button against your active theme and place it via standard hooks. WooCommerce Subscriptions support uses Amazon Pay charge permissions for recurring renewals and is included when your store needs it.

No. You get clean, readable, standards-compliant PHP delivered to your own Git repository, with no encrypted blobs and no per-seat license server. Secrets such as your Amazon private key are stored outside the web root and kept out of the database and logs. You own the code and can audit or extend it freely.