OKX Pay: Making Digital Payments Feel Familiar

Designing clear, trustworthy peer-to-peer and merchant payment experiences across multiple markets.

Role

Content design (co-lead)

Partners

Product, Design, Engineering, Legal/Compliance, Localization

Timeline

12+ months (conception to launch)

Scale

Multi-market P2P and merchant payments

OKX Pay: Making Digital Payments Feel Familiar

Designing clear, trustworthy peer-to-peer and merchant payment experiences across multiple markets.

Role

Content design (co-lead)

Partners

Product, Design, Engineering, Legal/Compliance, Localization

Timeline

12+ months (conception to launch)

Scale

Multi-market P2P and merchant payments

OKX Pay: Making Digital Payments Feel Familiar

Designing clear, trustworthy peer-to-peer and merchant payment experiences across multiple markets.

Role

Content design (co-lead)

Partners

Product, Design, Engineering, Legal/Compliance, Localization

Timeline

12+ months (conception to launch)

Scale

Multi-market P2P and merchant payments

1: Making Complex Payments Feel Familiar

People expect sending money or paying at a checkout counter to feel immediate, familiar, and trustworthy. OKX Pay aimed to bring that same simplicity to digital assets through peer-to-peer transfers and merchant payments across multiple markets. The challenge was to make complex transactions understandable without exposing unnecessary technical details or hiding information users needed to act with confidence.


I was one of two content designers involved from early planning through launch. My senior partner drove much of the initial content strategy, while I contributed to core flow iterations, errors and edge cases, localization, and production readiness. During her extended leaves, I became the primary content design contact, collaborating directly with product and design stakeholders to keep the project moving.

2: Singapore Scan to Pay (C2B Point-of-Sale)

2: Singapore Scan to Pay (C2B Point-of-Sale)

Paying at a physical checkout is different from sending money on your own time. When someone is waiting in line, they need to understand what they're paying, where the money is coming from, and whether the transaction was successful, without having to interpret the technical mechanics happening behind the scenes.


For the Scan to Pay feature in Singapore, I focused on making the payment content concise and easy to understand at the point of sale. By prioritizing details like the payment amount, source balance, and merchant, we helped make spending digital assets feel more like a familiar mobile payment experience while preserving the information users needed to transact with confidence.

3: Global Peer-to-Peer Transfers (US, EU and BR)

Sending money to another person should feel straightforward, even when the underlying transaction uses unfamiliar technology. OKX Pay supported familiar ways to find recipients, including phone numbers, email addresses, and QR codes, rather than requiring users to interact directly with complex blockchain addresses.

My content work helped make the transfer experience easier to follow, from identifying the recipient and confirming an amount to understanding transaction status and completion. More technical details remained available in transaction history for users who needed them. The goal was to make everyday transfers feel intuitive without obscuring important information about where users' money was going.

4: Content Iterations, Edge Cases and Rationale

Beyond the core payment flows, I owned substantial error and edge-case content. The goal wasn't simply to replace technical language with friendlier words, but to help users understand what went wrong and what they could do next. These examples show how clearer, more actionable messaging improved common failure and recovery scenarios.

Close-up snapshot of a mobile viewport scanner tracking a generic web asset barcode, generating a bold warning card directly over the image target window.
High-contrast screen capture showing an unrecognized user identifier string generating an error magnifying glass and structured formatting guidance strings.
Close-up snapshot of a mobile viewport scanner tracking a generic web asset barcode, generating a bold warning card directly over the image target window.
High-contrast screen capture showing an unrecognized user identifier string generating an error magnifying glass and structured formatting guidance strings.

Surface/Content

Illustrative Technical Copy

Final Shipped Copy

Rationale

Payment input/funds validation

Surface/Context:


Payment input/funds validation

Error: Balance Insufficient for Transaction Value

Illustrative Technical Copy:


Error: Balance Insufficient for Transaction Value

You don't have enough balance to pay

Final Shipped Copy:

You don't have enough balance to pay

Replaced technical error language with a direct explanation of the problem, helping users understand why the payment couldn't proceed and what needed to change before trying again.

Rationale:

Replaced technical error language with a direct explanation of the problem, helping users understand why the payment couldn't proceed and what needed to change before trying again.

Surface/Context:


Invalid QR code scanned in viewfinder

Illustrative Technical Copy:


Error: Invalid Matrix Address Source Unmapped

Final Shipped Copy:

Scan a valid OKX Pay QR code.

Rationale:

Instead of exposing an obscure scanning error, the message tells users which type of QR code is supported, making the problem understandable and the next action clear.

Surface/Context:


Recipient search/lookup

Illustrative Technical Copy:


No Results Found

Final Shipped Copy:

Check the contact info


Make sure the phone number or email address you entered is correct.

Rationale:

Rather than leaving users at a generic "No results found" message, the empty state provides a clear next step: checking the phone number or email address they entered.

Invalid QR code scanned in viewfinder

Error: Invalid Matrix Address Source Unmapped

