m2pfintech
Implementation Guide

Product Configuration

Define card programs with transaction limits, fee structures, KYC requirements, and wallet configurations.

A Product defines the complete ruleset for a card program — including who can get a card, what they can do with it, and how much it costs.


What is a Product?

Each card program you launch is backed by a Product configuration. Think of it as a template that defines:


Core Settings

SettingDescriptionTypical Values
Product NameDisplay name for the card program"Travel Card", "Corporate Expense Card"
Product IDUnique identifier used in API callsAssigned during setup
Card TypeVirtual, Physical, or BothVIRTUAL, PHYSICAL, BOTH
Card NetworkAssociated card networkVisa, Mastercard, RuPay
Card ExpiryValidity period from issuance3 years, 5 years, 10 years

KYC Requirements

The minimum KYC level determines which customers can be issued cards under this product:

KYC LevelDocuments RequiredTypical Limits
Minimum KYCMobile number + One ID proofLower transaction and balance limits
Full KYCPAN + Aadhaar/Passport + Address proofHigher limits as per RBI guidelines

Customers onboarded with Minimum KYC can be upgraded to Full KYC later via the KYC upgrade API, which automatically unlocks higher limits.


Transaction Limits

Limits are configured per product and apply at multiple levels to ensure compliance and risk management:


Fee Structure

Fees are configurable per product and can be set to zero if not applicable:

Fee TypeDescriptionTypical Range
Issuance FeeOne-time fee charged when a card is issued₹0 – ₹500
Reload FeeFee per wallet load/credit transaction₹0 – ₹25
ATM Withdrawal FeeFee per ATM cash withdrawal₹0 – ₹25
Annual / Monthly FeeRecurring maintenance fee₹0 – ₹500/year
Replacement FeeFee for issuing a replacement card₹0 – ₹300
Cross-Border FeeMarkup on international transactions0% – 3.5%
Currency Conversion FeeFee for forex wallet conversions0% – 2%

Fees are deducted automatically from the wallet balance at the time of the transaction. Fee configurations can be updated by M2P without requiring code changes on your side.


Configuration Flags

These flags control advanced product behavior:

FlagEffect
Customer ID TypeWhen enabled, idType and idNumber become mandatory during registration
Dedup StrategyControls how duplicate customers are detected — by Mobile, ID Number, or combination
Registration Unique CheckEnables tenant-level uniqueness validation during registration
NETC RegistrationAdds vehicle and FASTag fields to the registration flow for toll card programs

On this page