UAT·Ops About UAT-Ops

Payment gateways for Wix

Gateway pages

About Wix

Wix is a hosted website builder that bundles its own commerce products (Stores, Bookings, Restaurants, Events and Pricing Plans) behind a single checkout. Small businesses and agencies use it because the site, the catalogue and the payment step are all run by Wix; there is nothing to host and no theme code to maintain.

Payments come in two shapes. Wix Payments is Wix's own processor, available in 15 countries with published per-country card fees (2.9% + 0.30 USD in the US, 1.9% + 0.30 EUR in the EU). Everywhere else, or by choice, a merchant connects one of the 100+ third-party providers Wix lists per country: PayPal, Stripe, Square, Braintree, Razorpay, Mercado Pago and others. Only one provider can process cards on a site, and Wix does not accept a provider's sandbox credentials, so a live account is needed to connect.

For an integrator the relevant surface is the Payment Service Provider service plugin. A provider that is not already on the list onboards with Wix, then exposes Connect Account, Create Transaction and Refund Transaction endpoints (Capture and Void are optional) and posts status webhooks back to Wix with a short-lived OAuth token. Wix signs each outbound request with a JWT digest of the body and expects transaction and refund calls to be idempotent.

Checkout itself is not extensible in code. The dashboard controls fields, policies, fees and capture mode; design and required fields are fixed, and the only programmatic hook at the payment step is the Payment Settings plugin, which can request 3DS where the provider supports it.

Testing happens on free development sites created from the app dashboard, which include Wix Payments capabilities. On a live merchant site a completed test order is charged unless an offline payment method is enabled.

How payments work on Wix

Built-in payments
Wix Payments, Wix's own processor, available in 15 countries (US, Canada, UK, Brazil, Switzerland and ten EU states). Card fees are published per country, e.g. 2.9% + 0.30 USD in the US and 1.9% + 0.30 EUR in the EU for non-Amex cards. Accepting any payment requires a Premium or Studio plan that supports payments.1
Third-party gateways
Merchants connect one of 100+ third-party providers from the site dashboard (the country-specific help-center list names PayPal, Stripe, Square, Braintree, Razorpay, Mercado Pago, Paystack, Klarna, Afterpay and others); a site can connect only one provider for card processing, while several alternative-method providers (PayPal, crypto, BNPL) may coexist. Wix's published fee schedule covers Wix Payments only; for third-party providers Wix documents that card fees vary by provider and payouts are handled by the provider. Wix does not accept a provider's test/sandbox credentials when connecting. Providers not already on the list integrate by onboarding with Wix's business-development team and implementing the Payment Service Provider service plugin (Connect Account, Create Transaction, Refund Transaction, optional Capture/Void) plus webhooks back to Wix; a site owner can also add an unsupported provider to a single site with the Velo Payment Provider service plugin.2
Checkout extensibility
Checkout is Wix-hosted, and cannot be opened in the visual editor at all. From Checkout Settings, merchants can add custom form fields with conditional rules, edit the checkout header's own logo and background colour, add policies and consent checkboxes, extra fees, gift-card and saved-card toggles, authorization/capture mode, and cart validation rules. What that settings panel cannot touch is the page as a whole: its overall background, fonts, colour scheme and button design are fixed, and the email, first name, last name and delivery fields cannot be removed. Apps can influence the payment step through the eCommerce Payment Settings service plugin (for example forcing 3DS on a transaction), which only takes effect where the connected provider has implemented that setting.3

