About Issuer Dashboard

The CC Issuer Dashboard enables bank operations and CC management teams to manage credit card accounts, requests, and approvals efficiently.

This dashboard follows a Maker-Checker workflow to ensure dual control, security, and audit compliance for all key operations.

A maker raises a request.
A checker approves/rejects a request.

This document provides issuers with a walkthrough of the features and functionality for tracking, managing, and servicing credit card accounts through the Issuer Portal.

🔐 Roles and Permissions

CC defines three types of user roles to maintain operational hierarchy and accountability.

Role	Description	Key Actions
Admin Maker	Initiates or creates credit card operation requests.	Pay Bill Post Fee Update Card Program Account Closure Edit Total Limit Edit Maximum Credit Limit Update Payment Due Date Update/Configure Auto Debit Edit Auto Renewal View Transactions of a Card Freeze a Card Hotlist a Card Remove System Block Replace a Card Edit International/Domestic Spend Limits Refund Charges Post Chargeback Reverse Repayment
Admin Checker	Reviews, claims, and approves/rejects Maker-submitted requests.	Claim, approve, or reject requests
Support Maker	Initiates or creates credit card operation requests after authenticating customers.	Raise a request to: Pay Bill Post Fee Update Card Program Account Closure Edit Total Limit Edit Maximum Credit Limit Update Payment Due Date Update/Configure Auto Debit Edit Auto Renewal View Transactions of a Card Freeze a Card Hotlist a Card Remove System Block Replace a Card Edit International/Domestic Spend Limits Refund Charges Post Chargeback Reverse Repayment
Support Checker	Reviews and approves/rejects Maker-submitted requests.	Approve or reject requests

Only approved users can access the Issuer Dashboard using registered email IDs. All logins are secured via 2FA (Password + OTP).

🔁 Maker-Checker Workflow

All CC-related updates are routed through a Maker-Checker process. This ensures no transaction or modification occurs without a second-level review. Below is how this process works:

A maker creates a request (e.g., post a fee, account closure, and so on).
A request is created on the Approvals page with a status of Pending. A checker is assigned to the request.
The assigned checker reviews the details of the request from the Approvals page and can:
- ✅ Approve: Approves the request.
- ❌ Reject: Reject the request with comments.

Requests are auto-assigned evenly among Checkers. An admin checker can manually claim requests via the Assign to Me option.

↑