Last updated: June 18, 2026

Terms

These terms describe how businesses use Fidevos to manage wallet programs, prepaid cards, gift cards, staff scans, dashboards, and notifications.

This page is a website-ready baseline. Before final publication, it should be reviewed with legal counsel based on the company entity, providers, countries served, and the real product setup.

01

Accounts and access

The business is responsible for staff accounts, assigned permissions, and proper credential use. Each team member should use only their assigned access.

02

Wallet programs

The business configures rules, rewards, balances, gift cards, locations, copy, and pass design. Conditions shown to customers must be accurate and honored at redemption.

03

Scans, rewards, and prepaid value

Staff scans update passes, stamps, points, rewards, or prepaid balance. The business remains responsible for the commercial accuracy of top-ups, usage, refunds, expiration dates, and promotions.

04

Communications

Wallet notifications and campaigns must be relevant to the program and respect applicable preferences, consents, and regulations. Fidevos may limit abusive or non-compliant use.

05

Payments and plans

Monthly fees, additional locations, onboarding, integrations, and dedicated services depend on the agreed plan. External costs, such as POS providers or third-party services, are not included unless agreed in writing.

06

Integrations

Integrations with POS, CRM, ERP, or other systems depend on technical availability, provider APIs, and agreed scope. Timing and responsibilities are defined before work starts.

07

Availability and changes

Fidevos aims to keep the service stable and secure, but may update features, interfaces, or infrastructure to improve the product, security, or compliance.

08

Limitations

The business must not use Fidevos for illegal, misleading, discriminatory, spam-like, or third-party-infringing content. Fidevos may suspend access in case of misuse.

09

Support

Support covers setup, platform use, and technical issues according to the selected plan. Custom services, migrations, or dedicated development require a separate agreement.