Accredifi lets institutions request proof that a user controlled a MetaMask wallet at signing time, capture balance evidence, and reverify on a schedule without taking custody.
A MetaMask signature is powerful evidence, but it is not a full compliance workflow on its own. Accredifi turns that signature into a structured record institutions can use alongside their existing onboarding, underwriting, and AML/KYC processes.
A valid signature proves the user controlled the wallet when they signed. It does not permanently prove future control.
Balances are fetched and recorded separately. Institutions should treat ownership proof plus balance at time T as the useful attestation.
Accredifi supplies tamper-evident evidence. How that evidence supports lending, accreditation, AML, or compliance decisions remains your policy.
A MetaMask verification is not just a signature prompt. It is a recorded workflow that starts with an institution request and can continue through scheduled reverification.
The institution creates an email or one-time link with the requested wallet data and optional verification schedule.
The user accepts the request and signs a one-time message. Accredifi verifies the signature against the wallet address.
Wallet access is granted, evidence is stored, and scheduled reverification can require the user to sign again when due.
Accredifi gives your team the pieces needed to request wallet access, consume verified evidence, and keep the relationship current over time.
Send an email or one-time verification link from your loan application, onboarding flow, or review process.
Retrieve addresses, balances, and verification proof through API endpoints for your CRM, underwriting, or compliance tools.
Use webhooks and verification schedules to handle access grants, revocations, due dates, and overdue reverification.
No. MetaMask is wallet software. It can sign messages that prove wallet control, but legal identity, AML, and KYC decisions remain part of your institution's own workflow.
Accredifi creates a one-time signing request. The user signs it in MetaMask, Accredifi verifies the signature against the public address, and the private key never leaves the wallet.
It proves the user controlled the wallet at the time of signing. It does not prove current control forever, and balance data is supporting evidence captured separately at a point in time.
Yes. Institutions can create access requests by API or link, receive events when access is granted or verification is completed, and retrieve balances, addresses, and verification records for their systems.
Yes. Verification schedules can require the user to sign again on a recurring cadence, such as monthly. Due windows and overdue actions can be configured for ongoing assurance.
No. Accredifi is a verification infrastructure layer. Funds remain in the user's wallet, and no asset transfer is required to complete verification.
Still have questions?
Contact our teamInfrastructure layer for lending and compliance
Users sign messages to prove control. Funds stay in the user's wallet and private keys are never transmitted.
Store timestamped proof of wallet control alongside balance evidence for underwriting and compliance review.
Create access requests, monitor verification state, and retrieve records programmatically in your existing stack.
Require users to re-sign on a cadence when ongoing assurance is needed for lending or compliance workflows.
Create access requests, verify wallet control, capture balance evidence, and schedule reverification without custody or private key exposure.