DIDx
didx:proxy

IDENTITY DIRECTORY INFRASTRUCTURE

Connect through Verified Identity.

didx:proxy is a trusted addressing, consent, and routing layer that lets people and businesses be discovered, verified, and connected - without exposing sensitive details.

It works for money, communication, access, and any interaction where trust matters.

Think of it as DNS for money. Just as the Domain Name System resolves human-readable names to IP addresses, didx:proxy resolves verified identity handles to financial endpoints - compliant, fraud-resistant, and ready to work with any payment rail.

Book a demo

What is didx:proxy?

A Trusted Address Book for the Digital Economy.

Every interaction starts with the same hidden question: Who is on the other side, and can I trust them?

Today, systems answer this with fragile identifiers - account numbers, wallet addresses, phone numbers, emails. They're hard to use, easy to get wrong, and increasingly exploited by fraud.

These identifiers say where to send something, but not who you're dealing with, whether they're legitimate, or whether the interaction should even be allowed.

didx:proxy introduces a different model. It's a verified addressing layer where human-readable handles resolve to trusted endpoints, governed by identity, credentials, and consent.

You don't exchange raw details. You resolve trust.

For Your Business:

Simpler onboarding. Safer, compliant, and fraud-resistant payments. Fewer data-entry errors. A cleaner way to identify users across channels.

For Your Customers:

Handles they control - one or many - to use across apps, platforms, and services, keeping private details private.

Flow from Request for Verification to @nandi, didx Policy, then Unapproved Info or Approved Info

The Core Idea

Addressing is the Missing Layer of Trust.

The internet solved naming for machines with DNS. Finance, commerce, and digital services still rely on raw identifiers.

didx:proxy acts as a trust-aware identity resolution layer.

A handle like @nandi or @acme.pay doesn't point directly to data. It points to policy.

What gets returned depends on who is asking, why they're asking, and what credentials they hold.

TWO WAYS TO USE IT

What Problem Does This Solve?

For Businesses:

You need to know who you're interacting with before value moves, access is granted, or communication is established. Raw identifiers don't give you that certainty. They create fraud, errors, and compliance exposure.

For People:

Sharing details feels risky. Once an account number or address leaks, control is gone. People want a simple way to be reachable without being exposed.

How didx:proxy Works

Simple on the Surface.
Deeply Verified Underneath.

It's More Than Money

Money is Just One Type of Endpoint.

didx:proxy works wherever trust and routing intersect.

Financial

Route to bank accounts, wallets, stablecoins, cards, or future rails.

Business

Resolve verified company identity, registration, or authorised representatives.

Platforms

Identify users across products without duplicating onboarding.

Communication

Share verified contact endpoints without exposing raw details.

Access and Permissions

Prove authority before granting access to systems, assets, or services.

What Can a Handle Link To?

Verified
Endpoints for
Any Interaction

Proxy handles can map to verified identity information, payment endpoints, communication channels, or credentials - all permissioned and user-controlled.

  • Verified identity credentials
  • Bank account or payment details
  • Cryptocurrency wallet addresses
  • Contact information
  • Business registration
  • Professional certifications
  • Communication endpoints
Smartphone showing didx:proxy handle linking to Payment Details, Registration, and Contact Info endpoints

RESULT

A Better Mental Model

Not a payment alias. Not a username. Not a wallet address.

A trusted contact list for the digital economy.

You don't need to know everything about the other party. You only need to know enough to trust the interaction.

Person using a stylus with a tablet, focused on their work

Use Cases

Built for Trusted, High-Volume Financial Interactions

Banks & Fintech (Payments)

Alias-based payments that work with any payment rail. Replace account numbers with secure, verified handles - safer, simpler, more accurate.

Banks & Fintech (Onboarding)

Use proxy handles to identify customers across products without repeating KYC details.

Crypto & Digital Assets

Replace complex wallet addresses with verified handles. Reduce errors. Enable compliant, identity-bound transfers.

Marketplaces & Platforms

Let buyers, sellers, and gig workers interact using handles instead of exposing personal info.

Why didx:proxy?

Trust that Gets More Valuable with Time

Trust First

Every handle is bound to verified identity.

Consent by Design

Nothing resolves without explicit permission.

Policy-Driven

Different contexts return different answers.

Interoperable

Works with existing payment rails, identity systems, and platforms.

Future-Ready

CBDCs, stablecoins, instant payments, and systems not yet invented.

"We built didx:proxy because we saw where the world was going: identity and finance converging. This is the addressing layer that makes that convergence possible - secure, consented, and global."

Lohan Spies

Founder, DIDx

Company logo

QUESTIONS

FAQs

GET STARTED

Ready to Simplify Trusted Interactions?

See how didx:proxy can replace scattered details with verified identity handles your users can share anywhere.

Book a Demo