Fetch Load Details by ID
Retrieves a specific pool load transaction by its ID. Use this to check the status of a pool load request (CREATED → APPROVED → SUCCESS/FAILED).
Authorization
bearerAuth tenantId JWT Bearer token from the Authentication API
In: header
Your unique tenant identifier assigned during onboarding
In: header
Path Parameters
Pool Load Transaction ID
Header Parameters
Your unique tenant identifier
Response Body
application/json
application/json
curl -X GET "https://sandbox-api.m2pprepaid.com/prepaid/customer/v1/load/LD20260101001" \ -H "X-TENANT-ID: ACME_CORP"{
"result": {},
"pagination": {
"list": true,
"pageSize": 0,
"pageNo": 0,
"totalPages": 0,
"totalElements": 0
}
}{
"type": "https://www.m2pfintech.com/problem/problem-with-message",
"title": "Load transaction not found",
"status": 409,
"detail": "Load transaction with ID LD20260101001 does not exist",
"message": "error.business",
"businessCode": "PP_CORP_002"
}Fetch All Forex Transactions POST
Retrieves transaction history specifically for forex cards. The response includes a **parent-child transaction structure** where: - **Parent transaction**: The original card-level transaction (e.g., POS purchase in SGD) - **Child transactions**: Wallet-level breakdowns showing which currency wallets were debited and the exchange rates applied ### When to Use - Display forex transaction history with currency conversion details - Show customers how multi-currency transactions were split across wallets - Reconciliation for forex card operations ### Response Fields Key fields in each transaction: - `transactionCurrencyCode` / `transactionCurrencyCodeName`: Currency of the original transaction - `baseCurrencyCode` / `baseCurrencyCodeName`: Base currency (typically USD) - `exchangeRate`, `markupRate`, `markupServiceTax`: Currency conversion details - `preBalance` / `postBalance`: Wallet balance before/after (in child transactions) - `forexWallet`: Which forex wallet was used
Fetch Transaction History POST
Retrieves transaction history for a cardholder filtered by entity ID, date range, mobile number, or kit number. Supports pagination. ### When to Use - Display transaction history in your app or portal - Reconciliation and settlement reporting - Customer support — look up recent transactions ### Filters - **entityId** (required): Cardholder's entity identifier - **fromDate / toDate**: Date range filter (format: dd-mm-yyyy) - **kit**: Filter by specific card kit number - **mobile**: Filter by mobile number - **accountId**: Filter by specific wallet/account - **success**: Set to `true` to return only successful transactions - **isOffline**: Set to `true` to include offline transactions ### Response Structure Returns a paginated list of transactions with details including amount, type, merchant info, pre/post balance, exchange rates, and status.
