Card Services
Overview
Our card services support multiple card types, including Visa, MasterCard, American Express, and Discover, as well as other popular payment methods like Apple Pay and Google Pay. You can also set up recurring payments for your customers, making it easy for them to make regular payments without having to enter their card information every time.Our advanced fraud detection and prevention features use machine learning algorithms to help identify and prevent fraudulent transactions. We also provide detailed reporting and analytics, allowing you to track and analyze payment data and make data-driven decisions.
We also offer multi-currency support, which allows you to accept payments from customers in different parts of the world. And with our 24/7 customer support, you can always count on us to help you resolve any issues related to our card services.Our card services are also fully compliant with all local and international regulations, such as PCI DSS, so you can be confident that you're accepting payments in a secure and compliant manner.
Card Replacement (Post)
This webbook serves to promptly inform your system whenever a card replacement occurs. This helps ensure that important card management activities are communicated accurately and on time. Card replacements are crucial in banking because they affect customer accounts, security, and transaction abilities.
Pin Action (Post)
This webbook serves to promptly inform your system whenever there are PIN-related actions performed on a card. It's important for maintaining card security, overseeing operations, and meeting regulatory requirements in finance. PIN-related actions, as of now we support reset pin counter only.
Card Statement Summary
Status:
Production
Version:
V2
Category:
Card Services
Card Statement Summary
Overview
This API allows developers to retrieve transaction history for a specific card. It requires one of the supported card identifier as an input and returns all transaction details within a specified date range. The API connects to the card issuer's management system and retrieves the transaction history for the provided card number. The returned information includes details such as transaction amount, merchant name, and transaction date. API has capability to list posted transactions, authorized transactions or statement transactions
Transaction history retrieval
The primary feature of this API is its ability to retrieve transaction history for a specific card. It allows developers to easily access a cardholder's transaction history within a specified date range, providing them with the information they need to display the transaction history to the customer or for internal purposes.
Date range filtering
The API allows developers to specify a date range when retrieving transaction history, providing them with a more targeted and relevant set of information. This feature is particularly useful for businesses that need to monitor transaction activity over a specific period of time.
Secure data transfer
The API uses standard HTTP protocols to receive the request and return the response and it also uses the necessary authentication credentials such as an API key, which provides an additional layer of security to protect the cardholder's information.
How It Works
The customer initiates a statement summary request through the payment processing company's website or mobile app, using the Card Statement Summary API. The payment processing company verifies the customer's identity and retrieves the statement summary for the requested time period. The payment processing company returns the statement summary to the customer through the website or mobile app, allowing the customer to view a summary of their card activity and spending. The customer can use the Card Statement Summary API to review their spending and manage their finances, providing a convenient way to stay on top of their finances.
Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
Card Statement Summary
Status:
Production
Version:
V2
Category:
Card Services
Node | Child Node | Type | Length | Description |
---|---|---|---|---|
Authorization | Bearer xxxx | string | Authorization Header (Bearer Token) | |
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
header | msg_id | string | 12 | CardStatementSummaryHeader | ||||||
msg_type | string | 12 | Request Type Default ENQUIRY | |||||||
msg_function | string | 50 | Function name to be used Default REQ_CARD_STATEMENT_SUMMARY | |||||||
src_application | string | 10 | Source requesting channel Ex IVR | |||||||
target_application | string | 10 | Target application name Ex PCMS | |||||||
timestamp | string | 30 | Timestamp of the request Format DD/MM/YYYY HH:MM:SS | |||||||
tracking_id | string | 30 | Transaction Tracking Id | |||||||
bank_id | string | 4 | Source Bank Id Ex bankID | |||||||
body | card_identifier_id | string | 32 | card identifier | ||||||
card_identifier_type | string | 20 | CONTRACT_NUMBER or EXID | |||||||
statement_period | string | 4 | Format MMYY (Maximum statement is 12 months from the current date) |
{
"NISrvRequest": {
"request_card_statement_summary": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "REQ_CARD_STATEMENT_SUMMARY",
"src_application": "IVR",
"target_application": "PCMS",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"tracking_id": "236001",
"bank_id": "NIC"
},
"body": {
"card_identifier_id": "99984100148297467162",
"card_identifier_type": "EXID",
"statement_period": "0323"
}
}
}
}
Node | Child Node | Type | Length | Description |
---|---|---|---|---|
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvResponse | response_card_statement_summary | header | msg_id | string | 12 | Message ID, this field should be unique id for each Api call. This will be generated from client side. If the same message ID is used the system will decline the API call with Error Description “Duplicate Message ID” | ||||
msg_type | string | 12 | Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY” | |||||||
msg_function | string | 50 | Static Value - RES_CARD_STATEMENT_SUMMARY | |||||||
src_application | string | 10 | Source Application: This is a free Text and the client can populate the source system from where the API is Initiated Example: IVR, IB, MB No Validations of these are kept at Network Systems | |||||||
target_application | string | 10 | The target_application can hold any value from FI side, this can be used by FI to check the target system of the API call | |||||||
timestamp | string | 30 | Timestamp of the response Date & time Format DD/MM/YYYY HH:MM:SS | |||||||
bank_id | string | 4 | Bank Id is Unique Id 4 digit code for each client and the same will be provided once the client setup is completed in our core system. For sandbox testing – Please use “NIC” | |||||||
exception_details | application_name | string | 20 | Application Name | ||||||
date_time | string | 30 | Timestamp of the response Format “YYYY-MM-DD HH:MM:SS” | |||||||
status | string | 1 | Status of the request (S/F) | |||||||
error_code | string | 4 | EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
error_description | string | 100 | Error Description (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
transaction_ref_id | string | 20 | The tracking_id sent in the request will be sent back in response in this field. | |||||||
body | card_identifier_id | string | 32 | 454545XXXXXX1234 | ||||||
card_identifier_type | string | 20 | CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS | |||||||
statement_period | string | 4 | Statement period for the card statement summary ..Maximum statement is 12 months from the current date | |||||||
statement_details | statement_date | string | 10 | Billing Date | ||||||
last_statement_date | string | 3 | Last billing date | |||||||
statement_opening_balance | string | 20 | Statement Opening balance | |||||||
statement_closing_balance | string | 20 | Statement Closing balance | |||||||
due_amount | string | 20 | Due amount | |||||||
due_date | string | 10 | Statement due date in format YYYY-MM-DD | |||||||
full_payment_amount | string | 20 | Full payment amount/interest free amount | |||||||
interest_this_statement | string | 20 | Interest amount in selected statement | |||||||
statement_available_balance | string | 20 | Available amount at the time of statement | |||||||
reward_programs | reward_type | string | 3 | Reward type | ||||||
reward_open_balance | string | 3 | Reward open balance | |||||||
reward_balance | string | 20 | Reward balance on the current billing cycle | |||||||
reward_earned | string | 20 | Reward earned points on the current billing cycle | |||||||
reward_redeemed | string | 20 | Reward redeemed points on the current billing cycle | |||||||
reward_adjust | string | 20 | Reward adjust points on the current billing cycle | |||||||
reward_total_earned | string | 20 | Reward earned points on the current billing cycle |
{
"NISrvResponse": {
"response_card_statement_summary": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "RES_CARD_STATEMENT_SUMMARY",
"src_application": "IVR",
"target_application": "CMS",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"bank_id": "NIC",
"instance_id": "InstanceID"
},
"exception_details": {
"application_name": "TCC-ADP",
"date_time": "2023-02-01T16:39:47.314+04:00",
"status": "S",
"error_code": "000",
"error_description": "Success"
},
"body": {
"card_identifier_id": "454545XXXXXX1234",
"card_identifier_type": "CONTRACT_NUMBER\/EXID",
"statement_period": "string",
"statement_details": {
"statement_date": "15\/12\/2021",
"last_statement_date": "",
"statement_opening_balance": "0.00",
"statement_closing_balance": "-6000.00",
"due_amount": "-900.00",
"due_date": "05\/01\/2022",
"full_payment_amount": "-6000.00",
"interest_this_statement": "0.00",
"statement_available_balance": "",
"reward_programs": [
{
"reward_type": "",
"reward_open_balance": "",
"reward_balance": "",
"reward_earned": "",
"reward_redeemed": "",
"reward_adjust": "",
"reward_total_earned": ""
}
]
}
}
}
}
}
Code | Description |
---|---|
200 | Sample Description |
400 | Bad Request |
401 | Unauthorized |
403 | Forbidden |
500 | Internal Server Error |
502 | Bad gateway |
503 | Scheduled Maintenance |
504 | Gateway Timeout |
596 | Service Not Found |
How It Works
Follow the steps below. For more details, read the Quick Start Guide.
1- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
2- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
3- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
4- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
5- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.