Release announcements
Last updated
Was this helpful?
Last updated
Was this helpful?
Added a new ‘transfer_type' enum within the 'filters' parameter in '’ API.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Added new parameters, 'dry_run' and 'transaction_type,' to the '' API. These parameters allow you to control whether a quotation is stored in the system and define the type of transaction being processed.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Improvements
Bug fixes
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Changed the length of the 'first_name' and 'last_name' parameters from 40 to 60 characters in the Users APIs to accommodate users with longer names during registration.
Added new 'native_last_name' parameter to Users APIs, so that user's last name can be stored in native language.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Improvements
Added the receiver_user_id field to several transaction and transfer APIs, as well as to the webhook TRANSACTION event, allowing you to easily identify the beneficiary of transfers.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Improvements
Bug fixes
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
We've made improvements to our Courier Reports by including information on delays. This addition is designed to provide clients with insights into the reasons for delayed card deliveries, giving them the ability to address issues independently and bypass the need to raise tickets for resolution.Column Name: "Reason of Delay".
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Two new APIs have been developed: "Get advanced velocity limits related to card product" and "Get advanced velocity limits linked to card." These APIs allow you to retrieve a list of advanced velocity limits for a specific card product or card.
The "Change user status," "Change card status," and "Change account status" APIs now include a new optional parameter called "modified_by." This parameter helps identify the user who executed the operation.
Several internal enhancements have been implemented, which do not significantly impact the current implementation for clients.
Implemented several internal enhancements, which have no major impact on client's current implementation.
Added a new global setting related to abandoned tokens for VISA tokenization service, ensuring that webhooks are generated when a user does not complete the provisioning process within the allowed timeframe (24 hours).
Implemented several internal enhancements, which have no major impact on client's current implementation.
For digital wallets (ApplyPay, SamsungPay & GooglePay), a user is limited to a maximum of 10 tokens per card from the respective wallet providers (Terminated tokens are excluded).
Please be aware that transfers, load/unload, DAPI, and LEAN direct API flow will be declined if either the sender's or recipient's user status is not ACTIVE.
Take into account that a card is temporarily blocked for 24 hours for provisioning if the user makes five consecutive invalid CVV2 or expiry attempts.
Implemented several internal enhancements, which have no major impact on client's current implementation.
From now on, notifications for 'near expiry'/'expired' documents will be triggered only for Onfido documents. USER_DOCUMENT_ALERT webhook is used for this. For documents added via the upload APIs, it will be handled in upcoming releases.
Implemented several internal enhancements, which have no major impact on client's current implementation.
Implemented several internal enhancements, which have no major impact on client's current implementation.
Added several new optional parameters to the 'Users' APIs, so that you can store and get this information against each user:
new field "education_level"
new field "nearest_place" under existing object "address"
new field "nearest_place" under existing object "company_address"
new field "created_by" (unique ID of the agent who will be onboarding the INDIVIDUAL user)
Added a new field 'is_cancelled' in TRANSACTION webhook to indicate whether the auth transaction is cancelled and funds are credited back to cardholder (needed for a new payment scheme to be supported).
Implemented several internal enhancements, which have no major impact on client's current implementation.
Added new enums ‘ADDITIONAL_PAGE_1' & 'ADDITIONAL_PAGE_2' for 'file_identification_document_type’ parameter in User Identification APIs, so it can be stored and returned for uploading identification files. Note, that 'file_identification_document_type' remains optional for 'file_identification_type' : ADDITIONAL.
Implemented several internal enhancements, which have no major impact on client's current implementation.
DAPI direct API flow enhancement: Upon calling DAPI flow with HOLD transaction type, a proper error message is returned in case of insufficient funds in the pool account (error: Prefunded account has insufficient funds).
Implemented several internal enhancements, which have no major impact on client's current implementation.
Implemented several internal enhancements, which have no impact on client's current implementation.
Implemented several internal enhancements, which have no impact on client's current implementation.
Enhancements:
Transactions / Webhooks: Added two new fields in TRANSACTION webhook for Incremental Authorization:
Scheme Transactions: Transaction processing (authorization) is influenced by the below two settings being set to "false" at the system level. Meaning, regardless of the assigned value (true or false) at product or card level, the corresponding transaction will not be approved.
Account Termination: Added account termination rule: If an auth is partially reversed and its clearing is not received yet, then that particular auth is considered to be a pending auth and therefore, the account cannot be terminated. Bug-fix:
Implemented several other internal enhancements, which have no impact on client's current implementation.
Implemented several internal enhancements, which have no impact on client's current implementation.
Developed four new APIs to manage external bank account details so that these details can be used to execute the external transfers:
Implemented enhancement for MPGS - whenever a session or transacting is created via MPGS, a proper fintech name will now appear instead of“NymCard Payment LLC” as a merchant name.
Features and improvements:
Implemented enhancement for DAPI smart flow - now system supports 'note' field in URL parameters for transfer funds through DAPI widget so that you can pass 'note' as a customized information.
Features and improvements:
Fixed an issue when cardholder "enc_name" was displayed on the PCI widget instead of "name_on_card".
Fixed an issue when issuer fees were charged for the refunds transactions.
Features and improvements:
Features and improvements:
Fixed an issue with fees - fee in declined transactions is now returned in 'Get transaction details' and 'Search transactions' API responses and in 'TRANSACTION' webhook.
Features and improvements:
A new "status_reason_code" - "O1" (reason: Other) is now supported for user status change. It is used by our internal APIs to clarify user status change to SUSPENDED or TERMINATED in case the reason is other than the ones we already support in our API Catalog.
Fixed an issue when wallet transfer was declined with max amount limit reached.
Fixed an issue when ‘status_reason_code’ parameter was missing in TRANSACTION webhook for WALLET_TRANSFER ‘transaction_type’ for declined MPGS transaction.
Fixed an issue when user with CLEAR report from Onfido was changed to B1 status.
Fixed an issue when user report was not retrieved in user IDV report APIs.
Features and improvements:
Fixed an issue with MPGS credit card transaction, when amount deducted from credit card was not the same amount credited to NymCard account.
Fixed an issue when 'user_type' was missing in the 'User status change' webhook received upon changing user status from "PENDINGIDVERIFICATION "B4" to "PENDINGKYC" "I0" or "ACTIVE" "I0".
Fixed an issue with changing user status from ACTIVE to PENDINGKYC.
Fixed an issue with constraint violation when performing KYC.
Fixed an issue when users were not moving to World check during performing KYC.
Features and improvements:
Features and improvements:
Fixed an issue when card ID was missing in the 'TRANSACTION' webhook for declined transactions.
Fixed an issue when ‘CARD_STATUS_CHANGE’ webhook was not received upon changing the card status to ‘SUSPENDED’ due to max. number of pin retries attempts.
Features and improvements:
Added ability for system to generate export after processing the clearing file so it can be shared for reconciliation. Please contact the customer success team for details.
Implemented enhancement regarding webhooks: from now onwards 'original_amount_billing' parameter will be forwarded only in Reversal_advice webhooks, as it is only required for partial reversal cases.
Restricted user status change from ACTIVE to PENDINGIDVERIFICATION (B0 or B2) using 'Change user status' public/internal API.
Main features and improvements:
Developed and implemented core enhancements to the Card Product management process. Once a Card is created, its "Auth Settings" - inherited from its Card Product - cannot be changed. For any questions or concerns, please reach out to our Support or Customer Success teams.
Fixed an issue with missing fields in clearing webhooks. Now the following fields can be sent in clearing webhooks: “userid”, ”feeamount”, "ecommercesecuritylevel”, "cardentry", "posenvironment", "fallback", "pinpresent", "moto", "recurring", "installmenttransaction".
Fixed an issue when 'status_code' was not received in the negative/declined cases of webhooks with "event": "TRANSACTION", "message_type": "API" and "transaction_type": "WALLET_TRANSFER".
Main features and improvements:
Bug fixes:
Minor bug fixes and performance improvements.
Main features and improvements:
Bug fixes:
Fixed a lot of internal issues.
Main features and improvements:
Bug fixes:
Fixed a lot of internal issues.
Main features and improvements:
Bug fixes:
Fixed a lot of internal issues.
Main features and improvements:
Bug fixes:
Fixed a lot of internal issues.
Main features and improvements:
Bug fixes:
Fixed a lot of internal issues.
Main features and improvements:
Bug fixes:
Fixed an issue when user KYC call could be performed without uploading an identification or with uploading the wrong identification type.
Fixed an error which occurred upon changing card status.
Fixed an issue when 'ledger_balances' parameter was empty during account creation.
Main features and improvements:
Implemented changes to support the new industry standard – eight-digit issuing BIN.
Bug fixes:
Fixed the issue with duplicated BIN & PAN range during card product creation/update within the tenant.
Fixed the issue which occurred when performing KYC for users with 'status' = PENDINGIDVERIFICATION.
Fixed the issue with webhooks response time.
Main features and improvements:
Bug fixes:
Fixed an issue when used card PIN did not conform with PIN length defined at card product level.
Fixed an issue when duplicate webhook notifications were received for load transactions.
Fixed an issue with an informative error message upon trying to link a bulk card to an inactive user.
Fixed an issue when user KYC status for secondary users could not be changed.
Main features and improvements:
Implemented the following enhancements to the open banking widget, which helps to transfer funds from your bank account to your NymCard card account:
added a button to delink a bank
implemented handling of returned error codes
added ability to re-link the bank again in case the user has changed its banking credentials.
Bug fixes:
Fixed the following issues with the widget, which helps to transfer funds from your bank account to your NymCard card account:
added error message showing upon transferring funds to a suspended/terminated account
fixed authentication error message
fixed the issue when cool-down period icon overlapped with the text
fixed the cool-down page draft
updated main page draft
fixed 'Top Up completed' page
improved user experience when it comes to navigating back to the main page.
Fixed issues related to PCI Widget, regarding set/change PIN functionality in particular.
Fixed an issue when KYC status could not be updated for users with 'SECONDARY KYC' policy.
Fixed an issue with special symbols when adding addresses in 'Create card' API. Now you can also use the following symbols: comma, semicolon, colon, apostrophe.
Fixed an issue related to receiving webhook notifications with “event”: “IDENTITY_VERIFICATION” when tenant settings checks=‘FACIAL_SIMILARITY_VIDEO’.
Main features and improvements:
NymCard offers a possibility to transfer funds from your bank account to your NymCard card account using the widget. For more information refer to the ‘Funding and transfers’ section of our Getting Started guide.
Added ability to view and change card PIN using PCI widget, so cardholders can change or view the PIN which is required to perform cash withdrawals at the ATM or POS purchases with a physical card. For more information refer to the ‘Security’ section of our Getting Started guide.
Mandatory fields on the NymCard dashboard are now marked accordingly.
Conducted a reset on the NEO Admin Panel Dashboard.
Bug fixes:
fixed an issue with change of commission fees on Asia Cell and Toters.
Fixed BIN rerouting for several clients.
Fixed an issue when an error occurred while linking a bulk card to a user.
Fixed Onfido integration issues.
Added new status reason codes to ' APIs - S10 (Suspended by Host via automatic external creation) and A10 (Active, not verified by Host).
Implemented a new '' API, which allows you to retrieve the data of tokenized cards.
Added a new 'design_code' parameter to the APIs. This parameter enables a card to be printed with the design selected by the user when requesting the card.
Added a new “” API, which allows you to return advance fees against several specific parameters.
Added a new '' section to API catalog, which includes bunch of new APIs. It gives a possibility to integrate with Mastercard Cross-Border Services to conduct remittances. The Cross-Border Service APIs enable financial institutions and partners to build flexible solutions that support many different funds transfer and payment types via a single connection to Mastercard.
Added 'balances' parameters to the webhook TRANSACTION event, allowing you to easily identify the balances information. A sample webhook can be found .
Added a new 'auth_id_response' parameter to the nFront "" API, which is used for Unionpay 'cancellation' transaction type.
Added new '' API, which allows you to retrieve the details of all available limits associated with an account.
Added new status reason code S9 (Suspended by Host) to ' APIs.
Added a new webhook event, 'SUCCESSFULLY_CREATED', which notifies you whenever an account or card is successfully created. A sample webhook can be found .
Introduced a new "" API, allowing the card’s soft expiry to be updated with configurations available at the card product level. We've also added the parameters soft_expiry_update_allowed and soft_expiry_setting for card product APIs.
Added 2 new token lifecycle management APIs - for and .
Added the ability to request an FX rate quote for provider_type = EXTERNAL. For this we've introduced several new parameters (amount_type, derived_rate and final_rate) in the "" API request.
Introduced support of card activation charges. For this we added a new 'charge_type' - "CARD_ACTIVATION_CHARGES" in 'Create charge' API. For more information about charges refer to this .
Added '' API, which is used to search webhooks by different criteria.
Added enhancement for advanced velocity limits - now you can create an advanced velocity limit with two extra conditions: "TRANSACTION_ORIGIN" (DOMESTIC, FOREIGN, ANY) and "CARD_TYPE" (VIRTUAL, PHYSICAL). Relevant are added to the 'type' parameter in 'CONDITIONS' array.
Added a new "recipient_account_id" parameter in '' API. This parameter is used for fund transfer between accounts of different wallet currencies.
Implemented an enhancement to our multi-clearing process, designed to improve security and prevent negative balances in cardholder accounts. For more information refer to this .
Implemented advanced fees functionality. It allows fees configuration along with the dynamic conditions so that fees can be applied based on the configured conditions. For this we developed several new APIs. For more information refer to this .
Implemented new enums for the "transfer_type" parameter, enabling the system to differentiate whether a transfer occurs between the user's OWN account/wallet or not. For more information refer to this . Also added a new "transfer_type" field in TRANSACTIONS .
Added a new "consumed_limit" and "consumed_frequency" fields for velocity limits and advanced velocity limits in the response of '' API.
Introduced a new "allow_overdraft" field in APIs, the default value is 'false'.
Added a new "allow_initial_load" field in "auth_settings" and "currency_settings" of a with default value of 'false'.
Introduced a new "allowed_load_type" parameter under "wallet_details" in APIs.
Added a new parameter "group" with a default value of "SINGLE" in APIs.
A new webhook event, "ACCOUNT_STATUS_CHANGE," has been added. This event allows you to be notified whenever the account status changes, enabling you to take appropriate action. A sample webhook can be found .
New status reason codes (A3, S3 to S6, T7 to T18) introduced in the Cards resource (to be utilized by NymCard). Refer to the for more details.
A new API "" developed to fetch the limits associated with the card.
Enhanced functionality: clients can now create SMS templates based on wallet providers. Please be aware that the "wallet_provider" field is specifically applicable for the ITSP_OTP category type. The available enums for "wallet_provider" include APPLEPAY, SAMSUNGPAY, and GOOGLEPAY. Additionally, clients have the option to add a custom email OTP template using a new "email" parameter. For detailed information refer to the "" section in our API catalog.
Now clients can define new placeholders - CARD_NAME, FINTECH_NAME to use in SMS text in APIs. It is applicable for ITSP_OTP category only. CARD_NAME placeholder will read from the description field of the card product to which the card belongs.
"quote_id" field (if available) is now returned in the response of ' and '' APIs.
"transaction_id" field is now returned in the response of '' and '' APIs (applicable when status of the quote is BOOKED).
Introduced new "card_type" field (with enums PHYSICAL, VIRTUAL) for APIs, so now you can create both physical and virtual bulk cards.
Added two new enums (TRANSFER_TYPE & PURCHASE_TYPE) in 'conditions' array 'type' parameter in APIs, so now there is an option to configure separate velocity limit for TRANSFER_TYPE and PURCHASE_TYPE.
Introduced support of custom fields in APIs to add some additional fields as per business needs. Custom field object will be returned in the response of APIs.
Added a new "reference_number" field to the response of and APIs. This field is intended for reporting needs.
Added a new '' API to enable the validation of user PINs through an API. This modification has no impact on clients' integrations.
Added changes to ; below you can find new fields related to card tokens:
Added ability to configure advanced velocity limits, which allow you to add additional configurations such as merchants (i.e. categories or identifications) in velocity limit profile, so that you can configure velocity limit profile that is applicable for specified configuration. You can find related APIs .
Added 2 new parameters 'charge_type' and 'ids' to '' API, so now you can fetch charges list by charge type or charge IDs.
Onboarding / User Verification: Know which IDV/KYC provider is being assigned and to which category or check. For that purpose, a has been developed to retrieve some information related to user verification settings. See the below example:
Cards & Accounts: Introduced new "is_account_linked" parameter in APIs to indicate whether the card is linked to an account or not.
Onboarding / User Verification: Users' documents of issuing country other than that of the issuer country is being verified and accepted. That explains the purpose of the new validation being implemented. To cater to that changes, new user status reason codes [“status_reason_code”: B9, B9E, B10, B10E] are introduced. A new validation has been implemented to verify if the issuing country of the identity document matches with the issuer country (system level). If not, user will remain in PENDINGIDVERIFICATION status and will take on status_reason_code of B9 in case Onfido report is CLEAR; Otherwise, it is a B10. For more info refer to this .
Business User Onboarding: Introduced new 'optional' fields in APIs for "user_type" = BUSINESS to capture related information for compliance reasons:
Users: Change in the length of "shareholder_list" field in APIs - now accepts up to 50 shareholder ids to be linked.
Users: Change in the length of "share_controller_name" field in APIs - accepts up to 100 characters now.
Card status correction: The correct "status_reason_code" I3 is now reflected in APIs for a card created without an account but with an embossing already generated.
Added a new field 'title' to APIs. It is used during identification creation and the system can store 'title' and return it with identification document information.
Introduced several new status reason codes regarding a mechanism for IDV re-verification for INDIVIDUAL users who are already verified but their documents have either expired or about to expire. For more info refer to .
Added multi-currency functionality. You can find details in this . Also you can find related APIs .
Introduced a new ‘type' parameter (with enums HOLD, POST & RELEASE), which gives ability to identify for which status the TRANSACTION webhook is triggered. It is added to the response of '' and '' APIs. Also, it will be added to Transaction .
"note" field is now returned in TRANSACTION webhook for "transaction_type": "WALLET_CREDIT" & "WALLET_DEBIT". You can find webhook samples .
Implemented several significant enhancements regarding Fees. For more information please refer to this .
Added six new APIs to manage charges, namely card issuance charges, which can be applied when physical or virtual cards are issued to cardholders for the first time. For more information regarding Charges refer to this .
Added a new "messageReasonCode" field to TRANSACTION (message_type = AUTHORIZATION, transaction_type = REVERSAL_ADVICE). This field explains why the acquirer is rejecting authorization.
Added an extra validation check on date of birth (DOB): DOB retrieved from Onfido should match the DOB in the user profile. For this we added a new enum to '' parameter - “B7” (Date of birth consider). Note, that B7 validation is skipped in case date of birth (DOB) is not present in the user profile.
Increased the size of the 'business_activities' field to 1000 characters in '' APIs.
"sender_user_id" parameter is now returned in the response of '' & '' APIs.
Added "sender_user_id" parameter to the response of '' API when searching for WALLET_TRANSFER transactions. Also, "sender_user_id" is added as a transaction search filter.
Added new enum for ‘status_reason_code’ parameter in '' API. New enum is C1 (INCONCLUSIVE). In case you receive this reason code, it means that the user account is on hold.
Fixed an issue with "allowed_mccs_id" parameter, which is now returned in the response of '' API.
Also be aware, that some enhancements will be added to API catalog later, when full features will be implemented. But these changes have impact on current implementation, so please get acquainted with all details in this .
Implemented several vital enhancements for MCC list management. We strongly recommend to get acquainted with all details in this .
Added 'auth_settings' parameter to responses of the following APIs: '', '' and ''.
Added new '' API, which is used to create an account token for external transactions that are initiated from third parties.
Added possibility to change 'allowed_mccs_id' parameter on a card level using ' API.
Implemented enhancement regarding webhooks - "sender_user_id" parameter is now received in TRANSACTION (for WALLET_TRANSFERS) . Also, "sender_user_id" is returned in the response of "' API when passing the ID of a WALLET_TRANSFER transaction.
Added a new parameter - “type” to the '' API. This field indicates the type of card product (value should be 'PREPAID'). Also it is added to the responses of ' and '' APIs.
Added ability to simulate (pre-defined successful) user’s status and to proceed for completing the user verification process ( for KYC and IDV) on the test environments (DEV, Staging, Sandbox, UAT). Also you can find the respective webhook changes in this .
Added "source_channel" & "notes'' parameters to responses of ‘’ and ‘’ APIs in order to get some additional transaction’s information. Also these two parameters are added to the sample of "TRANSACTION" .
Added ability to search and get the balance inquiry transaction details as well in addition to the other transactions. Also you can find a "BALANCE_INQUIRY" webhook sample .
Added a new webhook event - 'EXPIRED_AUTH',so now you can for expired authorizations to be aware whenever an authorization is expired by the system. Webhook sample you can find in this . Also four new related parameters “auth_expired_by“, “auth_expired_at”, “is_reversed“ and “is_settled“ are added to APIs.
Added ability to cancel bulk card issuance request: for this new enum "CANCELLED" is added to the 'status' parameter in '' APIs. Note, that this functionality can be used only when bulk issuance card request is in status "DRAFT". If the bulk issuance request is "SUBMITTED", then it can not be modified any more.
Added a new "fee_details" parameter in '' and ‘ APIs responses, so that you can have more detailed information of all associated charged fees. Also this new "fee_details" parameter is added to TRANSACTION .
Added a to the Getting started guide, where you can find examples of notifications, which you can use in SMS in '' API.
Added new ‘’ API, which gives an opportunity to see the customer’s identification report by ‘report_id’, so that you can get the detailed report information with possible respective failure reason details.
Added new ' API, which helps to generate encrypted card details so that you can use encrypted card details in VISA SDK inApp provisioning flow for tokenizing the card.
Increased file upload size from 20Mb to 128Mb for '' and '' APIs.
Added new KYC status reason code 'T0' to ' APIs, which informs when KYC process failed due to timeout or other technical issue on WC side. Upon receiving the T0 status for the KYC, you need to trigger perform KYC again.
Added new tags <MERCHANT_NAME> and <TRANSACTION_AMOUNT> which you can use in SMS in '' API (along with existing tags <CARD_LAST4_DIGITS> and <OTP>).
Changed length of the 'name_on_card' parameter from 32 to 20 characters in APIs so that same length can be matched with embossing export format.
Added new API, which helps to retrieve the list of balance limit ID(s) linked to the account.
Added new API, which helps to get the detail information of customer’s identification report.
Implemented enhancements for DAPI widget - now you can skip country and bank selection step and go straight to the credentials in case of adding/linking a new bank or to fund transfer step. For more details refer to the .
Added new 'billing_amount_account', 'billing_currency_account' and 'conversion_rate_billing_account' parameters to '' and '' APIs, so you can fetch billing currency and amount applied on the account and understand clearly in which currency the billing amount is charged.
Added ‘source_channel’ parameter to the APIs. Possible values are MPGS, DAPI or ANY (default). It gives an opportunity to choose an appropriate channel, so that fee for every channel can be applied accordingly. This parameter is currently applicable for ‘transaction_type’ = TRANSFERS only. Also added ability to post fee on recipient account instead of sender account, so you can charge the transfer funds fee to recipient instead of sender. For more details refer to the .
Fixed an issue with appropriate response code mapping regarding system errors. More info about transaction status codes you can find
Added ability to set balance limit on individual account by using a new API - ''. Also you can unlink balance limit from account using another new API - ''.
Increased file upload size from 5Mb to 20Mb for '' and '' APIs.
Implemented enhancement regarding '’ API: card auth settings inherited from the card product will be returned only for the newly created cards. For existing cards, after updating the auth settings at the card level and calling 'Get card authorization settings data' API, the auth settings will be returned in response.
Added an explanation that "company_name" parameter is required if "employment_type" = 'SALARIED", "EMPLOYED" or "BUSINESS_OWNER". It is applicable for APIs.
Updated the 'pin' parameter in the “ API - it is a string now. So, as an example, the format now is the following - "pin": "0190".
Added ability for PCI widgets to support ‘proxy_number’ along with ‘card_id’. You can read more about proxy number usage .
Added support of proxy number when . You can read more about proxy number usage .
Fixed an issue when 'card_id' was not returned in '' API response.
Added ability to link IDV verification policies for parent and child users at tenant level. In terms of this feature new are added to API catalog.
Implemented new name verification mechanism to match name fields of API and uploaded documents so that identity verification process can be smoothly completed. Also in terms of this improvement new user status reason codes were added to .
Updated ability to terminate accounts, so now it is possible to to TERMINATED if account has no balance or account has no pending authorizations.
Added such new parameters as 'soft_expiry_period' and 'card_soft_expiry', which give ability to define soft expiry of the card (the concept of soft expiry usually applies to bulk cards/gift cards).
Added support of proxy number in '' APIs, so that you can perform card operations by providing proxy number instead of card ID.
Introduced new "SHAREHOLDER_BUSINESS", which can be used in case you have business and shareholder as a single entity under business user. Also added 2 new related parameters - 'license_type' and 'license_expiry'.
Added new parameters to ‘’ API, so now there is capability to search users based on creation and modified date.
Added new 'allow_contactless' parameter to APIs, which indicates if contactless transactions are allowed or not.
Added a new ‘USER_CREATED’ webhook event to the ‘’ API.
Implemented enhancements to APIs - instead of “CURRENCY_MARKUP“ transaction type , two new transaction types are introduced - “PURCHASE_MULTI_CURRENCY“ and “WITHDRAWAL_MULTI_CURRENCY“.
Added a new 'status' parameter to "" API, which helps to filter users based on their user statuses.
Added 'PIN_CHANGE' , so when the PIN change operation is completed a webhook will be generated.
Added "date_of_birth_city" parameter to '' APIs.
Added the "pin" parameter to the '' API, so you can simulate PIN based transactions and test scenarios like bad PIN.
Added ability to sort_by & order_by for users in ' API.
Implemented an to get linked relationships of a user.
Improved ‘User Status Change’ by adding new parameters 'old_status' and 'old_status_reason_code'.
Added ability to set Mastercard as a value for ‘channel_scope’ parameter in ‘’ APIs.
Implemented return of both available balance and ledger balances in APIs responses.
Improved "IDENTITY_VERIFICATION" , so now the system will send this webhook notification event along with a ‘status_reason_code’ as "B1" if the user is not verified.
Fixed an error, which occurred when with 'user_type'=BUSINESS.
Updated event name from “CARD_TRANSACTION“ to “TRANSACTION", as it includes both card transactions and API transactions. Note, that if you are using an old webhook event ‘CARD_TRANSACTION’, now it will have an 'events' type - ‘TRANSACTION’.
Fixed error issues in '' APIs.
Fixed “matcher” format in the sample request for ‘’ API .
Fixed an issue when invalid values were accepted for 'director_list', 'signature_list' and 'shareholder_ list' parameters in '' APIs.
Fixed an issue with the 'regulator_name' parameter in '' APIs.
Added new '' API, which is used to link multiple cards to one particular account. So when performing transactions from any of the cards, only the one linked account is debited or credited.
Added ability to create a card without an account. It is configured on the card product level, where you have to set the '' parameter as 'false'.
Added new parameters to '' APIs, which are applicable for BUSINESS user_type. It helps to register a business user in the system and issue an account to him.
Implemented Postman collection setup. So now you can run the NymCard API collection in Postman. For more info refer to the of this guide.
Fixed the issue with uploading files for some.
Fixed the issue with an error, which occurred when running '' API.
Fixed an issue with declined transaction status in '' API while linking a velocity limit to the card product.
Now you can maintain when the user uploads any document, so that the document and its version can be identified easily.
Added 'document_status' and 'document_status_reason' parameters to response in "" APIs to capture the details of the identification lifecycle for each identification.
Now the “company_name” parameter in “” APIs is required ONLY IF the user is employed (i.e. employment_type is "SALARIED", "SELF_EMPLOYED" or "BUSINESS_OWNER").
Added such new user types as Director, Signature and Shareholder to “” APIs. This is part of SME Onboarding (KYB).
Added ‘desing_code’ parameter to “” APIs and ‘extra_embossing_line’ parameters to “” APIs. It gives a possibility to define in which card design a card will be printed and enables to add the company name on a corporate card. This is required by the Perso center so they can find the exact card design that they need to Print on the plastic card.
Added “create_account_with_card” parameter to “” API. Also a new category “account_settings” is added to the “” API. These new parameters allow customers to create a card separately without auto-creating a card account and then linking this card to a preexisting account or to a newly created account. It provides the flexibility to link multiple cards to the same account.