The missing layerbetween wallets and finance

Financial systems need to verify crypto holdings. Wallets weren't built to prove anything to institutions. Accredifi bridges that gap with cryptographic proof that both sides can trust.

  • Proof of ownership without custody transfer
  • Balances that update with the chain
  • Verification that persists across your workflow
  • Audit trail that survives review

For lending, underwriting, compliance, and onboarding teams.

The problem

Crypto is entering regulated workflows. Verification hasn't kept up.

More clients hold wealth in self-custody wallets. Lenders, compliance teams, and onboarding flows are being asked to verify it. But there's no standard way to do this.

What teams ask for

  • “Send a screenshot”
  • “Share a CSV export”
  • “Show us your wallet”

What that gives you

  • No cryptographic proof
  • No audit trail
  • No way to reverify

What that means

  • Regulatory exposure
  • Slower decisions
  • Defensibility gaps

This is the gap Accredifi closes.

Why existing approaches fail

The workarounds don't work

Every alternative either compromises security, creates compliance gaps, or doesn't scale.

ApproachResult
Ignore itUnderestimates net worth, misses risk
ScreenshotsUnverifiable, easily faked, stale the moment taken
Custody transferHigh friction, defeats purpose of self-custody
Manual lookupNo ownership proof, not repeatable, no audit trail
AccredifiProof of ownership + live balances + persistent audit trail
What Accredifi is

A verification layer between wallets and your systems

Accredifi sits between the user's wallet and your institution. It verifies ownership cryptographically, structures the data for your systems, and maintains an audit trail you can defend.

User

Self-custody wallet

Signs a message to prove control

Accredifi

Verification layer

Verifies ownership, tracks state, surfaces data via API

Institution

Your systems

CRM, underwriting, compliance tools

Verification is not a moment. It's a lifecycle.

Proof persists, balances update, and the audit trail grows with every interaction.

Use cases

Where teams use this

Common workflows where institutions need to verify self-custodied crypto.

Crypto-backed lending

The situation

You need to verify collateral before approving a loan

With Accredifi

Accredifi verifies wallet ownership and surfaces balances. You get an API response your underwriting system can trust.

Onboarding & KYC

The situation

Client claims to hold crypto as part of net worth

With Accredifi

Instead of screenshots, they complete a verification session. You get proof that survives compliance review.

Ongoing compliance

The situation

You need to reverify holdings over time

With Accredifi

Accredifi schedules reverification and tracks status. Your systems stay up to date without manual follow-up.

See implementation details for institutions and individuals.

How it works

Verification that persists

Not a one-time check. An ongoing relationship with state you can enforce.

  1. 01

    Request access

    Institution creates an access request for the user

  2. 02

    User verifies

    User connects wallet and signs a verification message

  3. 03

    Proof is stored

    Accredifi records the cryptographic proof with timestamp

  4. 04

    Access is granted

    Institution can now retrieve verified data via API

  5. 05

    State persists

    Verification status and balances stay up to date

  6. 06

    Reverification runs

    Scheduled checks keep the relationship current

Integration

Fits into existing workflows

REST API, webhooks, and hosted verification links. Add verification to your onboarding, underwriting, or compliance flows without rebuilding them.

REST API

Create access requests, retrieve wallet data, manage verification lifecycle.

  • OAuth 2.0 authentication
  • JSON responses
  • Versioned under /api/1.0/

Webhooks

Get notified when verification events occur.

  • wallet_verification.success
  • wallet_access.granted
  • wallet_access.status_changed

Hosted links

Send users a verification link. No frontend work required.

Generate a link, embed it in your onboarding flow or email. User completes verification. You get the webhook.

Typical integration

// 1. Create an access request
POST /api/1.0/access-requests

// 2. User completes verification (via hosted link)

// 3. Receive webhook
wallet_verification.success

// 4. Retrieve verified data
GET /api/1.0/wallet-accesses/{id}
Security model

Verification without custody

Users keep their keys. You get cryptographic proof. Both sides win.

What Accredifi never does

  • Never touches private keys
  • Never moves or holds assets
  • Never requires custody transfer

What it does instead

  • Verifies ownership via message signing
  • Stores cryptographic proof with timestamp
  • Logs every access decision for audit

Built for audit

Every verification produces evidence you can defend.

Proof of ownership

Cryptographic signature proving wallet control, tied to timestamp.

Access audit trail

Who requested access, when it was granted, what scope was permitted, when it was revoked.

State history

Every status transition is logged. You can show regulators exactly what happened and when.

Start verifying self-custody holdings

Your clients already hold crypto in self-custody wallets. Give your team a way to verify it that survives audit.

Free tier includes 10 verifications per month. No credit card required.