What we checked

  • Wix Payments is Wix's own payment solution, accepting debit/credit cards, Apple Pay, Google Pay, PayPal, Tap to Pay and other methods, and operates in 15 countries: Austria, Belgium, Brazil, Canada, Finland, Germany, Ireland, Italy, Lithuania, Netherlands, Portugal, Spain, Switzerland, the UK and the US.1
  • Wix Payments card fees (excluding American Express) are 2.9% + 0.30 USD in the United States, 1.9% + 0.30 EUR in EU countries, 2.1% + 0.20 GBP in the United Kingdom, 2.9% + 0.30 CAD in Canada and 2.3% + 0.30 CHF in Switzerland; Amex rates are higher.4
  • A site must be on a Premium or Studio plan that supports payments before it can accept payments; alongside Wix Payments, Wix has partnered with more than 70 other providers worldwide, with the available set depending on the site's country.2
  • Third-party providers are connected from Accept Payments in the site dashboard by clicking Connect next to the provider and entering existing account credentials or creating an account; Wix states that 100+ payment providers are available.5
  • The country-by-country provider list includes PayPal, Stripe, Square, Braintree, Razorpay, Mercado Pago, PagBank, Paystack, iyzico, Klarna, Afterpay and crypto processors; a site cannot connect more than one provider for credit-card processing, though several alternative-method providers can be connected at once.6
  • Wix does not accept test or temporary credentials when connecting a site to a payment provider; sites connected with such credentials must disconnect and reconnect with live credentials. Support for test credentials is an open feature request.7
  • Payouts for any provider other than Wix Payments (PayPal, Stripe and so on) are managed by that provider, and merchants are directed to the provider for payout questions.8
  • The Payment Service Provider service plugin lets a PSP integrate with Wix so its service becomes available to applicable merchant sites, supporting cards, e-wallets, local methods, hosted third-party pages and refunds; a PSP must first onboard with Wix's business development team via an application form.9
  • A PSP integration implements three POST JSON endpoints (Connect Account, Create Transaction, Refund Transaction) plus optional Capture and Void endpoints for providers with full auth-capture enabled, and must send webhooks back to Wix to confirm payment and refund events; endpoint URLs are configured in the Wix Developers Center.10
  • Requests Wix sends to a PSP carry a Digest header holding a JWT whose payload contains the SHA-256 of the raw request body; the PSP verifies the signature with its app's public key, checks the exp claim and compares the body digest before acting.11
  • PSP webhooks are posted to https://www.wixapis.com/payments/v1/provider-platform-events with a client-credentials access token scoped to CASHIER.GET_ACCESS, obtained fresh for every webhook from https://www.wixapis.com/oauth/access; any non-200 response means the event was not received and should be retried.12
  • Wix expects Create Transaction and Refund Transaction to be idempotent so that interrupted calls can be safely retried.13
  • The SPI's payment-method table names creditCard, payPal, applePay, googlePay, klarna, afterpay, iDeal, sepa, sofort, giropay, bancontact, alipay, weChatPay and around 40 other local methods; the creditCard entry notes that fees vary between payment service providers.14
  • Wix publishes an MIT-licensed Node.js sample payment-provider server (server.mjs, jwt-validation.mjs, submit-event.mjs) as a reference implementation for the Payment Provider SPI.15
  • Site owners can add a provider Wix does not already support to their own site with the Velo Payment Provider service plugin by implementing getConfig, connectAccount, createTransaction and refundTransaction in site code.16
  • The checkout page cannot be customized from the editor; the dashboard controls custom fields with conditional rules, a header logo and colour, policies and consent checkboxes, additional fees, gift-card and saved-card options, authorization/capture and cart validation rules, while email, first name, last name and delivery fields cannot be removed.3
  • Customizing the background, fonts, colours or button design of the checkout page is not currently possible and is tracked as an open feature request covering Stores, Bookings and Restaurants Orders.17
  • An app can use the eCommerce Payment Settings service plugin to apply settings such as requiring 3D Secure during payment, configured with a deploymentUri and a fallback value if the call fails; whether a setting takes effect depends on what the connected provider implemented in its Wix integration.18
  • Wix passes payment requests to the connected third-party provider and does not control the payment lifecycle; whether 3DS is applied is up to the provider, and merchants are told to confirm 3DS support with the provider directly.19
  • App developers can create free development sites from the app dashboard that include full editor access, Premium and Wix Payments capabilities and Wix business solutions, choosing Stores, Restaurants, Events, Services or Blank templates across the Classic, Studio and Harmony editors.20
  • Checkout can be previewed in the editor up to the payment step on a Premium or Studio site with a connected provider; a completed test order on a live site is charged unless a manual payment method is enabled first, and Bookings checkout cannot be previewed.21
  • Wix app webhooks deliver a signed JWT verified with the app's public key, time out after 1250 ms without a 200 response, and are retried up to 12 times on a schedule running from 1 minute to 12 hours; duplicates and out-of-order delivery are possible and apps should store processed event IDs.22
  • The Wix App Market lists third-party and Wix-built apps across categories including eCommerce, with ratings, pricing and verification badges.23

