Are Existing KYC Processes Enough for Stablecoin Payments and Digital Asset Wallets?

Are Existing KYC Processes Enough for Stablecoin Payments and Digital Asset Wallets?

So far, we have explored when KYC is required in financial services, identity document verification, identity fraud prevention, KYC for international users, how to evaluate an existing eKYC solution, and the operational costs associated with KYC.

This time, let’s consider a slightly different scenario.

What happens when a company already offering payment, remittance, or prepaid services expands into new financial services such as stablecoin payments or digital asset wallets?

If the company already has KYC processes in place, it may seem reasonable to simply apply the same process to the new service.

But as the scope of a service expands, so can the range of users, transactions, and risks that need to be assessed.

That is why companies preparing to launch new financial services need to go one step beyond asking:

“Do we have KYC in place?” Instead, they should ask:

“Is our current KYC framework sufficient for the new service?”

That is where the review should begin.

Why Revisit KYC If You Already Have It?

Imagine a company that primarily provides payment services to domestic users.

It already verifies users during onboarding and performs identity document verification when necessary.

Now imagine that the company adds stablecoin-based payment or remittance capabilities and begins serving users in multiple countries.

The scope of its KYC requirements can change significantly.

Previously, the primary challenge may have been verifying the identities of domestic users. Now, the company may need to process users from a much wider range of countries.

A KYC process that once relied primarily on a one-time verification during onboarding may also need to account for situations where users must be verified again based on transaction activity or changes in risk.

Another important consideration is how identity verification results connect with subsequent risk management processes such as AML screening, sanctions screening, and PEP checks.

In other words, launching a new financial service does not necessarily mean building an entirely new KYC process.

Instead, companies need to determine whether their existing KYC framework can scale to support the users and risks introduced by the expanded service.

Change #1: As Your Service Becomes Global, Your KYC Coverage Must Expand

Services involving stablecoins and digital assets often need to accommodate global users or cross-border transactions.

One of the first challenges companies may encounter is identity document coverage.

A KYC process designed primarily for domestic users may only need to support a relatively limited range of identity documents.

Once international users begin joining the service, however, the company may need to process passports, national ID cards, driver’s licenses, and other identity documents from different countries.

Before applying an existing KYC process to a new service, companies should therefore ask:

Can our current KYC process verify the identity documents our future users will actually submit?

Simply looking at the number of supported countries is not enough.

Companies should also evaluate whether their KYC solution can extract the required information from those documents, identify potential signs of document forgery or tampering, and verify global identity documents to a level suitable for actual KYC operations.

Ultimately, expanding a financial service globally is not only about expanding product capabilities.

It also means expanding KYC coverage.

Change #2: Determine Whether KYC Should End After Onboarding

If your existing KYC process is primarily focused on onboarding, there is another important question to consider:

How long should information verified during onboarding continue to be trusted?

Users continue interacting with a service long after they create an account.

Their level of activity may increase, transaction volumes may change, and important information associated with their account may be updated.

Instead of treating KYC as a one-time onboarding requirement, companies should consider whether there are specific points throughout the customer journey where additional verification may be necessary.

Depending on the company’s policies, this could include situations where:

• Transaction volumes or service usage exceed a certain threshold

• Previously verified user information changes

• Significant changes are made to an account

• The user’s identity needs to be reconfirmed after the initial verification

• Risk signals indicate that additional review is necessary

The goal is not to require users to complete full identity document verification every time they make a transaction.

Rather, companies should establish reliable identity information during the initial KYC process and then apply the appropriate level of re-verification based on risk and context.

Change #3: Are KYC and AML Operating Separately?

As companies prepare to launch new financial services, KYC is often discussed alongside AML.

In practice, however, KYC and AML processes may still operate as separate workflows.

A company may use one system to verify a user’s identity and another to screen for sanctions, PEPs, or other risk indicators. This can leave operations teams responsible for reviewing multiple results and making the final decision manually.

The key issue is therefore not simply whether each capability exists.

