Customer management
Accounting, tracking of actions and sessions, connection of support channels.
Product
FWalls Back-office
CRM, transactions and loyalty
Shipped
Year2019
The challenge
What the client faced
The task the client came with and why it could not be solved before.
A service with customer accounts needs transactions, verification, loyalty and support — normally four separate systems that fit together badly.
Mechanics
What is inside
The mechanics the product is built from.
Transactions
Multi-currency accounts including crypto, full history and multiple payment providers.
Loyalty programme
Tiers, achievements, bonuses and wager tracking — with sub-systems linked to each other.
Flexible front end
Websites are deployed on top of the API, content is localised directly on the site.
Pipeline
The client's path
The client's path through the product: from sign-up to loyalty and the public website.
-
01
Company and solution
Companies and solutions are created in the back office: a ready solution is assembled from a template, and staff get access rights.
-
02
Client verification
KYC: managing the client's documents and verifying contact information, phone numbers and postal addresses.
-
03
Account and reporting
A multi-currency client account, tracking of the client's activity on the solution website and of client sessions, connection of support channels.
-
04
Transaction
Transaction requests are processed, payment providers are connected and categorised, and the history of operations is kept.
-
05
Loyalty programme
Statuses, achievements and bonuses accrue by configurable rules; subsystems are linked to each other and wagers are tracked.
-
06
The client sees the result
The public interface is deployed from a solution template on top of the back-office API: payment acceptance, content localisation right on the site.
Where it sits
Where it sits
The back office sits between external services and the interface the client sees.
External services
What connects
Payment providers, technical support channels, mailings and notifications.
FWalls Back-office
The core of the product
Companies and solutions, clients and KYC, transactions, loyalty, provider management and localisation.
Public interfaces
What the client sees
Websites deployed from solution templates on top of the back-office API and tuned to the client's tasks.
Outcome
What it gives you
Why this is one product rather than several systems glued together by integrations.
One perimeter instead of several systems
Accounting, transactions, verification and loyalty live in one product and work with the same client data.
Solutions are assembled from templates
A new solution for a client is deployed from a ready template rather than built from scratch.
Access rights are separated
Company staff and their rights are managed in the same interface as client data.
Loyalty subsystems are linked
A bonus for a purchase and a tier for completing achievements: rules are configured rather than hard-coded.
Providers change without rework
Payment providers are connected and categorised in the back office.
The client's website is tuned to them
The public interface runs on the back-office API, with content localisation right on the site.
Technology
What it is built on
The platform, the stack and the devices the product runs on.
Technologies
- Odin
- KYC
- Payment providers
- D3.js
Platforms
- Web
- API
Links
Where to look
The product website and the materials about it.
Live demo
Demo access is provided on request.
Need a product like this under your brand?
We will deploy it white-label, tune the processes and onboard your team.