Sources

  1. https://support.wix.com/en/article/about-wix-paymentsofficial documentation · checked 2026-09-11
  2. https://support.wix.com/en/article/accepting-payments-an-overviewofficial documentation · checked 2026-09-11
  3. https://support.wix.com/en/article/wix-stores-customizing-the-checkout-pageofficial documentation · checked 2026-09-11
  4. https://support.wix.com/en/article/wix-payments-transaction-feesofficial documentation · checked 2026-09-11
  5. https://support.wix.com/en/article/connecting-a-payment-providerofficial documentation · checked 2026-09-11
  6. https://support.wix.com/en/article/available-payment-providers-in-your-countryofficial documentation · checked 2026-09-11
  7. https://support.wix.com/en/article/request-using-test-temporary-credentials-to-connect-a-payment-providerofficial documentation · checked 2026-09-11
  8. https://support.wix.com/en/article/receiving-payouts-from-third-party-payment-providersofficial documentation · checked 2026-09-11
  9. https://dev.wix.com/docs/api-reference/business-management/payments/payment-service-provider-service-plugin/introduction.mdofficial documentation · checked 2026-09-11
  10. https://dev.wix.com/docs/api-reference/business-management/payments/payment-service-provider-service-plugin/implementation-overview.mdofficial documentation · checked 2026-09-11
  11. https://dev.wix.com/docs/api-reference/business-management/payments/payment-service-provider-service-plugin/validate-endpoint-requests.mdofficial documentation · checked 2026-09-11
  12. https://dev.wix.com/docs/api-reference/business-management/payments/payment-service-provider-service-plugin/webhooks.mdofficial documentation · checked 2026-09-11
  13. https://dev.wix.com/docs/api-reference/business-management/payments/payment-service-provider-service-plugin/idempotency.mdofficial documentation · checked 2026-09-11
  14. https://dev.wix.com/docs/api-reference/business-management/payments/payment-service-provider-service-plugin/payment-methods.mdofficial documentation · checked 2026-09-11
  15. https://github.com/wix-incubator/payment-spi-samplecode repository · checked 2026-09-11
  16. https://dev.wix.com/docs/velo/api-reference/wix-payment/service-plugin-spi/wix-payments/payment-provider/introduction.mdofficial documentation · checked 2026-09-11
  17. https://support.wix.com/en/article/request-customizing-the-design-of-the-checkout-pageofficial documentation · checked 2026-09-11
  18. https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/payments/payment-settings/payment-settings-integration-service-plugin/introduction.mdofficial documentation · checked 2026-09-11
  19. https://support.wix.com/en/article/about-3d-secure-3ds-payments-with-third-party-payment-providersofficial documentation · checked 2026-09-11
  20. https://dev.wix.com/docs/build-apps/build-your-app/testing/how-to-test-your-app-on-a-free-premium-development-site.mdofficial documentation · checked 2026-09-11
  21. https://support.wix.com/en/article/previewing-the-checkout-process-1420066official documentation · checked 2026-09-11
  22. https://dev.wix.com/docs/build-apps/develop-your-app/api-integrations/events-and-webhooks/about-webhooks.mdofficial documentation · checked 2026-09-11
  23. https://www.wix.com/app-marketmarketplace listing · checked 2026-09-11

Last verified 2026-09-12 · Reviewed by a person 2026-09-25

Integration capabilities, requirements, pricing, availability, and vendor policies may change over time. UAT-Ops documents information based on the authoritative sources and testing available at the time of review.

Where newer information, testing, or vendor documentation materially changes a published claim, UAT-Ops may revise the page to reflect the most current verified information. Readers should confirm time-sensitive requirements with the relevant vendor before making production or purchasing decisions.