Release Notes
Please make sure to subscribe to our status page for updates on service status, scheduled maintenances, and further releases.
v9.5
This version includes performance improvements and bug fixes.
SDKs Latest Versions
Periodically updates are released to the web and mobile SDKs, which can include new functionality, bug fixes, and security updates. We urge all stakeholders to update integrated SDK versions to the newest version as soon as these are available.
The latest version numbers are:
v9.4
This version includes performance improvements and bug fixes.
Merchant Panel
Multi-Factor Authentication Update
The Two Factor Authentication re-enrollment will be possible in the Merchant Panel and shall require 2FA confirmation.
v9.3
This version includes performance improvements and bug fixes.
Web API
Complete Authorize Call
The following fields are no longer needed to be sent in the 1.39 Complete Authorize Call.
'useDifferentBillingAddress',
'customerFullName',
'addr1',
'addr2',
'addr3',
'houseNumber',
'city',
'state',
'countryCode',
'postCode',
'phone'
When you are still sending these parameters, the calls remain successful, but in the response under additional information, we will notify you that these fields are no longer recognized.
Merchant Panel
Multi-Factor Authentication Update
The Two Factor Authentication to log in to the Merchant Panel will change to a time-based one time password authentication method. We would like to ask you to already download either the Google or Microsoft Authenticator App. Additional information on how to set this up will be shared from our CRM Team.
v9.2
This version includes performance improvements and bug fixes.
Web API
Update: Enhanced Transparency in Get Payment Status API
We've updated the Get Payment Status API to include additional information about related transactions. Now, if a Deposit Transaction is settled and has related internal transactions with a status of "Captured", these related transactions will be listed under a new return parameter "internalTransactionsPendingSettlement" in the additional Information section of the response. This enhancement provides more transparency and detail about the status of related transactions.
SDKs Latest Versions
There is no updates on the SDK this time.
Coming Soon (in future upgrade v9.3)
Update on Address Data Submission for Complete Authorize API
The "useDifferentBillingAddress" parameter and related address fields in the Complete Authorize API will be deprecated in the future version v9.3 (not as part of this upgrade v9.2). If a different billing address is needed, it must be included in the Init Authorize API request if it hasn't already been submitted as part of that request. This change helps to streamline the authorization process.
v9.1
This version includes performance improvements and bug fixes.
Merchant Panel
New Field
We have enhanced the sections "Transactions", "Transaction History" and "Linked Transactions" with the field "Status Reason".
File Names
We have enhanced the "Report" Section showing also the name of the report to identify the right report more easily.
SDKs Latest Versions
Periodically updates are released to the web and mobile SDKs, which can include new functionality, bug fixes, and security updates. We urge all stakeholders to update integrated SDK versions to the newest version as soon as these are available as the following link.
The latest version numbers are:
- Web – v9.1
- iOS – v9.0
- Android – v9.0
SmartPay customers do not need to take any action.
v9.0
This version includes performance improvements and bug fixes.
Merchant Panel
Chargeback Transactions Custom Fields
For Chargeback transactions, the fields Custom1, Custom2, and Custom3, provided with the original transaction will be displayed in the Merchant Panel
Failed Authorizations
When an Authorization has failed, for example, due to errors in 3D Secure User Authentication, it is now visible with the Transaction Status "Failed" in the Merchant Panel.
Web API
New Status "Failed" for Failed Authorizations
When a transaction fails during the authorization process, the transaction will be marked as status "Failed". Failed Authorizations are visible in the Merchant Panel.
New Validation and API Response Code
A validation with response code 0619 has been introduced to the API Call Complete Add Stored Payment Option. It prevents storing a Payment Option for a PaymentOptionCode different than the one provided in the related Init Add Stored Payment Option request.
Dot-less Domain Support for Dev Environments
URL Input Validation has been altered to allow dot-less domains for flexibility in development environments. This means, for example, URLs such as https://localhost/test are allowed for development purposes. For the best compatibility with the widest range of external systems and payment providers, it's still strongly recommended for Merchants to use HTTPS Absolute URLs, including a top-level domain.
General Changes
Rate Limiting
Rate Limiting of all API Requests has been implemented to avoid instability due to unexpected peaks in demand, for example "Black Friday" Sales events. In case you are expecting high demand, please reach out to your Customer Relationship Manager
SDK Change
Dot-less Domain Support for Dev Environments
URL Input Validation has been altered to allow dot-less domains for flexibility in development environments. This means, for example, URLs such as https://localhost/test are allowed for development purposes. For the best compatibility with the widest range of external systems and payment providers, it's still strongly recommended for Merchants to use HTTPS Absolute URLs, including a top-level domain.
SDKs Latest Versions
Periodically updates are released to the web and mobile SDKs, which can include new functionality, bug fixes, and security updates. We urge all stakeholders to update integrated SDK versions to the newest version as soon as these are available as the following link.
The latest version numbers are:
- Web – v9.0
- iOS – v9.0
- Android – v9.0
v8.9
This version includes performance improvements and bug fixes.
Merchant Panel
To improve the security of our merchant panel, merchant panel users that would like to change their phone number, are asked to provide their merchant panel password as a confirmation.
SDK Change
In future SDK versions, only HTTPS scheme URLs will be permitted in the SDK callbackURL as well as other URL values. This change follows industry security best practices and ensures the best compatibility with all services providers in all environments. We urge all merchants to review their integrations before upgrading the SDK to versions of v8.9 and above.
SDKs Latest Versions
Periodically updates are released to the web and mobile SDKs, which can include new functionality, bug fixes, and security updates. We urge all stakeholders to update integrated SDK versions to the newest version as soon as these are available as the following link.
The latest version numbers are:
- Web – v8.9
- iOS – v7.6
- Android – v8.3
v8.8
This version includes performance improvements and bug fixes.
v8.7
This version includes performance improvements and bug fixes.
API Calls
The following fields have been removed from the API call: Init Add Stored Payment Option and Complete Add Stored Payment Option
"useDifferentBillingAddress",
"customerFullName",
"addr1",
"houseNumber",
"city",
"countryCode",
"postCode",
"emailAddress"
If you are still sending these fields in the API calls, you will receive a positive response with a notice that these fields are unrecognized. This information will be present in the sections "additionalInformation" and "unrecognizedFields".
Please make sure that this is not impacting your processing.
Merchant Panel
To optimize our performance of the Merchant Panel, we have changed the way Merchant Panel Users can see the total counts of a search result.
If you are interested to see how many items have been found in your search, you can simply click on "Count all items" (in the right corner below your search result) and verify how many line items were part of the search.
SDKs
Periodically updates are released to the web and mobile SDKs, which can include new functionality, bug fixes, and security updates. We urge all stakeholders to update integrated SDK versions to the newest version as soon as these are available as the following link.
The latest version numbers are:
- Web – v8.7
- iOS – v7.6
- Android – v8.3
v8.6
This version includes performance improvements and bug fixes.
3RI merchant-initiated authentications for partial/split or delayed shipments
We extended our MIT Card processing capabilities and are introducing 3RI payments for MIT. This way of transaction processing can be used for partial/split or delayed shipment transactions.
For more information on 3RI payments, please do not hesitate to reach out to your account manager, or send an e-mail to our support team.
Merchant Panel Changes
Yearly Merchant Data Review
As an Electronic Money Institute in Luxembourg we are obliged to perform yearly reviews of our merchant base. Therefore, in the upcoming months, you may be asked in the Merchant Panel to approve the data that we have currently stored about the respective legal entity. Shall there be deviations, we will ask for further documents and information
Three New Fields: Custom 1, Custom 2, Custom 3
We introduced three new fields to the merchant panel grid and reports for the tabs Transaction, Account Statement and for the Payout Report. The three new fields can be used by merchants to send extra data in regards to the transaction during payment processing. If you are interested to use these fields in the future, please do not hesitate to reach out to your account management team or send an e-mail to our support team.