# Scheme Management Module Requirements Specification

**Document Version:** 1.0  
**Module:** Scheme Management  
**Product:** Enterprise Acquiring Platform  
**Document Type:** Functional Requirement Specification (High-Level)  
**Status:** Draft

---

# 1. Introduction

## 1.1 Purpose

The Scheme Management module provides centralized management of all payment scheme (card network) related configurations, rules, parameters, certifications, compliance, routing, and operational data required by the acquiring platform.

The module acts as the master repository for scheme-specific configurations and provides services to all other platform modules.

---

# 2. Objectives

The Scheme Management module shall:

- Support multiple payment schemes.
- Centralize scheme configurations.
- Eliminate hard-coded scheme rules.
- Maintain version-controlled scheme parameters.
- Support multiple countries.
- Support multiple currencies.
- Support multi-tenant deployments.
- Support domestic and international schemes.
- Support future scheme additions without software changes.
- Provide centralized configuration management.
- Provide complete audit history.

---

# 3. Supported Payment Schemes

The platform shall support (configurable):

- Visa
- Mastercard
- RuPay
- American Express
- JCB
- UnionPay
- Discover
- Diners Club
- Jaywan
- Meeza
- mada
- EFTPOS
- Local/Domestic Schemes
- Future Schemes

---

# 4. Scope

The module shall manage:

- Scheme master data
- Card scheme configuration
- Card products
- BIN/IIN management
- EMV parameters
- Contactless parameters
- Routing configuration
- Network parameters
- Settlement calendars
- Scheme holidays
- Certification records
- Compliance requirements
- Interchange master tables
- Assessment fee tables
- Scheme fee tables
- Reason codes
- Dispute configuration
- Scheme bulletins
- Card ranges
- Country rules
- Currency rules
- Merchant category rules
- Reporting configuration
- API configuration
- Audit information

---

# 5. Out of Scope

The module shall NOT manage:

- Merchant MDR
- Merchant pricing
- Transaction processing
- Authorization processing
- Settlement processing
- Reconciliation
- Merchant onboarding
- Terminal inventory
- Dispute processing
- Fraud decisions

These functions belong to their respective modules.

---

# 6. Module Navigation

```text
Scheme Management
│
├── Dashboard
├── Scheme Configuration
├── Card Products
├── BIN Management
├── Card Ranges
├── Country Configuration
├── Currency Configuration
├── EMV Parameters
├── Contactless Parameters
├── Routing Configuration
├── Network Parameters
├── Merchant Category Rules
├── Interchange Tables
├── Scheme Fee Tables
├── Assessment Fees
├── Reason Codes
├── Dispute Parameters
├── Settlement Calendar
├── Holiday Calendar
├── Certification Management
├── Compliance Management
├── Scheme Bulletins
├── Reports
├── Administration
└── Audit
```

---

# 7. Functional Requirements

## 7.1 Dashboard

The system shall provide:

- Active schemes
- Scheme status
- Certification status
- Upcoming expiries
- Bulletin notifications
- Configuration changes
- Compliance alerts
- Recent updates

---

## 7.2 Scheme Configuration

The system shall allow:

- Add Scheme
- Update Scheme
- Activate Scheme
- Suspend Scheme
- Deactivate Scheme
- Country mapping
- Currency mapping
- Processing window
- Settlement cycle
- Status management

---

## 7.3 Card Product Management

Maintain:

- Debit
- Credit
- Prepaid
- Commercial
- Corporate
- Virtual Cards
- Token Cards
- Fleet Cards
- Gift Cards

Configurable attributes:

- Product Code
- Product Name
- Product Type
- Scheme
- Country
- Currency
- Status

---

## 7.4 BIN / IIN Management

Support:

- BIN upload
- BIN download
- BIN lookup
- BIN search
- BIN activation
- BIN versioning
- Country mapping
- Issuer mapping
- Card product mapping

---

## 7.5 Card Range Management

Maintain:

- Card ranges
- Start BIN
- End BIN
- Issuer
- Scheme
- Country
- Status

---

## 7.6 Country Configuration

Manage:

- Countries
- Supported schemes
- Domestic rules
- Regional restrictions
- Processing rules

---

## 7.7 Currency Configuration

Manage:

- Currency codes
- Decimal precision
- Settlement currency
- Processing currency
- Supported currency list

---

## 7.8 EMV Parameter Management

Manage:

- AIDs
- CAPKs
- TAC
- Floor Limits
- Terminal Action Codes
- CVM Rules
- Terminal Capabilities
- Kernel Versions
- Risk Parameters

---

## 7.9 Contactless Parameters

Maintain:

- Contactless limits
- CVM limits
- Offline limits
- Reader limits
- Consumer device limits

---

## 7.10 Network Routing

Configure:

- Primary Network
- Secondary Network
- Routing priorities
- Failover routing
- Domestic routing
- International routing

---

## 7.11 Network Parameters

Maintain:

- ISO Version
- Message Specifications
- Processing Codes
- Function Codes
- Timeout
- Retry
- Retry Count
- Network Windows

---

## 7.12 Merchant Category Rules

Maintain:

- MCC
- MCC description
- Allowed transactions
- Cashback rules
- Installment rules
- Risk category
- Restrictions

---

## 7.13 Interchange Management

