# IQ release notes

### Changes in Upcoming Release

* Fix for wallets exceeded top up limit.&#x20;
* Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.

### Release Notes (13/05/2026)

* Introduced several new APIs for Visa Click to Pay. It is a tokenized, EMV® Secure Remote Commerce-based solution designed to streamline and secure online checkout for cardholders, merchants, and issuers. For more information, refer to this [API Catalog](https://portal.stg.platform.ae-1.nymcard.com/default/documentation/02_api_specs#tag/Visa-Click-to-Pay/operation/listClickToPayEnrollments)
* Fix for the Bill Payment transaction display on PMD.
* Enable Maker/Checker (4-Eyes) for Unload Funds. This enables no single user can debit customer accounts without a second authorized approval.
* Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.

### Release Notes (29/04/2026)

* Changes in linking multiple merchant lists to card and card product - V2  [`Merchant allowed APIs`](https://portal.stg.platform.ae-1.nymcard.com/default/documentation/02_api_specs#tag/Allowed-Lists/operation/getAllowedMerchant) [`Merchant Link/Unlink APIs`](https://portal.stg.platform.ae-1.nymcard.com/default/documentation/02_api_specs#tag/cards/operation/linkAllowedMerchantsToCardV2) [`Card Product Link APIs`](https://portal.stg.platform.ae-1.nymcard.com/default/documentation/02_api_specs#tag/card-products/operation/unlinkAllowedMerchantsFromCardProductV2)&#x20;
* Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.

### Release Notes (15/04/2026)

* Added backend support for mobile app banner.
* Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.

### Release Notes (01/04/2026)

* Added new 'card\_product\_id' parameter in the response of the Card Listing API, so that you can identify the product associated with each card and apply relevant product-specific logic or UI behaviour.
* Updated existing MASTER wallets to set IQD as priority 1 and USD as priority 2 in order to normalize wallet priorities for existing users who have both IQD and USD MASTER wallets.
* Enhanced card search capabilities in the mobile application to allow users to search their own cards securely, enable searching recipient cards using specific identifiers, restrict visibility to only eligible (Active) cards etc..
* Added backend support for mobile app banner.
* Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.

### Release Notes (18/03/2026)

* Added enhancement to nFront to fall back to 'transaction\_currency' and 'transaction\_amount' when 'billing\_currency' and 'cardholder\_billing\_amount' are missing,\
  so that the app always shows the correct currency and amount even for reversal advice messages where billing fields are not present.
* Added enhancement to Virtual Card PAN Generation.
* Implemented backend support for Areeba Payment Gateway (ARPG), including new source channel handling, Transfers API updates, CMS-level integration, and forex logic.
* Enhanced the PIN retry counter (now it is set to 5 attempts).
* Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nymcard.com/get-started/release-announcements/iq-release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
