Stripe vs Adyen: Best Payment Gateway for SG Web

1. Local Acquiring and SGD Settlement Routes

Both hold Monetary Authority of Singapore (MAS) Major Payment Institution licences. The difference is how the gateway touches the local rails.

Stripe operates through Stripe Payments Singapore Pte. Ltd. and routes SG‑issued Visa/Mastercard via its direct acquiring connections. Settlement lands as a single SGD batch next business day, and funds hit a DBS, OCBC, or UOB account with same‑day crediting for verified volume. Stripe also plugs into PayNow via SGQR for instant bank transfers — no card fees on that rail, only a fixed S$0.30 charge per transaction.

Adyen runs its Singapore operations through a MAS‑regulated branch. Its single‑platform architecture gives you explicit control over acquiring, processing, and scheme routing. You can hold multiple SG acquiring banks, split traffic, and route fallbacks if one acquirer’s authorization rate dips. Settlement is negotiable — same‑day or T+1 SGD for merchant accounts clearing above S$250k monthly. For web stores doing heavy local volume, Adyen’s local acquiring lowers the effective interchange markup compared to a gateway re‑routing through a HK or EU entity.

2. API Tooling and Checkout Performance Metrics

Stripe’s API documentation and SDK coverage remain the reference standard. A bare‑bones credit card checkout can be up in under ten minutes: use Payment Intents with the `payment_method_options[card][request_three_d_secure]` flag set to `any`. P99 latency of the Create PaymentIntent endpoint consistently runs between 150–220 ms from Singapore‑hosted infrastructure, and Stripe’s webhooks fire within 1–2 seconds of terminal state changes. For SG merchants leaning on Shopify, WooCommerce, or Next.js storefronts, the official Stripe Drop‑in UI is the fastest credible integration.

Adyen has comparable raw API performance — its Checkout API tops out around 130 ms P99 from the APAC endpoint — but the integration complexity sits an order higher. Building a production‑grade Adyen loop means handling their `additionalData` payloads, writing your own webhook verifier (they use HMAC keys per merchant account), and managing Split Payouts if you run a marketplace. The only major SG‑specific advantage: Adyen’s native GrabPay integration returns an encrypted token without forcing you through a third‑party mobile‑SDK bridge, which Stripe still executes as an under‑tested beta in the region.

3. Recurring Billing and Singapore‑Specific Payment Methods

For web apps with recurring revenue — SaaS, software subscriptions, and membership sites — Stripe Billing is materially stronger. SG merchants get prorated plan changes, dunning emails, and automatic retry logic that respects local late‑fee constraints. Adyen’s tokenisation (`paymentMethod.token`) supports saved‑card recurring, but it palms off subscription orchestration to your own codebase; you’re building invoicing, retry, and accounting sync yourself.

On local alternative payment methods, both support the same baseline: PayNow, GrabPay, and SGQR scan‑to‑pay. The operational nuance is in the redirect flows. Stripe presents PayNow as a first‑class payment method within its hosted checkout, showing the QR code inline. Adyen treats PayNow as an APM that opens a separate redirect via its Web SDK — acceptable, but it breaks single‑page checkout immersion. Neither currently processes NETS online transactions as a turning‑key web gateway; you’d need to bolt on a separate NETS plugin, which is a real gap for SG consumer‑facing B2C stores.

4. Pricing in SGD: Published vs Negotiated

Stripe publishes SG pricing with absolute transparency:

Adyen is interchange‑plus. You pay the card scheme interchange (typically 1.3%–2.1% for SG consumer cards) plus a processor markup, often quoted in basis points (usually 15–40 bps). On a S$75 average transaction, Adyen nets out 0.6%–0.9% cheaper than Stripe’s flat rate — but Adyen also imposes a flat per‑transaction fee (often S$0.10–S$0.20) and historically quoted a monthly platform fee for accounts below S$250k annual volume. For a food delivery, ticketing, or B2B portal clearing over S$500k per month, Adyen’s pricing beats Stripe by roughly S$3,000–5,000 annually. For a pre‑revenue MVC or a side project, Stripe’s published plan has zero minimum and zero monthly cost.

5. Segment Verdict: Who Picks Stripe or Adyen

Pick Stripe for:

– Teams shipping solo with limited dev capacity — the dashboard, Fraud Radar, and built‑in dispute tooling solve abuse handling without writing backend rules.

– Subscription and recurring‑revenue web apps where Billing and customer lifecycle automation outweigh rate savings.

– Storefronts built on Shopify/WooCommerce — Stripe’s plugin support is officially maintained and handles SG tax (GST) pass‑through cleanly.

Pick Adyen for:

– SG web merchants doing high‑volume, single‑ticket purchases (electronics, same‑day delivery marketplaces, travel) where 15–40 bps across hundreds of thousands of transactions pays for the engineering overhead.

– Operators needing local SG acquiring control, multi‑acquirer fallback, and split‑payout flows without working through an intermediary bank.

– Teams with a dedicated payments engineer who owns integration, monitoring, and reconciliation outright.

Both gateways hold MAS licensing, reach PayNow/GrabPay, and run APAC‑hosted API endpoints. The decisive factor is your operational profile: Stripe is the gateway you ship in a sprint; Adyen is the gateway you commit to when volume justifies owning the rail.

Summary Table