Know the counterparty behind the transfer

Connect a counterparty's wallets, bank accounts and documents. Assess each address against your risk policy and keep Travel Rule information and verification evidence with the transfer.

Counterparty verification

A name, an address and a transfer answer different questions

Your team needs to establish who the party is, whether the address meets policy and whether the required transfer information has been collected and exchanged. Range connects those records while keeping the evidence for each check identifiable.

Counterparty identity

Give the party one record across wallets and bank accounts

Create a directory of vendors, customers, investors, partners and exchanges. Attach their identifiers and supporting documents so finance and compliance work from the same party record.

  • Multiple addresses

    Keep labeled onchain addresses across networks on one party.

  • Bank identifiers

    Record bank accounts alongside the party's wallet addresses.

  • Supporting documents

    Attach KYC, KYB and contracts to the counterparty record.

  • Live activity

    Review sent and received activity with amounts and transaction links.

Counterparty management dashboard with connected organizations

What the record holds

The details your team otherwise searches for

Party type

Vendor, customer, investor, partner, exchange or other.

Wallet identifiers

Labeled addresses with their networks.

Bank account details

Bank, account type, currency and masked identifiers.

KYC, KYB and contracts

Supporting files kept with the party.

Transaction activity

Sent and received amounts linked to source transactions.

A record for your systems

Manage the same counterparty identifiers through the API.

Address risk

See the exposure behind a counterparty's wallet

Screen each address to see its attribution, flagged sent and received volume and suspicious behavior. Drill into the counterparties and categories behind the result.

  • Material exposure

    Review flagged shares, dollar amounts and counterparty counts.

  • The parties behind the flow

    Inspect labeled counterparties, their categories and net flows.

  • Exposure by category

    Review sanctions, fraud, phishing and other flagged categories.

  • Findings and history

    Open signal evidence and previous screens for that address.

Risk policy

Assess addresses against your thresholds

The directory establishes the party record. Address screening applies your risk policy to each wallet.

Category volumes can overlap when a counterparty matches several categories. They should not be added together as a unique exposure total.

Travel Rule

Keep Travel Rule evidence with the transfer

Range collects originator and beneficiary information, identifies the receiving VASP and routes the exchange through integrated VASP network providers.

VASP information exchange

Pair the transfer with the required message and acknowledgment.

Self-hosted wallet verification

Retain proof of control for the self-hosted address.

Missing or unresolved information

Document incomplete exchanges and unidentified recipients for review.

The transfer record retains the information, verification evidence and reviewer decision.

Ongoing review

Keep the relationship under review after onboarding

A counterparty's identifiers and risk can change. Monitor wallet activity and use your existing identity provider for entity-level checks.

Wallet risk changes

Alert on sanctions, blacklist changes and high-risk interactions.

Unapproved wallet interactions

Flag activity with addresses outside your configured allowlist.

PEP and adverse-media review

Bring provider-based entity checks into ongoing counterparty review.

Entity-name screening is separate from onchain address attribution and exposure analysis.

How it works

Build the counterparty and transfer record

  1. 01

    Establish the party record

    Link wallet and bank identifiers with KYC, KYB and contracts.

  2. 02

    Assess each address

    Apply your attribution, exposure and behavior policy.

  3. 03

    Exchange and verify

    Route Travel Rule information and retain self-hosted wallet proof.

  4. 04

    Resolve and retain

    Review exceptions and keep the evidence with the transfer.

A dedicated Range environment for counterparty information

Isolate your workspace, control encryption keys and use private connections. Range engineers manage the environment with your team.

Talk to an expert
    • A separate cloud account, network and database
    • Nothing shared with any other customer
    • Pinned to the region you choose
    • Encrypted with keys held in your own cloud account
    • Revoke a key and the data is unreadable, to us too
    • Staff access only with your approval, always logged
    • Private links from your network, never the public internet
    • Connected to banks and custodians over private links
    • Logs streamed to your own security tools
    • Forward-deployed engineers on your team
    • We deploy, monitor and upgrade it
    • The same platform as our shared cloud
    • An audit trail for every decision
    • Evidence ready for examiners
    • Fits your existing security reviews

Counterparty questions

What compliance teams ask

The party's type, its onchain addresses across networks, its bank accounts, its KYC, KYB and contract documents and its live activity.

Range links a party's wallets, exchange deposit addresses and bank accounts to one counterparty record. Screening runs per address, so each address keeps its own findings and screen history.

Range assesses each address through attribution, exposure and behavior. Exposure shows the share and amount of sent and received volume involving flagged counterparties. Your team sets severity thresholds and USD floors, then reviews the evidence behind the findings.

Range routes Travel Rule data across integrated VASP network providers, retains a proof of control for each self-hosted address and keeps the evidence with the transfer.

The workflow brings incomplete information or an unresolved recipient to review. The record keeps the available message, verification evidence and reviewer decision with the transfer.

More questions on Travel Rule, see the full FAQ.

Case Studies

Simplify stablecoin transfers and improve transparency

“I've had the privilege of collaborating with Range since their early days. Most recently, we worked together on a pioneering project aimed at simplifying and enhancing transparency around USDC cross-chain transfers. Throughout our ongoing collaboration, Range has consistently demonstrated exceptional technical and security-focused expertise.”

John Letey, Director of Engineering at Noble

Noble logo

Protect counterparty and transfer information

Customer data is isolated and encrypted. Range does not hold your assets or private keys.

Workspace isolation

Screening activity, policies and sensitive workspace data are separated between customers.

Data protection

Range maintains GDPR-aligned processing, access, retention and privacy controls.

SOC 2 Type II audit

Range is undergoing an independent external SOC 2 Type II audit.

Layered security

Encryption, role-based access, least privilege and monitoring protect the platform.

Review the party and transfer evidence together

Bring a counterparty and a transfer flow. See how the identifiers, risk findings and Travel Rule evidence connect.