What matters is whether those verification results can be connected into a unified view of user risk.

For example, a user may successfully complete identity verification but still require additional review based on subsequent AML screening.

When designing KYC for a new financial service, companies should consider whether they can connect the process into a single workflow:

Identity Verification
→ AML Screening
→ Risk Assessment
→ Additional Verification When Required

If KYC answers the question “Who is this person?”, AML and risk management can help determine “How should this user be managed?”

Change #4: Not Every User Needs the Same Level of Verification

As new services are introduced, the number of potential risk factors can increase.

But that does not necessarily mean every user should go through the strongest possible level of verification.

Repeatedly requiring complex verification from legitimate users can create unnecessary friction and negatively affect the overall user experience.

A more important question is whether the level of verification can be adjusted based on the user’s circumstances and risk profile.

For example, regular users may complete standard KYC and begin using the service, while users associated with additional risk signals or higher-risk activities may be asked to complete further verification.

A simplified flow might look like this:

Standard User

Basic KYC → Service Access

User Requiring Additional Verification

Basic KYC → Risk Signal → Additional Verification → Service Access or Review

The goal of KYC for new financial services is therefore not simply to add more verification steps.

It is to build a structure that applies the appropriate level of verification to the users who actually require it.

User Risk Can Change Even After KYC Is Complete

There is another factor to consider.

A user who presented no issues during onboarding may not always remain at the same level of risk.

User information may change. Transaction patterns and volumes may evolve. New information relevant to AML screening may also emerge.

For this reason, KYC for new financial services may need to evolve beyond a simple:

Onboarding → KYC Complete → End

Instead, companies may need to consider the user’s entire lifecycle:

Onboarding
→ Verification
→ Screening
→ Risk Assessment
→ Re-verification

In this model, KYC is no longer simply a verification step users must pass during onboarding.

It becomes part of the foundation for managing user trust and risk throughout the customer lifecycle.

What Really Changes Is the KYC Framework, Not Just the Verification Technology

As we have seen, preparing for stablecoin payments or digital asset wallets does not necessarily require an entirely different identity verification technology.

The fundamentals of KYC remain important: verifying identity documents and confirming that the person using the service is the legitimate user.

What changes is the scope of the processes that KYC needs to connect with.

Previously, the process may have looked like:

Onboarding
→ Identity Document Verification
→ Complete

For new financial services, companies may need to consider a broader operational framework:

Onboarding
→ Identity Verification
→ AML Screening
→ Risk Assessment
→ Additional Verification
→ Ongoing Reassessment

Before adding new features one by one, companies preparing to launch new financial services should first ask:

Can our current KYC process support global users?

Are KYC and AML results connected into a unified risk assessment process?

Can additional verification be triggered when a user’s risk level increases?

Can existing users be re-verified when necessary?

If the answers to these questions are currently spread across multiple systems and manual processes, operations may become increasingly complex as new financial services are added.

For New Financial Services, KYC Should Work as One Connected Flow

ARGOS supports global identity verification through ID Check and provides an environment where identity verification can be connected with user risk checks such as AML screening, sanctions screening, and PEP screening when required.

The goal is not simply to add more individual verification features.

What matters is creating a unified workflow based on your service policies: who needs to be verified, when additional verification should be required, and how the resulting information should be managed.

If you are preparing to launch services such as stablecoin payments, digital asset wallets, or global remittance, review your existing KYC framework before simply applying it to the new service.

The first question should be whether your current verification structure can scale to accommodate the new users, transactions, and risks your service will introduce.

From eKYC Implementation to Operations: What Should You Actually Check?

Across the first seven articles in this series, we have explored when KYC is required, identity document verification, identity fraud prevention, KYC for international users, how to evaluate existing eKYC solutions, KYC operational costs, and now KYC for emerging financial services.

In the eighth and final article, we will bring everything together and outline the key requirements companies should review when implementing eKYC for the first time or upgrading their existing KYC environment.