Getting started with Reven

The safest order is to confirm the scope, configure shared business data, prepare one module, test it from both the customer and staff perspectives, and only then publish the link.

1. Confirm the scope

Complete the solution specification. Confirm which modules are active, who owns the account, which currency and language apply, and which payments, Wallet integrations and devices are included in the implementation.

2. Set up the business profile

In the dashboard, go to Settings → Business profile. Check the name, description, contact details, address, logo and public business identifier. Open the public page in a private browser window to see it as a customer would.

Do not change the currency after sales have started without consulting Reven. Currency affects prices, payments and provider compatibility.

3. Add the team and roles

In Settings → Team, invite users and give each person the minimum access they need. A person who only redeems vouchers can receive a redemption-only role; an operations manager does not need access to billing or team management.

4. Configure payments

In Settings → Payments, connect a provider available for the business region and currency. Complete merchant-account onboarding and confirm that the status allows payments to be accepted. Never send passwords, API keys or tokens through ordinary email or a support chat.

5. Prepare the first module

Use the configuration map. For the first launch, choose one complete scenario, for example:

• PLN 100 voucher: purchase → email/PDF → balance check → redemption;
• booking: service → specialist → available time → appointment → cancellation;
• restaurant: menu item → order → payment → acceptance → preparation → ready.

6. Run a two-sided test

Run the customer test through the public link in a private window and on a phone. Run the staff test with the intended account and — when using Kiosk or POS — on the actual device. Check messages, statuses, amounts, language, refund or cancellation, and whether the operation is visible in the dashboard.

Do not delete a failed transaction to “clean up.” Record the time with timezone, identifier, module and result; support needs these details to establish the cause.

7. Publish and monitor

Place the correct public link on the website, social media, QR code or printed materials. For the first few days, appoint a person responsible for the dashboard and agree on a fallback customer-service process. Test every change to prices, rules, schedules or payments before publishing it broadly.