Business / Merchant
Service Activation Request
Architecture preview for merchants who request Ehsan ECO commerce, inventory, HRM and POS activation through a consumer introducer CIN. This page does not mutate merchant services, wallet or ledger data yet.
No live submission yet.
Future request needs consumer approval.
Example from gross system commission.
After buyer and introducer share.
Merchant request draft
Future live version should validate introducer CIN, merchant identity, country and service eligibility before submission.
Commission and activation policy
This mirrors the Supreme Root Admin commission engine architecture.
If merchant pays 100 BDT system commission: buyer consumer receives 25, shop introducer receives 10, and the remaining 65 flows to the Commission Distribution Tower.
Merchant service activation should not become valid until the introducer consumer accepts the request.
Store merchant CIN, introducer CIN, selected services, accepted timestamp, country, currency, policy version and audit actor.
Request contract preview
API/ledger contract reserved for the future live merchant request flow.
/api/commission-engine/merchant-introducer-preview
Disabled. This page is still architecture preview only.
Consumer acceptance is required before services become activation-ready.
Lifecycle path
No live submission is performed in this phase. These steps reserve the correct operational path.
- 1
Merchant enters introducer consumer CIN.
- 2
Merchant selects required services.
- 3
Request is held as pending until the consumer accepts.
- 4
After acceptance, selected services become activation-ready.
- 5
Future ledger events use buyer CIN, merchant CIN, introducer CIN, country, currency and policy version.