← Wallet buyer guides

Wallet software procurement checklist

A useful procurement process makes delivery assumptions visible before the agreement is signed. Give commercial, engineering, operations and security reviewers a shared brief.

WalletD · Content updated . Product scope and operating responsibilities; deployment acceptance is separate.

Define the product and delivery boundaries

Describe the wallet workflows, users, providers and systems involved. Ask each supplier to distinguish available capabilities from configuration, custom development and planned work. Tie delivery milestones to observable acceptance criteria.

  • Business workflows and expected transaction patterns
  • Required integrations and customer-side dependencies
  • Demonstration, test, handover and launch criteria

Evaluate build versus buy using explicit assumptions

Compare internal development with a vendor engagement across implementation, maintenance, staffing, infrastructure and operational support. Account for integration work in both options. Avoid treating a software license as the full cost of operating a wallet. Model at least 36 months of expected transaction volume: a subscription with a per-transaction fee and a flat subscription can swap places on cost as volume grows.

  • Internal engineering and on-call capacity
  • Time spent maintaining integrations and upgrades
  • Transition, data export and replacement costs

Request evidence for security and compliance claims

Ask what evidence applies to the product, service and proposed deployment. Certification support is different from an independently assessed certification. Have qualified reviewers determine the scope and obligations applicable to your organization.

  • Scope, date and issuing party of any claimed assessment
  • Control ownership across customer, vendor and hosting provider
  • Evidence and remediation work included in the engagement

Review commercial and operating terms together

Clarify permitted use, custom-code rights, renewal and exit provisions alongside support and delivery commitments. Record exclusions. A flexible agreement is useful when responsibilities and change handling are clear to both parties.

  • License scope, environments and custom-work rights
  • Support hours, severity definitions and response commitments
  • Change requests, acceptance, termination and handover terms

What should the operator verify?

Confirm which capabilities are shipped, configured, custom work or planned. WalletD is in early access; synthetic ledger evidence is not production acceptance or a security certification. The operating partner owns customer funds, provider contracts and required permissions.

Inspect the evidence and its limits · Review software prices and separate running costs