Please enable JavaScript.
Coggle requires JavaScript to display documents.
Unified Merchant Data & Portal - Coggle Diagram
Unified Merchant Data & Portal
Problems
Fragmented Experience
Merchant interaction is inconsistent. (SSO)
Fragmented Data
Merchant master data (devices, companies stores branches NACE, user management..) are in silos (DBs etc.)
Possible inconsistency duplication or defects
Lack of Backoffice Panel for Token Teams
Democratization based on access policies within the company
Lack of the ability to track merchant activity for VAS etc.
Device Activity
Which merchants uses which integration?
Which merchants accepts offers ?
How to reach an merchant group based on NACE?
Merchant communications for events & updates?
Device offers ok, but integrations and VAS ?
Phases
Master merchant system development with all parties
1.a. Merchant registration, onboarding, KYC
1.b. Consolidate existing merchants into new system
1.c. Single sign-on, identitity access management for merchants
Portal Development
2.a Merchant master management devices, apps, stores, stores and branches
2.b.
Token Merchant Portal
Master Merchant Management
Identity & Access Management
Company & Branch & Store Management
Devices
Banking Apps
Subscriptions ?
Terms & Conditions & Compliance
Merchant Registration - Single Point
After Sales
Tickets & Tracking
Dashboard
Device Info
Campaigns
News & Notifications
Sales & Revenue in branches
Token X Access & Redirection
Campaigns and Upsell opportunities
Key Resources
All Apps - Ozan's Team
aTMS - eBelgeler- Sedat's Team
Legacy Systems - Sinan's Team
Customer Service - Ferhat - Gökhan
3rd party or internal for orchestration
Merchant Apps
Sales & After Sales
Fito
Customer Service
Açma Kapama Devir
Usage Problems
Defects
Campaigns & Upsell
New Device offers
Battery Offers
Sales
Peripherals
Devices
Platform & Integrations
Token X
Sales Automation
E belge & E arşiv
Subscriptions
IAM & SSO
Meal Cards
Proposal
Single Merchant Portal