m2pfintech
Integration Guide

Entity State Machines

State machines for Customer, Card, and Maker-Checker workflows in M2P Prepaid Platform.

Understanding entity states and valid transitions is critical for integration. Invalid transitions will return PPCUST_032 (Invalid Status Transition) or PP_CORP_187 (Cannot perform operation) errors.


Customer Entity Status

Valid Status Values:

StatusDescriptionTransactions Allowed
ACTIVENormal operating stateAll
LOCKEDTemporarily frozen (reversible)None
BLOCKEDPermanently blockedNone
FRAUDFraud-flaggedNone
CUSTOMER_BLOCKEDBlocked by customer requestNone
CREDIT_FREEZEOnly credits blockedDebits only
DEBIT_FREEZEOnly debits blockedCredits only
REFUND_ONLYOnly refunds allowedRefunds only
INACTIVENot yet activatedNone
CLOSEDPermanently closed (terminal)None
EXPIREDExpired (terminal)None

Card Status Lifecycle

Status Transition Rules:

FromAllowed ToNotes
ACTIVELOCKED, BLOCKED, HOTLISTEDOnly active cards can be locked or blocked
LOCKEDACTIVE (unlock)Only locked cards can be unlocked
BLOCKEDREPLACEDBlocked cards can only be replaced
HOTLISTEDTerminal state
CLOSEDTerminal state
EXPIREDTerminal state

BLOCKED, HOTLISTED, CLOSED, and EXPIRED are terminal states — no further transitions allowed.


Card Delivery Lifecycle


Maker-Checker Workflow

Critical operations require dual authorization:

Operations requiring Maker-Checker:

OperationService
Product creation and configuration changesConfiguration API
Corporate creation and product mappingConfiguration API
BIN range additionConfiguration API
Issuance approval (configurable)Corporate API
Fee structure changesConfiguration API
Card actions (block, replace)Corporate API

On this page