Accepting Amazon Pay on your own store

Amazon Pay lets a shopper check out on your site using the card and address already stored in their Amazon account. Amazon handles authentication and contributes fraud signals; you receive settlement and fulfil the order. The appeal is obvious in markets where Amazon account penetration is high, particularly Germany, France and the United Kingdom. The trade-off is less obvious, and it is the reason this method deserves a decision rather than a default.

Distinction

Amazon Pay is not selling on Amazon

Worth separating clearly, because the two are constantly conflated and the economics have nothing in common. Selling on the Amazon marketplace means referral fees, fulfilment fees and a customer relationship that belongs to Amazon. Amazon Pay is a wallet button on your own store, priced as payment acceptance, with the order and the customer remaining yours. If someone in your business is quoting marketplace referral percentages when discussing Amazon Pay, the conversation has gone wrong before it started.

How to accept Amazon Pay as a merchant

You do not contract with a scheme here in the usual sense. Amazon Pay is integrated either directly or through your PSP, and which route you take changes both the pricing and who owns the reconciliation. Integrated through a PSP, Amazon Pay appears as one method among many in a single settlement flow. Integrated directly, it becomes a second settlement relationship with its own reporting, its own payout timing and its own dispute process. Neither is wrong, but the second is often chosen by accident rather than deliberately.

Amazon Pay payment gateway and PSP support

Support is broad across gateways serving European markets, so it is not a selection criterion. What separates providers is the rate applied to Amazon Pay volume, whether that rate is visible as its own line, and how cleanly the settlement reconciles against your order data. Wallet methods are where blended pricing does most of its damage, because the wallet fee and the underlying card economics get folded into one average that nobody can decompose.

Settlement

Two settlement relationships, and what the second one costs

The section above says the direct route is often chosen by accident. Here is what the accident costs, so that it can be chosen on purpose instead.

A second settlement relationship is not a second contract, it is a second month-end. It brings its own payout calendar, so cash arrives on a different day from everything else. It brings its own reporting format, which somebody has to map to your order identifiers. It brings its own dispute process with its own deadlines, which is a second place where a missed date costs money. And the month no longer closes from one file.

The threshold is arithmetic. If the direct route is twenty basis points cheaper and your Amazon Pay volume is 300,000 euros a year, that is 600 euros against a reconciliation that costs more than that in finance time before anyone has benefited from it. At 3 million euros the same twenty points is 6,000 euros and the calculation reverses. Somewhere between those two the answer changes, and what decides it is your own volume rather than a preference for tidy integrations.

Amazon Pay fees and what actually drives them

Underneath the button, an Amazon Pay transaction is still a card transaction, so it carries card economics plus the wallet layer. That is the structural point most merchants miss. A wallet does not remove interchange, it adds a party. Whether the total is competitive depends on how the wallet layer was priced in your agreement and whether the card cost underneath it is passed through or absorbed into a blend. If Amazon Pay carries a meaningful share of your volume and you cannot see its effective rate separately from cards, you are not in a position to judge it.

Segments

The same button buys two different things

Amazon Pay converts because Amazon holds the identity, the stored card and the address book. That is worth a great deal to a customer who has never bought from you, and close to nothing to a returning customer who already has a card stored with you and an address on file. The fee is the same in both cases, so the same button is buying two different things and only one of them is worth the price.

The split is easy to produce and almost nobody has it. Take 4 million euros of revenue with 35 per cent from first-time customers, so 1.4 million euros. If Amazon Pay carries 18 per cent of that, 252,000 euros at 2.2 per cent against a card at 1.3 per cent is 2,268 euros of extra fee, spent on removing the exact friction that stops first-time buyers: typing a card number and an address into a shop they have not used before. That is a good trade at almost any plausible lift. On the other 2.6 million euros from returning customers, Amazon Pay carrying 12 per cent is 312,000 euros, and the same 0.9-point gap is 2,808 euros spent on a convenience the customer already had with you.

The conclusion is not to remove the button. It is that what your checkout shows first should differ between a recognised returning customer and a new one. Ask your provider whether the selector can be ordered by customer state at all, because in a large number of set-ups it cannot, and then it is the constraint doing the deciding rather than anybody’s commercial judgement.

Which payment provider supports Amazon Pay for merchants in Europe?

MultiSafepay, PAYONE and Datatrans all document Amazon Pay, but not every gateway still offers it, so this is one of the few wallets where availability is worth confirming rather than assuming. The better questions are what each charges for wallet volume, whether the underlying card cost is transparent, and what conversion lift you are actually getting in exchange. That last part is measurable, and it is worth measuring rather than assuming, because the lift a wallet delivers varies enormously by category and basket value.

Strategy

The strategic question: a competitor’s checkout on your store

Amazon Pay converts well precisely because Amazon owns the identity, the stored card and the address book. For a brand that also competes with Amazon for the same customer, that is a real consideration rather than a theoretical one. It does not make the method wrong. It makes it a decision with a commercial dimension beyond the fee, and one that a direct-to-consumer brand should take consciously, weighing conversion against the reinforcement of a shopping identity it does not control.

Reviewing what Amazon Pay costs you

What you pay for wallet acceptance is set in your PSP or Amazon Pay agreement, not by a scheme, and it is negotiable like any other line. Start by establishing whether you are overpaying your PSP, or look at what payment performance optimisation does to authorisation rate and cardmix, which is where a wallet earns or costs you money.

How a wallet behaves inside your flow, from one-click through to the return after a challenge, is a checkout flow optimisation question as much as a pricing one.

Relevant markets: Germany, France, United Kingdom, Italy, Spain, Austria, Netherlands