Skip to main content
Research checked 13 October 2026. This is a requirements/design reference list. Institution counsel/compliance and accountable bank owners must validate applicability and amendments before adopting regulated policy.

​
M2P product references

M2P publicly presents modular core banking, card-management and lending platforms. This separation informs the product reference; the documented Banking responsibilities and workflows are this project’s own design. Provider marketing cannot supply Banking’s fees, approval limits, contract schemas, regulatory permission, certification or operating readiness. Features not explicitly requested, such as AI decisioning, UPI or merchant acquiring, remain candidates requiring scope decisions.

​
Indian regulatory reference register

No historical 2022 card page is treated as the sole current authority for a 2026 deployment. This review intentionally avoids coding legal thresholds, deadlines or limits from an incomplete regulatory reading.

​
Source facts versus design proposals

References establish public capability patterns and relevant policy sources. B01–B35 features, diagrams, examples, sequencing and combination tests are original proposals for owner review. They do not claim M2P implements the exact same internal state machine. Legacy implementation evidence comes from the current workspace’s module index, source feature inventory and dated verification records. Current source contradicts older production-route-absence statements; route presence still proves neither full hosted acceptance nor live bank operations.

​
Mintlify authoring/runtime

Use official navigation and official CLI preview. The local review now runs the official mint CLI rather than a substitute Markdown renderer. Search/assistant account features may require separate CLI sign-in; content, tabs and Mermaid preview are independently reviewable.