Scan a valid OKX Pay QR code.

Instead of exposing an obscure scanning error, the message tells users which type of QR code is supported, making the problem understandable and the next action clear.

Recipient search/lookup

No Results Found

Check the contact info


Make sure the phone number or email address you entered is correct.

Rather than leaving users at a generic "No results found" message, the empty state provides a clear next step: checking the phone number or email address they entered.

5: Localization and Production Quality

As Pay expanded across markets, maintaining consistency through localization, implementation, and QA became increasingly important. I supported content-key management and localization handoffs while reviewing iOS and Android staging builds to identify issues before release.


Through testing of text scaling, regional content, and error states, I identified usability, content, and interaction issues, including launch blockers, and worked with cross-functional partners to address them. I also co-authored FAQs and supporting user guidance to help customers understand the product and recover from common problems.

6: Takeaway

Designing for simplicity doesn't mean stripping information away. Pay reinforced the importance of surfacing the information users need at the moment they need it, and treating terminology, errors, localization, QA, and supporting content as parts of one cohesive trust system.

1: Making Complex Payments Feel Familiar

People expect sending money or paying at a checkout counter to feel immediate, familiar, and trustworthy. OKX Pay aimed to bring that same simplicity to digital assets through peer-to-peer transfers and merchant payments across multiple markets. The challenge was to make complex transactions understandable without exposing unnecessary technical details or hiding information users needed to act with confidence.


I was one of two content designers involved from early planning through launch. My senior partner drove much of the initial content strategy, while I contributed to core flow iterations, errors and edge cases, localization, and production readiness. During her extended leaves, I became the primary content design contact, collaborating directly with product and design stakeholders to keep the project moving.

2: Singapore Scan to Pay (C2B Point-of-Sale)

Paying at a physical checkout is different from sending money on your own time. When someone is waiting in line, they need to understand what they're paying, where the money is coming from, and whether the transaction was successful, without having to interpret the technical mechanics happening behind the scenes.

For the Scan to Pay feature in Singapore, I focused on making the payment content concise and easy to understand at the point of sale. By prioritizing details like the payment amount, source balance, and merchant, we helped make spending digital assets feel more like a familiar mobile payment experience while preserving the information users needed to transact with confidence.

3: Global Peer-to-Peer Transfers (US, EU and BR)

Sending money to another person should feel straightforward, even when the underlying transaction uses unfamiliar technology. OKX Pay supported familiar ways to find recipients, including phone numbers, email addresses, and QR codes, rather than requiring users to interact directly with complex blockchain addresses.

My content work helped make the transfer experience easier to follow, from identifying the recipient and confirming an amount to understanding transaction status and completion. More technical details remained available in transaction history for users who needed them. The goal was to make everyday transfers feel intuitive without obscuring important information about where users' money was going.

4: Content Iterations and Rationale

Beyond the core payment flows, I owned substantial error and edge-case content. The goal wasn't simply to replace technical language with friendlier words, but to help users understand what went wrong and what they could do next. These examples show how clearer, more actionable messaging improved common failure and recovery scenarios.

Surface/Context:


Payment input/funds validation

Illustrative Technical Copy:


Error: Balance Insufficient for Transaction Value

Final Shipped Copy:

You don't have enough balance to pay

Rationale:

Replaced technical error language with a direct explanation of the problem, helping users understand why the payment couldn't proceed and what needed to change before trying again.

Surface/Context:


Invalid QR code scanned in viewfinder

Illustrative Technical Copy:


Error: Invalid Matrix Address Source Unmapped

Final Shipped Copy:

Scan a valid OKX Pay QR code.

Rationale:

Instead of exposing an obscure scanning error, the message tells users which type of QR code is supported, making the problem understandable and the next action clear.

Surface/Context:


Recipient search/lookup

Illustrative Technical Copy:


No Results Found

Final Shipped Copy:

Check the contact info


Make sure the phone number or email address you entered is correct.

Rationale:

Rather than leaving users at a generic "No results found" message, the empty state provides a clear next step: checking the phone number or email address they entered.

Close-up snapshot of a mobile viewport scanner tracking a generic web asset barcode, generating a bold warning card directly over the image target window.
High-contrast screen capture showing an unrecognized user identifier string generating an error magnifying glass and structured formatting guidance strings.

5: Localization and Production Quality

As Pay expanded across markets, maintaining consistency through localization, implementation, and QA became increasingly important. I supported content-key management and localization handoffs while reviewing iOS and Android staging builds to identify issues before release.


Through testing of text scaling, regional content, and error states, I identified usability, content, and interaction issues, including launch blockers, and worked with cross-functional partners to address them. I also co-authored FAQs and supporting user guidance to help customers understand the product and recover from common problems.

6: Takeaway

Designing for simplicity doesn't mean stripping information away. Pay reinforced the importance of surfacing the information users need at the moment they need it, and treating terminology, errors, localization, QA, and supporting content as parts of one cohesive trust system.