The right Stripe alternative depends on the operating job you need payments to perform. You may need PayPal or Venmo acceptance, a checkout inside an existing Shopify store, in-person sales, Merchant of Record responsibilities for eligible digital products, interchange-plus pricing, or cross-border accounts and settlement. There is no universal cheapest or best option.
Choose the operating model first, then compare total cost and implementation effort against your transaction mix. A U.S. software company selling subscriptions internationally may shortlist Paddle for supported Merchant of Record transactions. A retailer already using Shopify may prefer Shopify Payments to keep orders and payment data in one commerce system. Those are different decisions, not a ranking.
Choose the provider that removes your main operating constraint. A headline processing rate is only one input.
How to choose a Stripe alternative
A payment processor moves a transaction through acceptance and settlement. A Merchant of Record, or MoR, can also become the seller of record for supported transactions and take on specified responsibilities under its contract. The roles are not interchangeable. An MoR arrangement may affect who handles applicable tax collection, refunds, or chargebacks, while your business may retain supplier accounting and other regulatory duties.
Use this sequence before requesting quotes:
- Map the business. Record your legal entity, business country, customer markets, and sales channels, including online checkout, subscriptions, invoices, marketplaces, and physical point of sale.
- Define payment requirements. List cards, wallets, local methods, currencies, settlement currencies, card-present volume, and international transactions.
- Assign responsibilities. Decide who owns billing, tax collection and remittance, refunds, disputes, reconciliation, customer support, and account review. If you are considering an MoR, compare those duties with its contract.
- Model cost and effort together. Use the same transaction mix for each finalist and include subscriptions, FX, hardware, implementation, reconciliation, and any platform or external-gateway fees.
The U.S.-oriented public pricing examples in this guide were researched on November 19, 2026. Actual pricing and availability can vary by country, legal entity, merchant category, plan, channel, payment method, volume, eligibility, underwriting, and contract. Confirm current terms for your business before selecting a provider.
Match the provider to the operating model
| Operating need | Providers to shortlist | Tradeoff to verify |
|---|---|---|
| PayPal checkout or Venmo acceptance | PayPal; PayPal Enterprise Payments | Compare method-specific prices, checkout products, eligibility, and integration path. Current technical and pricing materials may still use the Braintree name. |
| MoR for eligible digital products | Paddle | Check product and jurisdiction coverage, contractual seller responsibilities, customer support scope, and custom-pricing eligibility. |
| Complex international or enterprise payments | Adyen | Obtain a method- and market-specific quote and assess the engineering and payment-operations capacity required. |
| Payments inside a Shopify store | Shopify Payments | Compare Shopify plan costs, payment rates, external-gateway fees, and plan restrictions. |
| Retail POS with online sales | Square | Compare hardware, location-based plans, in-person rates, online rates, and required retail features. |
| Interchange-plus pricing | Helcim | Model interchange and network costs plus the published margin against your card, channel, and volume mix. |
| Multi-currency finance and cross-border payments | Airwallex | Confirm entity eligibility, account and settlement currencies, FX and transfer costs, and checkout fit. |
Shortlist within the category that matches your main constraint. Then confirm the specific country and legal entity, payment methods, settlement options, underwriting requirements, and operational owner for refunds and disputes. PayPal publishes separate U.S. prices for different payment methods, including card, PayPal, and Venmo transactions. See PayPal’s U.S. fee schedule and its PayPal Enterprise Payments information.
Compare total cost, not the advertised rate
Flat-rate processing, interchange-plus margins, MoR fees, and commerce-platform subscriptions describe different cost structures. Compare them using the same monthly transaction profile instead of treating every percentage as an equivalent effective rate.
- PayPal: its U.S. pricing page lists card processing starting at 2.89% plus $0.29, and PayPal or Venmo at 3.49% plus $0.49. These are method-specific examples, not one universal PayPal rate. Review the current U.S. pricing and detailed merchant fee tables.
- Paddle: publicly lists 5% plus $0.50 per Checkout transaction. It also describes custom pricing for some high-volume or complex businesses. Check the applicable offer at Paddle pricing.
- Adyen: publishes a fixed processing fee plus payment-method-specific charges. The public model is not one flat rate for every market or method, so request a relevant quote through Adyen’s pricing information.
- Shopify Payments: is included with Shopify plans rather than being a standalone $29 monthly payment subscription. The U.S. Basic plan is listed at $39 monthly or $29 monthly when billed yearly, while online card rates depend on plan. Shopify says orders processed solely through Shopify Payments avoid its third-party transaction fees, while an external provider may add Shopify fees to its own charges. See Shopify plan pricing and its payment-cost explanation.
- Square: its U.S. Retail Plus plan is listed at $49 per location per month. Square offers other plans and products, with rates varying by channel and product. See Square Retail pricing.
- Helcim: publishes interchange-plus margins by channel and rolling three-month processing-volume tier. The margin is not the complete effective rate because interchange and network costs remain variable. Review Helcim’s pricing details.
- PayPal Enterprise Payments: standard U.S. card and third-party digital-wallet pricing is listed at 2.89% plus $0.29. Venmo and other methods have different pricing, and international charges can apply. Check the current Braintree fee terms.
- Airwallex: lists a free U.S. Explore plan and Grow at $12 per user monthly plus a team-size-based platform fee. Payment, FX, and transfer charges are additional. See Airwallex U.S. pricing.
Processing or MoR service
A flat rate covers defined transactions. An interchange-plus margin is only the processor’s addition to underlying costs. An MoR fee may bundle broader services for supported sales.
Platform and operating costs
Include subscriptions, Shopify third-party fees where applicable, FX, international surcharges, refunds, disputes, hardware, implementation, and reconciliation time.
Build a monthly estimate using payment volume, average ticket, card-present share, international share, payment-method mix, refunds, disputes, FX, subscriptions, hardware, and external-gateway fees. For interchange-plus, separate interchange and network pass-through from processor margin and fixed fees. For cross-border sales, keep transaction currency, settlement currency, conversion cost, and converted amount distinct. If public pricing does not resolve the comparison, ask each finalist to quote against the same transaction profile.
Check tax, checkout, and geographic responsibilities
Choose an MoR only after mapping each product and sales jurisdiction to the contractual seller, tax collection and remittance scope, refund owner, chargeback owner, and supplier obligations. Paddle describes an MoR model for applicable transactions, and its terms identify its reseller role and specified tax, refund, and chargeback responsibilities. That does not remove every seller accounting or regulatory obligation. Read Paddle’s offer alongside its legal terms.
If the store already runs on Shopify, compare Shopify Payments with an external provider using the complete cost stack. Shopify Payments is a commerce-platform payment option, not an MoR arrangement. Airwallex combines cross-border accounts, FX, transfers, payment acceptance, and billing. Its U.S. page advertises accounts that can collect and hold funds in more than 20 currencies, but eligibility, payment methods, settlement, and fees depend on the entity and country. Confirm the fit at Airwallex’s pricing page.
For every finalist, verify the legal entity and country it can serve, the customer methods and settlement currencies required, who handles refunds and disputes, and the terms governing underwriting and account review. A broad geographic claim is not confirmation that your entity, product, or transaction is eligible.
Map responsibility before price. If the provider is not the contractual seller for a transaction, do not assume its checkout or tax features transfer your seller obligations.
Design payment-event handling before automating it
A webhook delivery is a provider notification, not proof by itself that a payment is complete. Use the verified event and the provider’s payment state to control fulfillment or accounting. A rules-based workflow should decide whether a payment is captured, pending, denied, refunded, or disputed. AI is not needed for that decision. It may summarize an unstructured support case for a person, but it should not authorize fulfillment or change ledger state.
Use two records with distinct grains:
- Delivery record: one row for each received provider event notification, keyed by provider plus provider event ID. It records receipt, verification, payload provenance, and processing outcome.
- Payment-state record: one row for each provider payment or capture, keyed by the provider payment or capture identifier. It records the current reconciled state and may link to several delivery records, refunds, or reversals.
Keep provider event IDs separate from payment or capture IDs and order IDs. The same order can have multiple captures or refunds, and a provider can deliver the same event repeatedly. A proposed delivery record can contain provider, merchant_account_id, provider_event_id, provider_payment_id, order_id, event_type, payment_status, amount_minor_units, currency, settlement_currency, received_at, provider_created_at, raw_payload_hash, verification_status, reconciliation_status, processing_status, and downstream_record_id. This is an illustrative implementation model, not a vendor-published schema.
For example, an illustrative normalized delivery record might look like this:
{
"provider": "square",
"merchant_account_id": "merchant_example_17",
"provider_event_id": "evt_example_8042",
"provider_payment_id": "pay_example_3917",
"order_id": "order_example_206",
"event_type": "payment.updated",
"payment_status": "COMPLETED",
"amount_minor_units": 12500,
"currency": "USD",
"verification_status": "verified",
"reconciliation_status": "matched",
"processing_status": "accepted"
}
The sample represents one delivery row, not one payment summary. A separate payment-state row would identify the payment or capture and could be updated by several verified deliveries. A read-then-create check alone can race. Use a database-enforced unique key and transactional upsert whenever concurrent processing is possible.
Provider-specific event gates
| Provider | Trigger and state to inspect | Validation and destination | Exception owner |
|---|---|---|---|
| PayPal | Subscribed REST webhook for a capture or related order event. Inspect capture status. | Verify the notification, separate event and capture IDs, and fulfill only after completed capture. Send the accepted state to the order system. | Integration owner for verification or retries; finance or fulfillment for reconciliation. |
| Square | payment.created or payment.updated. Read the payment record and status. |
Do not equate payment creation with completion. Distinguish authorization, completion, cancellation, and refund before updating payment state. | Payments integration owner for API ambiguity; finance for amount, refund, or settlement mismatch. |
| Shopify | Configured order webhook for the selected app and API surface. Read the relevant current order or payment state. | Verify HMAC, scopes, API version, shop identity, and identifiers. Reconcile current state before writing to CRM or accounting. | Shopify app owner for signature, scope, or version failures; finance or operations for order mismatch. |
PayPal documents webhook registration, verification, event subscriptions, and repeated delivery attempts. A pending capture is not completion. See the PayPal REST webhook guide and verification and delivery documentation. Square documents payment.created and payment.updated events, but the payment status must be inspected before fulfillment. See the Square Payments API webhook reference. Shopify documents webhook topics, signature verification, access scopes, and API-version considerations. Confirm the exact app and API surface rather than generalizing specialized UCP order-webhook behavior to every implementation. See Shopify webhook documentation.
Use bounded parsing and deterministic checks: accept only expected event types and status values, verify that identifiers belong to the expected merchant account, compare amount and currency with the order, and prevent a refund or reversal from being overwritten by an older success event. A failed check must not write a successful payment state.
Zapier integration directory pages can show that an app connection exists, but they do not prove event semantics, field mappings, retries, idempotency, or accounting correctness. Verify the actual trigger, action, fields, permissions, and delivery behavior before relying on an automation. For integration planning, see our Zapier automation services.
Make the final selection with a short pilot
Test each finalist against representative cases from the actual business rather than only a successful card payment. Include a refund, dispute, international transaction, wallet or local method, subscription if relevant, and in-person payment if relevant. Reconcile gross amount, fees, refunds, net settlement, and currency against internal records. Measure support resolution, export completeness, and time required to operate the system during the pilot instead of assuming performance from a vendor comparison.
- Representative payment methods, channels, currencies, refunds, disputes, and settlement cases have been tested.
- Finance has reconciled gross, fees, refunds, net settlement, and currency against provider reports.
- The system of record is named for orders, payment state, accounting, customer data, and refunds.
- Required identifiers, exports, scopes, API versions, and webhook fields have been checked for the chosen application.
- Signature verification, database uniqueness, retry handling, and exception routing have been tested.
- A finance owner and technical owner have approved rollback criteria before write-back is enabled.
Stage the cutover. Keep the pilot limited, compare provider settlement reports with internal records, and expand only after finance and operations sign off. Define which system owns payment state and how an accepted payment, refund, reversal, or dispute updates external records before enabling write-back. For that operating design, see our CRM systems and workflow design.
