Viva Wallet
Fair 3.3 Easy 3.7 Secure 4.7
| Pillar | Criterion | Score | Evidence |
|---|---|---|---|
| Easy | Day-one UX Can non-technical staff use it without a project? | 3 | Typical onboarding for this product category. Source |
| Easy | Operate Admin burden, updates, backups and language coverage. | 4 | Vendor operates the hosted service. Source |
| Easy | Integrate SSO, mail/CalDAV, APIs and common NGO connectors. | 4 | Integrations vary; check current APIs and connectors. Source |
| Fair | Lock-in / exit Can you leave with your data in open formats, at known cost? | 3 | Exports/APIs usually exist; switching still costs migration effort. Source |
| Fair | Sovereignty EU legal entity, EU hosting, and exposure to extra-EU lawful access? | 5 | EU/EEA/EFTA legal entity per European Alternatives listing; confirm regions. Source |
| Fair | Openness Open source or open standards? Are independent implementations possible? | 2 | Proprietary product. Source |
| Secure | IT security Authentication, encryption, patch cadence and independent audit. | 5 | Security baseline depends on vendor posture and your configuration. Source |
| Secure | User security 2FA, roles, phishing resistance and safe defaults. | 4 | Account roles and MFA availability vary by plan. Source |
| Secure | Personal data GDPR fit: DPA, residency, sub-processors and Schrems II posture. | 5 | European vendor GDPR posture; still confirm DPA and subprocessors. Source |