Transaction History
This service will fetch the details of transaction made on the prepaid card.
Request parameters:
Node |
Child Node |
Type |
Length |
Description |
Remarks |
header |
msg_id |
String |
12 |
Unique Source Message ID
|
Mandatory |
msg_type |
String |
13 |
Request Type Default: "ENQUIRY" |
Mandatory |
|
msg_function |
String |
50 |
Function name to be used Default: "REQ_TRANSACTION_HISTORY" |
Mandatory |
|
src_application |
String |
5 |
Source requesting channel e.g. “IVR” |
Mandatory |
|
target_application |
String |
10 |
Target application name e.g. “PCMS” |
Mandatory |
|
timestamp |
String |
30 |
Timestamp of the request Format “DD/MM/YYYY HH:MM:SS” |
Mandatory |
|
tracking_id |
String |
15 |
Transaction Tracking ID |
Mandatory |
|
bank_id |
String |
4 |
Source Bank e.g. “bankID” |
Mandatory |
|
instance_id |
String |
10 |
N/A |
Optional |
|
body |
Card_no |
String |
Min-16 Max-19 |
14/16-digit card no e.g: XXXXXXXXXXXX0833 First 6 digits will be BIN for PCMS cards |
Mandatory |
from_date
|
String
|
8
|
Format - YYYYMMDD Start Range for Transaction Acquiring Date |
Optional |
|
to_date
|
String
|
8 |
Format - YYYYMMDD End Range for Transaction Acquiring Date |
Optional |
|
is_financial
|
String
|
1 |
Sample: ‘Y’- for fetching financial transactions, ‘N’ –for fetching Non-Financial Transaction and ‘A’- for fetching ALL Transactions |
Mandatory |
|
is_posted
|
String | 1 | Sample: 0 – List both Authorize & Posted Transactions 1 – List only Posted Transaction 2 – List only Authorized Transactions | Optional | |
output_type
|
String | 1 | Sample: 0 – Card number Transaction Only 1 – Wallet ID Transactions | Optional | |
sort_order
|
String | 2 | 01 – Ascending Order, 02 – Descending Order | Optional | |
top_n
|
String | 3 | Specifies the top N transactions to be returned. 0 specifies all transactions in the range. If N is greater than the number of records that lie in the range, the actual number of records will be returned. For instance, if a request is made with Top N parameter set to 5 and the actual number of results lying in the range are 3, then 3 records will be returned. | Optional | |
transaction_channel
|
String | 4 | 0000 – For all channels. Xxxx – For specific channel on which records should be filtered. | Optional |
Request Json
{
"NISrvRequest": {
"request_transaction_history": {
"header": {
"version": "1.0",
"msg_id": "1234567",
"msg_type": "ENQUIRY",
"msg_function": "REQ_TRANSACTION_HISTORY",
"src_application": "IVR",
"target_application": "PCMS",
"timestamp": "1",
"tracking_id": "1",
"bank_id": "bankID",
"instance_id": null,
"status": null,
"user_id": null,
"work_station_id": null
},
"body": {
"card_no": "XXXXXXXXXXXXXXX",
"from_date": "20200101",
"to_date": "20200201",
"is_financial": "A",
"is_posted": "0",
"output_type": "0",
"sort_order": "01",
"top_n": "20",
"transaction_channel": "0000"
}
}
}
}
Response parameters:
Node |
Child Node |
Type |
Max |
Description |
Remarks |
header |
msg_id |
String |
12 |
Source Message ID |
Mandatory |
msg_type |
String |
13 |
Request Type “TRANSACTION” |
Mandatory |
|
msg_function |
String |
50 |
“REP_CARD_STATUS_ CHANGE” |
Mandatory |
|
src_application |
String |
5 |
Source requesting channel e.g. “IVR” |
Mandatory |
|
target_application |
String |
10 |
Target application name |
Mandatory |
|
timestamp |
String |
30 |
Date & time. Format “DD/MM/YYYY HH:MM:SS” |
Mandatory |
|
tracking_id |
String |
15 |
Tracking ID |
Mandatory |
|
bank_id |
String |
4 |
Source Bank e.g. “bsnkID” |
Mandatory |
|
instance_id | String | 10 | NA | Optional | |
exception_details |
application_name |
String |
20 |
Name of the component |
Mandatory |
date_time |
String |
30 |
Date & time. Format “DD/MM/YYYY HH:MM:SS” |
Mandatory |
|
status |
String |
1 |
Transaction Status S/F S – Success, F - Failure |
Mandatory |
|
error_code |
String |
4 |
Error Code |
Mandatory |
|
error_description |
String |
100 |
Error Description |
Mandatory |
|
trace | String | 10 | NA | Optional | |
data | String | 10 | NA | Optional | |
type | String | 10 | NA | Optional | |
transaction_ref_id |
String |
20 |
Transaction Reference ID |
Optional |
|
body |
transaction_details |
||||
card_no | String |
Min-16 Max-19 |
Card Number of the Customer |
Mandatory | |
expiry_date |
String |
4 |
Expiry Date of Card : Sample: XXXX |
Mandatory |
|
wallet_id |
String |
20 |
Unique Wallet ID Assigned |
Mandatory |
|
transaction_code |
String |
4 |
Refer to Appendix A |
Mandatory |
|
source_channel_type |
String |
4 |
Fixed Set of Value: 0132 - CDM |
Mandatory |
|
wallet_balance |
String |
9 |
Current Balance of Wallet Sample: 2000.00 |
Mandatory |
|
transaction_local_date |
String |
8 |
Format- YYYYMMDD Transaction Acquiring Date Sample: 20091218 |
Mandatory |
|
transaction_local_time |
String |
6 |
Format- HHMMSS Transaction Acquiring Time Sample: 163755 |
Mandatory |
|
posting_date |
String |
8 |
Format- YYYYMMDD Posting Date Sample: 20091218 |
Mandatory |
|
retrieval_reference_number |
String |
10 |
Unique number for a transaction within a day Sample: 9xxxxxxx5 |
Mandatory |
|
transaction_amount |
String |
9 |
Amount of Transaction. If a transaction is Posted the Posted Amount will be shown Sample: 2000.00 |
Mandatory |
|
transaction_currency |
String |
3 |
3- digit ISO Code |
Mandatory |
|
transaction_narration |
String |
50 |
Narration for Transaction |
Mandatory |
|
auth_id_response_code |
String |
10 |
Authorization Code of Transaction Sample: 190990 |
Mandatory |
|
billing_amount |
String |
16 |
Billing Amount of Transaction. Sample: +00012000000 |
Optional |
|
billing_currency |
String |
3 |
3- digit ISO Code |
Mandatory |
|
settlement_type |
String |
1 |
Type of Settlement. Debit or Credit Fixed Set of Values : D – Debit C - Credit |
Optional |
|
merchant_name_location |
String |
50 |
Name and Location of Merchant in case of POS Transactions. |
Mandatory |
Response Json
{
"NISrvResponse": {
"response_transaction_history": {
"header": {
"version": "1.0",
"msg_id": "1234567",
"msg_type": "ENQUIRY",
"msg_function": "REP_TRANSACTION_HISTORY",
"src_application": "IVR",
"target_application": "PCMS",
"timestamp": "2020-02-27T15:21:37.926+04:00",
"tracking_id": "1",
"bank_id": "bankID",
"instance_id": null,
"status": null,
"user_id": null,
"work_station_id": null
},
"exception_details": {
"application_name": "NITIB_TCC_BRK_GEN_PCMS",
"date_time": "2020-02-27T15:21:37.926+04:00",
"status": "F",
"error_code": "EAI-PCM-BRK-000",
"error_description": "Success"
},
"body": {
"Transaction_Details": [
{
"card_no": "XXXXXXXXXXXXXX",
"expiry_date": "XXXX",
"wallet_id": "XXXXXXXX",
"transaction_code": "0401",
"source_channel_type": "0120",
"wallet_balance": "000000000000",
"transaction_local_date": "20200225",
"transaction_local_time": "111615",
"posting_date": "20200225",
"retrieval_reference_number": "000000000002",
"transaction_amount": null,
"TransactionCurrency": null,
"TransactionNarration": "Balance Inquiry",
"AuthIdResponseCode": "575102",
"BillingAmount": null,
"BillingCurrency": "784",
"SettlementType": null,
"MerchantNameLocation": " "
},
{
"card_no": "XXXXXXXXXXXXXX",
"expiry_date": "XXXX",
"wallet_id": "XXXXXXXXXX",
"transaction_code": "0401",
"source_channel_type": "0120",
"wallet_balance": "000000000000",
"transaction_local_date": "20200227",
"transaction_local_time": "121251",
"posting_date": "20200227",
"RetrievalReferenceNumber": "000000000026",
"transaction_amount": null,
"TransactionCurrency": null,
"TransactionNarration": "Balance Inquiry",
"AuthIdResponseCode": "575224",
"BillingAmount": null,
"BillingCurrency": "784",
"SettlementType": null,
"MerchantNameLocation": " "
}
]
}
}
}
}
Docs Navigation
- API Security
- Falcon Services
- Card Services
- BETA
- Version 1.0
- Card Balance Enquiry
- Card Activation
- Card Set Pin
- Card Change PIN
- Card PIN Verification
- Card Status Update
- Card Limit Update
- Card Details
- Customer Details
- List Of Cards
- Customer Demographic Update
- Card Used Limits
- Card Statement Summary
- Card Transaction
- Utility Payments
- Account Create
- Account Update
- Account Closure
- Card Create
- Card Update
- Card Replacement
- Client Create
- Client Update
- Transaction Details
- PIN Retries Counter Reset
- Digital Status Chnage
- Get CVV2 Service
- Card Link Delink
- Card Insurance Products
- Card Change Insurance Product Status
- Card Direct Debit
- Update Card Direct Debit
- Card Balance Conversion Enquiry
- Card Balance Conversion
- Card Transaction Eligibility
- Card Transaction EPP Conversion
- Card Replacement Embossing
- Card NMON Transactions
- Retail Banking Transactions
- Appendix 1
- Appendix 2
- Appendix 3
- Appendix 4
- HTTP Codes
- Error Codes
- Version 2.0
- Lookup Card Identifier
- List Of Cards
- Card Activation
- Card Set PIN
- Card Change PIN
- Card Status Update
- Client Create
- Account Create
- Card Create
- Customer Demographic Update
- Account Update
- Card Update
- Card Replacement
- Customer Details
- Card Details
- Client Update
- Card Balance Enquiry
- Card Transaction
- Card Limit Update
- Card PIN Verification
- PIN Retried Counter Reset
- Get CVV2 Service
- Card Verification
- Card Transaction Details
- Get Encryption Certificate
- Get Dictionaries MCC
- Get Account Balance
- Card Insurance Product
- Card Insurance Product Update
- Card Direct Debit Update
- Card Direct Debit
- P2P Transfer
- Account Transaction
- Account Status Change
- Card Statement Summary
- Account Transaction Details
- Card Contact Details
- List of Accounts
- Account Hierarchy
- Notification Service
- Appendix 1
- Appendix 2
- Appendix 3
- Appendix 4
- HTTP Codes
- Error Codes
- Buy Now Pay Later
- Card Limits
- Insurance Services
- Webhook Services
- Switch Services
- Card Control Services
- Merchant Digital Onboarding
- Notification Service
- SMS Security Services
- Terms and Condition
0 Comments
Please sign in to post a comment.