Announcements

The Announcements page is your go-to source for the latest updates, news, and important information. It includess details on software releases, policy updates, maintenance schedules, and special events. Stay informed by checking this page regularly.

Enhancements Implemented in LIVE:

Endpoint Name Description of Change Sample Release Date
Corporate Send Money – API V2 Corporate Salary Payments (B2C) have been enabled in API V2. The API now supports both Customer-to-Customer (C2C) and Business-to-Customer (B2C) transaction processing. API References → Corporate Sender → Initiate Transaction V2 Live
Confirm a Transaction **Input Fields:** nationality countryOfBirth countryOfResidence Beneficiary ID-placeOfIssue Previously, any two characters could be entered; this will now be restricted to valid ISO codes only. **Before:** For Pakistan, "nationality" - PT could also be passed. **After:** "nationality" - Only PK will be accepted. Live
Create a Transaction **Input Fields:** Remitter ID-placeOfIssue Beneficiary ID-placeOfIssue Previously, any two characters could be entered; this will now be restricted to valid ISO codes only. **Before:** For UAE, "Remitter ID-placeOfIssue" - UA could also be passed. **After:** "Remitter ID-placeOfIssue" - Only AE will be accepted. Live
Create Transaction 1. Beneficiary Nationality - Should be ‘Pakistan’ for Pakistan account transfers (same bank transfer and third-party transfer). 2. Purpose of Remittance - Should be “Family Maintenance” for Pakistan account transfers (same bank transfer and third party transfer). 1. "nationality" = "Pakistan" 2. "remittancePurpose" = "Family Maintenance" LIVE
All relevant methods where the country code is accepted. 1. A new parameter 'payoutCurrency' ‘is added as a mandatory parameter wherever ‘destinationCountry’ is mandatory, in all relevant methods. 2. Only standard ISO codes and the corresponding payout currency will be accepted, and no dummy codes will be accepted. 3. If ‘destinationCountry’ parameter is optional, then ‘payoutCurrency’ is also optional. However, if ‘destinationCountry’ value is entered then payout currency should be mandatory. 4. In all the relevant methods (as listed below) wherever ‘destinationCountry’ is a part of the response, only standard ISO codes will be returned and no dummy codes. E.g., For Uganda payout in
USD or UGX (local currency): "destinationCountry" - UG "Payout Currency" - USD or "destinationCountry" - UG "Payout Currency" - UGX
LIVE
Create Transaction optional parameters become mandatory if Receiving Country=Oman and Delivery mode=4: Beneficiary ID Type
Beneficiary ID Number Beneficiary ID Issue Date Beneficiary ID Expiry Date
"primaryId": {
"type": 11, "number": "IN123TEST", "issueDate": "2000-01-01", "expiryDate": "2030-01-01",
Live
Create Transaction optional parameter "City" becomes mandatory in Remitter and Beneficiary "Address" object for all countries "city": "Delhi" Live
Create Transaction optional parameter "District" becomes mandatory in "Address" object if Receiving Country=BD, Delivery Mode=7, Remitter/ Beneficiary Nationality=BD "district": "Bagerhat" Live
Get Outstanding Remittance new field in response body: "SourceOfFundCode" "sourceOfFunds": "Business",
**"sourceOfFundCode": 1**
Live
Get Outstanding Remittance new fields in response body: "Settlement Currency"
"countryOfBirth" (Remitter)
"settlementCurrency": "AED"
"countryOfBirth": "PK"
Live
Get Outstanding Remittance new field Remitter "cardNo" in response body, if Receiving Country=AE "cardNo": "646464" Live
Get Outstanding Remittance values for the following parameters to be displayed: 1. Fields for AE: Remitter ID type, Remitter ID number, Remitter country of birth 2. Fields for NP: Remitter Mobile Number, Remitter ID type, Remitter ID number, Relationship with Beneficiary, Source of Fund 3. Common fields "type": 11,
"number": "IN123TEST" "countryOfBirth": "IN" "relation": "HUS"
Live
Receive Payment new field in response body: "SourceOfFundCode" "sourceOfFunds": "Business",
**"sourceOfFundCode": 1,**
Live
Receive Payment new fields in response body: "Settlement Currency"
"nationalityCountryCode" (Remitter/Beneficiary) "countryOfBirth" (Remitter)
"nationality": "BANGLADESH",
**"nationalityCountryCode": "BD"** "settlementCurrency": "AED" "countryOfBirth": "PK"
Live
Receive Payment new field Remitter "cardNo" in response body, if Receiving Country=AE "cardNo": "646464" Live
Receive Payment values for the following parameters to be displayed: 1. Fields for AE: Remitter ID type, Remitter ID number, Remitter country of birth 2. Fields for NP: Remitter Mobile Number, Remitter ID type, Remitter ID number, Relationship with Beneficiary, Source of Fund 3. Common fields "type": 11,
"number": "IN123TEST" "countryOfBirth": "IN" "relation": "HUS"
Live
Create "dummy" transaction New Sandbox endpoint is solving the issue of Receiving Partners who need to call several endpoints on the sending side for testing receiving endpoints. Therefore, a Receiving Partner can call "Create Dummy Transaction" without populating the standard "Create Transaction" payload. To do this, the Receiving Partner would need to execute the following steps: 1. Prepare API headers 2. Select endpoint: {{baseUrl}}/api/v1/simulations/transactions/initiate. 3. Press "Send" with: - Option 1: An empty body request. Sample: `{ }` - Option 2: A request with a minimal set of data (including delivery mode). 4. Retrieve a response - a transaction created with an ICTC number. {
"payingAgent": "PK01RH", "targetCurrency": "PKR", "targetAmount": 0, "sourceAmount": 100, "sourceOfFund": "Salary", "deliveryMode": "7", "remittancePurpose": "16" }
Live
Partner Support System endpoints The Partner Support System (PSS) is designed to help our Partners seamlessly incorporate our request management capabilities into their application. PSS consists of 3 endpoints: - Post Request - Track Request - Attend Request [More information ](https://docs.instantcashworldwide.com/docs/partner-support-system-pss) Live

Upcoming Enhancements:


Endpoint NameDescription of ChangeSampleRelease Date

Please note that these changes are subject to refinement as we approach the release date. We encourage you to regularly check this section for the latest information and prepare for a smooth transition.