Maintain scheme published interchange tables.

Support:

- Effective date
- Country
- Scheme
- Card Type
- Merchant Category
- Transaction Type
- Currency
- Domestic
- International

---

## 7.14 Scheme Fee Management

Maintain:

- Assessment Fee
- Processing Fee
- Cross Border Fee
- Token Fee
- Chargeback Fee
- Arbitration Fee
- Compliance Fee
- Licensing Fee

---

## 7.15 Reason Code Management

Maintain:

- Scheme
- Reason Code
- Description
- Dispute Category
- Time Limits
- Required Documents

---

## 7.16 Dispute Parameters

Configure:

- Response time
- SLA
- Chargeback window
- Arbitration window
- Evidence requirements

---

## 7.17 Settlement Calendar

Manage:

- Settlement cycles
- Settlement cut-off
- Settlement holidays
- Processing windows

---

## 7.18 Holiday Calendar

Maintain:

- National holidays
- Scheme holidays
- Bank holidays
- Settlement holidays

---

## 7.19 Certification Management

Maintain:

- L2 Certification
- L3 Certification
- Host Certification
- Contactless Certification
- SoftPOS Certification
- Expiry
- Renewal

---

## 7.20 Compliance Management

Track:

- PCI DSS
- PCI PTS
- EMV
- Scheme compliance
- Key rotation
- Audit dates
- Compliance status

---

## 7.21 Scheme Bulletins

Manage:

- Bulletin number
- Bulletin date
- Description
- Impact
- Implementation status
- Effective date

---

## 7.22 Reports

Generate reports for:

- Active schemes
- BIN reports
- Certification reports
- Compliance reports
- Bulletin reports
- Fee reports
- Interchange reports
- Routing reports
- Audit reports

---

## 7.23 Administration

Manage:

- Masters
- Configuration
- User permissions
- Roles
- Templates
- Lookup values
- System parameters

---

## 7.24 Audit

Maintain audit logs for:

- Configuration changes
- User activities
- Parameter changes
- BIN updates
- Certification updates
- Fee changes
- Routing updates

---

# 8. Integration Requirements

The module shall integrate with:

- Merchant Management
- Terminal Management
- Payment Processing Switch
- Settlement Engine
- Reconciliation Engine
- Fee & MDR Management
- Dispute Management
- Fraud Management
- HSM / Key Management
- Notification Service
- Reporting Engine
- API Gateway

---

# 9. User Roles

Support role-based access for:

- Scheme Administrator
- Product Administrator
- Operations Team
- Settlement Team
- Network Team
- Compliance Team
- Risk Team
- Auditor
- Read Only User
- API User

---

# 10. Security Requirements

The system shall support:

- Role Based Access Control (RBAC)
- Maker / Checker Approval
- Four-eye Approval
- Field-level authorization
- Configuration approval workflow
- Audit logging
- Encryption of sensitive data
- API authentication
- Session management

---

# 11. Non-Functional Requirements

The module shall support:

- High availability
- Multi-tenant architecture
- Horizontal scalability
- High performance
- Configuration versioning
- Effective dating
- Rollback capability
- Localization
- Time zone support
- Multi-language support
- Backup & recovery
- Disaster recovery
- REST APIs
- Event publishing
- Bulk import/export

---

# 12. Configuration Versioning

The system shall support:

- Draft configurations
- Published configurations
- Future effective dates
- Version comparison
- Rollback
- Approval workflow
- Change history

---

# 13. Data Import & Export

Support import/export for:

- BIN files
- Card ranges
- Interchange tables
- Scheme fee tables
- Reason codes
- EMV parameters
- Routing configuration
- Certification records
- Holiday calendars

---

# 14. Notifications

The system shall generate notifications for:

- Certification expiry
- Compliance expiry
- Bulletin release
- Configuration approval
- Configuration rejection
- Version publication
- Import completion
- Import failure

---

# 15. APIs

Provide APIs for:

- Scheme lookup
- BIN lookup
- Card product lookup
- Routing lookup
- Reason code lookup
- Interchange lookup
- Scheme fee lookup
- Country lookup
- Currency lookup
- EMV parameter lookup
- Contactless parameter lookup

---

# 16. Dependencies

Dependent on:

- Authentication Service
- User Management
- Notification Service
- Audit Service
- Document Repository
- API Gateway
- HSM / Key Management

Provides services to:

- Payment Switch
- Merchant Management
- Terminal Management
- Settlement
- Fee & MDR
- Dispute Management
- Fraud Management
- Reporting

---

# 17. Future Enhancements

Future capabilities may include:

- Automatic Visa/Mastercard bulletin ingestion
- Scheme API synchronization
- AI impact analysis of rule changes
- Automatic BIN updates
- Automatic fee updates
- Configuration simulation
- Rule comparison
- Compliance dashboards
- Predictive certification renewal alerts
- AI-assisted configuration validation

---

# 18. Design Considerations

- All scheme data shall be configuration-driven.
- No scheme-specific values shall be hardcoded.
- All master data shall support versioning.
- Configuration changes shall support approval workflows.
- All configurations shall be auditable.
- Multi-country support shall be native.
- Effective-date-based configuration shall be supported.
- APIs shall be reusable across all acquiring platform modules.
- The module shall be extensible to support new payment schemes without application code changes.