m2pfintech
API LibraryCustomer

Upgrade Customer KYC

Upgrades a customer's card KYC level from Min KYC to Full KYC. This is required to increase transaction limits and enable full card functionality.

Supported Document Types

TypeDescription
PANPermanent Account Number
AADHARAadhaar card
PASSPORTPassport
DRIVING_LICENCEDriving licence
VOTER_IDVoter ID card

First-Time Registration

For customers being registered for the first time during KYC upgrade, provide the firstTimeRegistration object with name, gender, email, and card details.

Prerequisites

  • Customer must be in Min KYC status
  • Valid identity document is required
POST
/v1/customers/upgrade/kyc

Authorization

bearerAuth tenantId
AuthorizationBearer <token>

JWT Bearer token from the Authentication API

In: header

X-TENANT-ID<token>

Your unique tenant identifier assigned during onboarding

In: header

Header Parameters

X-TENANT-ID*string

Your unique tenant identifier

Request Body

application/json

entityId*string

Required. Customer entity ID

Length1 <= length
docType*string

Required. Identity document type

Length1 <= length
Value in"PAN" | "AADHAR" | "PASSPORT" | "DRIVING_LICENCE" | "VOTER_ID"
docNo*string

Required. Document number

Length1 <= length
proxyCardNo?string

Kit number of the card

txnRefNo?string

Unique transaction reference

kycType?string

Target KYC type

productId?string

Product ID

kycIdentifier?string

KYC identifier

refNo?string

Reference number (kit number for SOR call)

dob?string

Date of birth (format: YYYY-MM-DD)

Match^(\d{4})-(\d{2})-(\d{2})$
address?
firstTimeRegistration?

First-time registration details (if new customer)

Response Body

application/json

application/json

application/json

curl -X POST "https://sandbox-api.m2pprepaid.com/prepaid/customer/v1/customers/upgrade/kyc" \  -H "X-TENANT-ID: ACME_CORP" \  -H "Content-Type: application/json" \  -d '{    "entityId": "615928984620006085281025",    "docType": "PAN",    "docNo": "UIXEU1234T",    "proxyCardNo": "1000000009",    "txnRefNo": "M2P130015"  }'
{
  "result": {
    "status": "success",
    "message": "Customer's Card KYC upgraded successfully"
  },
  "pagination": null
}
{
  "type": "https://www.m2pfintech.com/problem/problem-with-message",
  "title": "Bad Request",
  "status": 400,
  "detail": "Unable to convert http message",
  "message": "error.http.400"
}
{
  "type": "https://www.m2pfintech.com/problem/problem-with-message",
  "title": "Invalid request",
  "status": 409,
  "detail": "Invalid request",
  "message": "error.business",
  "businessCode": "PPCUST_010"
}

Update Customer Trip Details POST

Adds or updates travel trip details for a forex customer. Trip information is required for forex card operations and regulatory compliance. ### Trip Types - `NEW` — Adding a new trip - `EXISTING` — Updating an existing trip (provide trip `id`) ### Trip Details Include - Destination country with ISO codes - Travel dates (start/end) - Purpose of travel (with RBI purpose codes) - Passport details (number, file number, issue/expiry dates) - Supporting documents

Fetch All Dispute Reason Codes GET

Retrieves the complete list of dispute reason codes across all card networks. Use this endpoint to populate a reason code dropdown in your dispute filing UI. ### Response Returns a flat list of all active reason codes. Each reason code includes: - `id`: Internal identifier - `reasonCode`: The network-specific reason code (e.g., "13.1" for VISA) - `reasonCodeDesc`: Human-readable description of the dispute reason - `status`: Whether the reason code is currently active ### Tip If you need reason codes for a specific network only, use the `/v1/disputes/fetch-reason-codes/network/{id}` endpoint instead.