Core Functionality Updates
| Changes | Description |
|---|---|
| Secure Data Transfer for Payment Service Migration | A new mechanism has been implemented to allow merchants to securely retrieve data from our system. This secure data transfer is particularly beneficial when merchants transition to a different payment service or processor, ensuring that sensitive information is protected throughout the process. |
| Tokenization Retry | This feature introduces the ability to enable tokenization retry for merchants. Tokenization retry can be configured to automatically attempt tokenization again after a failure, ensuring higher success rates in capturing payment methods. Additionally, tokenization retry is designed to work seamlessly with multiple payment methods, which were introduced in the 1.13.0 release. |
Core Functionality Updates
| Changes | Description |
|---|---|
| ACH Transaction Processing and Rejection Handling for Nuvei Processor | ACH transactions are not processed in real-time. To ensure accurate transaction status in the system, it is essential to obtain data on any rejections. This functionality has been implemented to improve transaction status accuracy and system reliability. |
| Backup Processor Retry for Recurring Payments | The backup processor retry feature was enhanced to support recurring payments, in addition to one-time payments. When a payment attempt fails through the primary processor, the system will automatically retry the payment using a backup processor, provided the relevant setting is enabled. This enhancement ensures that both one-time and recurring payment transactions have a higher chance of success, reducing disruptions and improving the overall user experience. |
| Expanded Time Zone Support | Time zone support has been expanded from previously only accommodating US time zones to now including a full global list of time zones. This enhancement ensures that users from around the world can select and use their local time zones, improving the accuracy and relevance of time-based data and scheduling within the system. Additionally, the UI now displays the user's local time and supports Daylight Saving Time (DST), providing a more personalized and user-friendly experience. This feature aims to provide a more inclusive and flexible user experience for a global audience. |
| TSYS Payment Processing via Payments API | Existing endpoints in the Payments API now support processing payments through TSYS. This enhancement allows for seamless integration with TSYS, providing greater flexibility and more options for handling transactions. |
| Merchant Search | The dropdown menu for searching merchants has been enhanced with a new search functionality. Users can now quickly find and select merchants by typing keywords into the search field within the dropdown, streamlining the process of locating specific merchants. |
| Role Based Access Control (RBAC) | Role-Based Access Control (RBAC) has been implemented to enhance security and streamline user management within the system. This feature allows administrators to assign specific roles to users, each with defined permissions and access levels. |
| Multiple Payment Methods for Subscriptions | A new feature has been added that allows multiple payment methods to be associated with a single subscription. When creating a subscription, users can now add several payment methods, which will be used sequentially for processing payments. If a payment fails with the primary card, the system will automatically attempt to process the payment with the next available card during the next billing cycle. The number of retry attempts for each payment method can be configured to meet specific needs. In the event of a hard decline on a card, that card will be excluded from further payment attempts and will no longer be used. This feature is configurable and operates for merchants when enabled, providing increased flexibility and reliability in subscription management. It ensures that payments are more likely to be successfully processed, even if initial payment attempts fail. |
| Configurable Subscription Payment Recycle Scheduling | A new feature allows merchants to configure the payment recycle schedule for subscriptions by contacting support. Merchants can now request customized scheduling for retrying failed subscription payments, ensuring that payment attempts are aligned with their specific needs and preferences. To set up or modify the payment recycle schedule, merchants can reach out to our support team, who will assist in configuring the desired retry intervals and frequency. This feature provides greater control over payment management and enhances the ability to handle subscription payments effectively. |
| Expanded Country Support for Merchant Configuration | Previously, merchant configuration was limited to a single country, the US. This release expands the available options to include all countries. Merchants can now configure their settings for any country. |
| Improved Network Token Retrieval Process | The process for obtaining network tokens has been enhanced to provide a more efficient and reliable experience. This improvement streamlines the steps involved in retrieving network tokens, reducing latency and increasing the accuracy of token generation. |
API Reference Guide Updates
| Changes | Description |
|---|---|
| Removal of Avatax Tax Parameters | Several Avatax-related tax parameters were removed to streamline the invoicing process. The following parameters have been removed:
|
Documentation Portal Updates
| Changes | Description |
|---|---|
| Checkout Line Items Value Types | The Checkout Guide has been updated to include detailed information about the Value Types of line items. This addition provides clear guidance on how to define and utilize different value types for line items during the checkout process. |
Technical Enhancements
| Changes | Description |
|---|---|
| International payments | The architecture has been prepared to support international payments, ensuring a seamless and reliable transaction experience for global users. |
| Framework update | The .NET framework has been updated to the newest version. This upgrade brings enhanced performance, improved security, and better support for modern development practices. |
| Bug fixes | We've resolved several bugs to improve the stability and performance of the product. |
API Reference Guide Updates
| Changes | Description |
|---|---|
| The new endpoints for the checkout are available | * Create Checkout Link Create a URL for a checkout page to accept payments.This URL can be seamlessly integrated into your payment flow, embedded into your payment page, or used to direct customers to a hosted payment page. The link will be deactivated once the customer opens the checkout page. * Get Complete Checkout Information endpoint allows to retrieve complete checkout information, merchants can use our API to access detailed data about each transaction. This includes customer details, payment method information, transaction status, and any error messages if the payment fails. |
| Email is optional | The email associated with a billing address is now optional for processing transactions through Nuvei processor |
Documentation Portal Updates
| Changes | Description |
|---|---|
| The new guide for the checkout are available | To assist merchants with the integration process, we have introduced the Checkout Guide . This comprehensive guide provides step-by-step instructions on how to integrate with either the hosted checkout page or the embedded payment page. It covers all aspects of the integration, from initial setup and configuration to customizing the payment form and handling responses. |
Core Functionality Updates
| Changes | Description |
|---|---|
| Checkout feature | The Checkout feature provides the ability to use our page with a form to collect payments. Merchants can embed Checkout directly into their websites or redirect customers to a Revolv3 hosted checkout page. This feature ensures a seamless payment experience by securely handling customer payment information, supporting various payment methods, and complying with PCI DSS standards. |
API Reference Guide Updates
| Changes | Description |
|---|---|
| The BIN number is returned in endpoint responses | The information about the credit card BIN number is now returned in the responses of the following endpoints: * Get Invoices * Get Invoice * Get Payment Method |
API Reference Guide Updates
| Changes | Description |
|---|---|
| Update Payment Method Billing Address endpoint accepts Billing Address object | It is now allowed to Update the billing address associated with an existing payment method by supplying a billing address object. Previously, it was only possible to supply an existing billing address ID. |
| Create Subscription response enhancements | The following enhancements were made to the Create Subscription endpoint response to provide more information and make the result of the call more transparent: A “message” parameter was introduced to return information about the first payment transaction result. The subscription object will always be returned in the response (previously, it was not returned in the case of the first payment transaction failure). |
API Reference Guide Updates
| Changes | Description |
|---|---|
| New Payments API end points | Newly implemented endpoints will allow merchants to send additional optional parameters that will identify whether a payment is one-time, recurring, or an installment (initial or subsequent). This will enable linking transactions at a processor/card scheme level. The following transaction types are introduced: * Sale with raw payment method data * Sale with payment method ID * Payment method authorization with raw payment method data * Payment method authorization with payment method ID * Capture of previously authorized amount Note: Currently, linking transactions on a processor/card scheme level is implemented for Adyen and Worldpay processors. |
| One-time payment without subscription | The specification of One-time payment without a subscription was updated with detailed information about parameter validations that will make integration processes smoother |
Core functionality updates
| Changes | Description |
|---|---|
| Proportion routing rule enhancements | Transactions will be routed more effectively to distribute transaction volume between processors in line with the merchant's desired proportion rule. |