multiflow vs. Amazon Pay

Amazon Pay is a wallet button. It sits at the top of your checkout page alongside Apple Pay, Google Pay, and Shop Pay. A customer clicks it, Amazon authenticates them, their Amazon-stored card and address fill in, and the order processes. The actual processing still runs through your acquirer — Stripe, Braintree, Square, or whatever else.

multiflow is a layer above your acquirer. It handles which brand gets which descriptor, which brand shows up in which row of finance's reconciliation export, which dispute queue a chargeback lands in. It has no opinion about which wallet buttons render at checkout.

So the question "Amazon Pay or multiflow" is a false choice. Operators running multi-brand portfolios routinely use both: multiflow for orchestration, Amazon Pay for wallet conversion lift at checkout.

Amazon Pay charges 2.9% + $0.30 per transaction for domestic US card acceptance — competitive with Stripe standard pricing. For qualified merchants it drops to interchange-plus tiers. There is no monthly fee.

multiflow is 5.5–7.5% all-in. It is higher than Amazon Pay because it does a different thing. If you only want a wallet button, Amazon Pay is cheaper because that is all it does. If you need portfolio orchestration, multiflow's rate includes that work.

Operators running both pay Amazon Pay's rate on Amazon Pay transactions (routed through the multiflow acquirer underneath) and multiflow's tiered rate on everything else. Finance sees a blended effective rate.

Amazon Pay piggybacks on your Amazon Seller account (or creates one during signup). If you are already an Amazon seller in good standing, Amazon Pay approval is fast. If you are not, Amazon's underwriting applies — documentation of your business entity, tax status, and product category.

multiflow underwrites through our acquirer partners independently. If Amazon declined your seller account (common in certain DTC verticals), we can still approve you through Stripe, Authorize.net partners, or Square depending on what you sell.

Amazon Pay is configured per Amazon Seller account. A 4-brand operator either runs all four brands through one Amazon Pay merchant (which means all four show up on Amazon buyer statements with the same merchant name) or opens four separate Amazon Seller accounts (which requires four legitimate tax entities in most cases).

Neither option gives per-brand descriptor orchestration. multiflow handles descriptors at the processor layer underneath; Amazon Pay renders at checkout; the customer sees the right brand name on their statement regardless.

The risk profile operators worry about with Amazon Pay is not card processing holds — it is Amazon Seller account suspension. If any of your brands have an Amazon marketplace presence and trip Amazon's seller policies, the Seller account suspension can cascade to Amazon Pay acceptance across your DTC sites.

multiflow has nothing to do with that risk. It is an Amazon policy issue. What multiflow does provide: an acquirer-layer failover so that if Amazon Pay acceptance goes dark on one brand, the rest of checkout (cards, Apple Pay, Google Pay) keeps working through our layer.

For a WooCommerce multi-brand portfolio: install the Amazon Pay official plugin at each sub-brand site for wallet rendering. Run card processing and orchestration through the multiflow WooCommerce plugin (MAEF parent/child). Amazon Pay transactions route through the multiflow acquirer underneath when possible, or through an Amazon-Pay-specific processor connection when not.

For Shopify: both have official apps. The integration is additive, not exclusive.