Wix Payments Error Messages
Cleaning up compliance error messaging for Wix Payments
Overview
Wix Payments is Wix’s in-house payment solution, but it relies on external payment partners such as Stripe, Adyen, and PayPal to process payments and payouts. Each provider uses its own backend compliance codes, and Wix maps those codes to user-facing messages shown when merchants need to fix an issue with their account. In this project, the goal was to overhaul a large, outdated set of compliance-related error messages so users could better understand what was wrong and what action to take.
Context
This work sat inside Wix Payments, where merchants depend on clear guidance to avoid delays in accepting payments or receiving payouts. Because the compliance rules and provider code sets change frequently, the existing message system had become inconsistent over time: some messages no longer matched the latest provider codes, some were too vague to help users act, and a few codes surfaced no message at all.
Scope
The project focused on auditing and rewriting the compliance error message system tied to Stripe, Adyen, and later PayPal integrations. It involved reviewing hundreds of existing code-to-message mappings, identifying gaps and outdated content, and designing a clearer, more scalable messaging approach for merchants encountering account verification or payout issues.
Problem
The core problem was that the existing error messaging system no longer reflected the real compliance states users were experiencing. Providers regularly introduced new codes or updated existing ones, while Wix’s user-facing messages were not always kept in sync. As a result, merchants could see instructions that were outdated, incomplete, unrelated to their actual issue, or in some cases a blank message area with no explanation at all.
This was not just a copy cleanup project. Inaccurate or unclear compliance messaging can delay a merchant’s ability to accept payments or receive payouts, increase frustration during a sensitive moment, and generate avoidable support tickets. In a fintech context, message quality directly affects trust, task completion, and operational efficiency. The scale of the project include hundreds or messages, far too large for a single screenshot.
My role
As UX Writer on Wix Payments, I took ownership of cleaning up the compliance messaging system. I initiated the project, aligned with the heads of Payments and Product, audited the existing code/message structure, collaborated with external provider representatives and internal Customer Support, and rewrote the messaging framework.
Team and collaboration
I worked with:
-
Heads of Payments and Product for alignment and prioritization.
-
Stripe and Adyen representatives to validate updated provider code lists.
-
Customer Support to identify the issues that caused the most friction for users.
-
Internal product partners responsible for implementation.
Constraints
This project had several real constraints:
-
Compliance rules and provider code systems changed frequently.
-
Different payment partners had different logic and levels of specificity.
-
The system already contained hundreds of legacy messages.
Proccess
1. Audit and mapping
The first step was pulling all existing compliance messages and backend codes from the Wix system. That made it possible to see the full scope of the problem, including outdated mappings, duplicate messages, gaps between provider codes and user-facing content, and codes with no usable message attached.
2. External and internal research
After building the internal inventory, I worked with Stripe and Adyen representatives to get the most up-to-date provider code lists and compare them against the Wix system. I also partnered with Customer Support to understand which compliance issues created the most confusion and friction for merchants.
3. Message architecture
Once the mapping was complete, I reviewed where messages could be consolidated and where they needed to be split into more specific variants. The goal was to reduce unnecessary duplication while increasing the usefulness of messages for users facing different types of compliance problems.
4. Rewrite and guidance improvement
I then rewrote the full set of messages to make them more accurate, more actionable, and more specific. Where providers could identify a more precise issue, such as a mismatch in a first name or last name, the new messaging passed that detail on to the user. I also added links to supporting Wix resources so users could better understand requirements before retrying actions such as ID uploads.
Solution
The end solution was a cleaned-up and more maintainable compliance messaging system that:
-
Mapped provider codes to more accurate user-facing messages.
-
Removed outdated or misleading instructions.
-
Fixed blank-message cases where users were seeing no guidance at all.
-
Increased specificity so users could understand the exact issue and next step.
-
Added educational support links to reduce repeated mistakes.
Outcome
The full rollout is still in progress, so final results are not yet available. Even so, the project already resolved critical gaps, including codes that triggered blank states with no message shown to users. The expected impact is clearer guidance for merchants, fewer delays in payment acceptance and payouts, and lower support load caused by confusing or incomplete compliance messaging.
Reflection
This project reinforced how important content governance is in fast-moving fintech systems. A message library tied to evolving backend logic cannot be treated as static copy; it needs regular auditing, stronger mapping discipline, and closer collaboration between providers, product teams, and support.