RWA Vendor Due Diligence Checklist: Twelve Evidence Checks

Evaluate legal identity, permissions, security, key controls, references, pricing and exit evidence before appointing an RWA infrastructure provider.

Reviewed by FluidRWA Research Team · November 18, 2026

Short answer

Evaluate an RWA vendor by checking its contracting entity, service scope, control of assets and keys, operational evidence and exit terms. Treat website claims and directory entries as starting points, not completed due diligence.

The demo goes well. The proposal looks polished. Your launch date is approaching, and the vendor says it can cover everything. Before you sign, ask a less comfortable question: if the service stopped tomorrow, could your team recover the records, control the assets and keep serving investors?

Due diligence turns that question into a practical buying process. You do not need to ask every provider for the same mountain of documents. You need evidence for the responsibilities you are handing over, starting with the twelve checks below.

Twelve checks and the evidence to request

CheckEvidence to requestHold the decision when
Legal identityRegistered name, jurisdiction, ownership and signing entityThe proposal and contract name different entities without explanation
PermissionsExact entity, register entry, permitted activity and restrictionsA group licence is offered as proof for a different entity
Service boundaryIncluded services, exclusions and third-party responsibilitiesCoordination is described as direct service provision
Customer referencesPermission to speak to relevant customersLogos are the only implementation evidence
Security assuranceReport date, system boundary, exceptions and remediationAn old or unrelated report is used to imply current coverage
Key and admin controlSigner matrix, recovery process and change approvalsNo one can name who can move assets or upgrade contracts
Contract auditsReport, deployed version and unresolved findingsAn audit of different code is presented as coverage
InsuranceInsured entity, limits, exclusions and claims processMarketing language replaces policy evidence
Data protectionLocations, processors, retention, access and incident termsInvestor data responsibilities are unspecified
Financial continuityAvailable accounts, support commitments and contingency planNo plan exists for provider failure
ExitRegister and data exports, migration support and noticeYou cannot obtain usable records outside the platform
Total costSetup, recurring, transaction and pass-through chargesImportant operating work is excluded from the quote

Start with legal identity, activity scope and control of keys. A material unanswered question should remain open even if the overall score looks attractive. This is a procurement checklist, not a promise that a short review establishes regulatory compliance.

Turn claims into a reproducible evidence log

Use columns for claim, source, exact product or entity, document date, date accessed, reviewer, unresolved question and decision. Keep a source link even when the page is inaccessible. An accessible register homepage is not evidence that the named company has a particular permission.

For security, the NIST Cybersecurity Framework can help organize the control discussion. A framework mapping is not certification. For token logic, compare the deployed contracts and configuration with the auditor's actual scope.

Rehearse one failure and one exit

Ask the vendor to demonstrate a lost signer, failed payment or unavailable data feed. Record how the incident is detected, who authorizes remediation and how the customer is informed. Then ask for a complete export and have a second person reproduce a balance or corporate action without the vendor dashboard.

Do not put real investor personal information in a shared demo environment. Use synthetic records and check who can access the resulting exports.

Make the decision explicit

Classify each requirement as evidenced, not applicable, open or failed. Assign an owner and deadline to open items. Obtain contractual commitments for dependencies that could prevent launch, and reject a proposal when a critical control cannot be established. Review timing depends on complexity and vendor responsiveness; there is no universal one-week completion promise.

Use regulatory lookup guidance, platform responsibilities and custody role separation. Submit your requirements with the activity and jurisdictions your project needs.

FAQ

Can a directory listing replace due diligence?

No. Use it to identify candidates, then verify the entity, scope and supporting evidence independently.

How long does the review take?

It depends on complexity, evidence quality and unanswered questions. Do not treat a fixed timetable as proof of completion.

What should stop a purchase?

An unresolved critical control, such as unclear authority to move assets, missing permissions for a required service or unusable exit records.

Planning your infrastructure shortlist?

Share the asset, service requirements and jurisdictions your project needs.

Submit requirementsRun readiness assessment