Core Functionality Updates
| Changes | Description |
|---|---|
| Embedded Checkout Support | Checkout can now be embedded directly into merchant websites via iframe. This enhancement improves user experience and helps increase conversion by removing full-page redirects. |
| Merchant Invoice Reference Sent to Worldpay | Merchant Invoice Reference ID is now sent to Worldpay in the Order ID field. If not provided, the system defaults to using the Revolv3 Invoice ID. |
| Invoice Reference Mapping for EPX Transactions | Invoice and merchant reference IDs are now sent to EPX (INVOICE_NBR and ORDER_NBR), enabling easier transaction tracking and search by invoice number in EPX systems. |
Documentation Portal Updates
| Changes | Description |
|---|---|
| Improved Developer Documentation | We have updated our developer guides with more detailed and comprehensive information to simplify integration and improve the overall developer experience. |
Technical Enhancements
| Changes | Description |
|---|---|
| Bug Fixes and Stability Improvements | Various minor issues have been resolved to improve overall system stability and reliability. |
Core Functionality Updates
| Changes | Description |
|---|---|
| Date Range Filter in Global Search | The Portal global search has been enhanced with a date range filter, allowing users to narrow search results by specific time periods. Preset options include Today (default), Last 7 Days, Last 30 Days, as well as a Custom Range. |
| Dynamic Transaction Descriptors for EPX | We have added support for dynamic transaction descriptors for the EPX processor. Merchants can now pass descriptor values per transaction via the API, providing greater flexibility and consistency with other supported processors. When enabled in the Portal, dynamic descriptors are automatically mapped to the appropriate EPX fields and applied across supported transaction types, including Sale, Authorization, and Capture. |
| $0 Authorization (Account Verification) Support | We have added support for $0.00 authorization (account verification) transactions (Worldpay and EPX), allowing merchants to validate customer account details without performing a financial charge. |
API Reference Guide Updates
| Changes | Description |
|---|---|
| 3D Secure Parameters Support in Payment API | We have extended the Authorization and Sale Payment API endpoints to support 3D Secure (3DS) parameters. Merchants can now submit 3DS authentication data as part of payment requests. The list of endpoints: ▪ Sale with Payment Method Details ▪ Auth with Payment Method Details This enhancement enables seamless integration with external 3DS providers and supports compliant 3DS-enabled card payment flows. ⚠️ 3D Secure (3DS) parameters received via the API are now forwarded to the payment processor only for Worldpay transactions. |
Technical Enhancements
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability of the product. |
Core Functionality Updates
| Changes | Description |
|---|---|
| Merchant Analytics Dashboard | A new Analytics Dashboard is now available in the Portal, providing merchants with key business insights and metrics. The dashboard displays various indicators for the current month, compared against the previous period, along with charts showing trends across current and historical data. |
API Reference Guide Updates
| Changes | Description |
|---|---|
| Processor Response Details in Payment API | Payment API responses now include two new parameters — The list of endpoints: ▪ Sale with Payment Method Id▪ Sale with Payment Method Details ▪ Auth with Payment Method Id ▪ Auth with Payment Method Details ▪ Capture ▪ Create Subscription |
| Account Updater Details in Payment Responses | Payment API responses now include Account Updater information for supported processors (currently Adyen and Worldpay). Merchants can see when an account update occurred and get details of the updated card, including: ▪ AccountUpdateDateTime – the date and time when the update happened ▪ AccountUpdaterMessage – the message returned by the processor ▪ binNumber, paymentLast4Digits, and paymentExpirationDate – details of the new card, when available The list of endpoints: ▪ Sale with Payment Method details▪ Sale with Payment Method Id ▪ Auth with Payment Method details ▪ Auth with Payment Method Id ▪ Capture ▪ Refund Invoice ▪ Get Invoice ▪ Get Invoices V1 |
Technical Enhancements
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability of the product. |
Technical Enhancements
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability of the product. |
Core Functionality Updates
| Changes | Description |
|---|---|
| Processing Method in Invoice Data Export | The Invoice Data Export report has been enhanced to include the Processing Method for each invoice. Possible values: ▪ None – for Capture transactions, refunds (ACH and credit card), and reversal authorizations. ▪ ProcessorToken – when a processor-specific token is used. ▪ NetworkToken – when a universal network token is used across processors. ▪ Ach – for transactions processed via ACH account number. ▪ CreditCard – for transactions processed with raw credit card data. |
Core Functionality Updates
API Reference Guide Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Trial Marking for Initial Recurring Transactions | We’ve added the ability for merchants to mark the first recurring payment as a trial transaction. Key details: ▪ A new portal setting lets merchants enable trial marking for supported processors. ▪ When enabled, the system automatically appends “Trial” to the transaction descriptor for the initial recurring payment. ▪ Works with both static and dynamic descriptors, while ensuring compliance with processor-specific descriptor length rules. ▪ Phase 1: available for Worldpay integration. This enhancement provides greater flexibility in handling recurring billing scenarios where the initial transaction should be clearly identified as a trial. |
| Changes | Description |
|---|---|
| Processor and MID Information in Payment Responses | We have enhanced payment API responses to include additional processor-related parameters: * paymentProcessor – the name of the processor handling the transaction (e.g., WorldPay). * processorMerchantId – the merchant account ID (MID) assigned by the processor (e.g., 10071676). These parameters are now available in responses for the following endpoints: * Sale (with/without Payment Method details) * Auth (with/without Payment Method details) * Capture * Create Subscription Merchants can now easily identify which processor and merchant processor account were used for each transaction, improving transparency and simplifying reconciliation across multiple processors. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability of the product. |
| Updated Inactivity Timeout | We have adjusted the portal’s user session timeout for increased security. Now, users will be automatically logged out after 15 minutes of inactivity (previously 60 minutes). |
Core Functionality Updates
API Reference Guide Updates
Technical Enhancements
| Changes | Description |
|---|---|
| New Integration: BridgePay Now Available on the Portal | We are pleased to announce the integration of BridgePay into our platform, providing merchants with a robust and versatile payment processing solution. Key Features: * Comprehensive Transaction Support: Process a wide range of transactions, including authorizations, sales, refunds, and more. * Tokenization Capabilities: Utilize both one-time and recurring tokenized transactions to enhance security and streamline payment processes. * Descriptor Flexibility: Configure either static or dynamic descriptor to ensure clear transaction labeling on customer statements. * Dynamic Routing Participation: Leverage BridgePay in dynamic routing setups to optimize approval rates and enhance transaction success. |
| Subscription Support for Nuvei | We have added support for recurring and recycling billing through Nuvei. Merchants can now create and manage subscription-based transactions using Nuvei as their payment processor. |
| Changes | Description |
|---|---|
| New API Endpoint: Configure BridgePay for Merchants | We have introduced a new API endpoint that enables merchants to configure BridgePay as a payment processor directly through the API. This addition streamlines the setup process, allowing for efficient integration and management of BridgePay within merchant accounts. |
| Currency Support in Subscription Transactions | We have extended subscription transactions to include a currency parameter. The system now: * Sends the specified currency to the processor if supported. * Returns a clear error message if the currency is not supported by the configured processor. * Stores the currency in subscription records, invoices, and processor transactions. |
| Flexible Billing Frequency for Subscriptions | We’ve enhanced subscription settings by replacing the fixed billingFrequencyType values with a flexible interval-based configuration. Merchants can now define billing cycles using a combination of:* intervalCount (numeric value) * intervalType (days, weeks, months, or years) This allows for fully customizable recurring billing schedules — for example, every 28 days — and updates both the trial duration options and recurring logic accordingly. Existing subscriptions have been migrated to support the new format. |
| Enhanced Bulk Invoice Retrieval | We have introduced an improved Get Invoices endpoint that allows merchants to retrieve multiple invoices in a single request (up to 100), with expanded filtering, sorting, and data details. Key enhancements include: * Support for bulk invoice retrieval with advanced filters (by billing date, last update date, etc.) * Additional sorting options and improved parameter handling * Detailed payment information in the response, including payment type, token details, descriptor, and currency * Ability to request raw processor response data for deeper insights The existing Get Invoices endpoint remains available, but the new version offers significantly more flexibility and richer data. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability of the product. |
| Updated Inactivity Timeout | We have adjusted the portal’s user session timeout for increased security. Now, users will be automatically logged out after 15 minutes of inactivity (previously 60 minutes). |
Documentation Portal Updates
Technical Enhancements
| Changes | Description |
|---|---|
| New Documentation Added: ACH Direct Debit | A new article on ACH Direct Debit is now available in the Guides section. Merchants can explore how to use this payment method, transaction flow, and best practices. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
API Reference Guide Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Merchant-Specific BIN Blocking Rules | Merchants can now configure BIN-based block rules tailored to each account. If a transaction includes a blocked BIN, our system returns a clear, branded decline response indicating it was blocked due to BIN rules. This enhances control and security for merchants. |
| Manage Email Notification Preferences | We’ve added a new “Notification Settings” section to the Portal, now available under the Settings menu. This feature gives users greater control over the types of email notifications they receive. Key Capabilities: * Subscribe or unsubscribe from specific notification topics. * Choose which team members should receive each type of notification. * Toggle individual topics on or off based on your preferences. Changes made in the Portal take effect immediately, ensuring your communication preferences are always up to date. |
| Changes | Description |
|---|---|
| New API Endpoint: Configure JPMorgan (Paymentech) for Merchants | We have introduced a new API endpoint that enables merchants to configure JPMorgan (Paymentech) as a payment processor directly through the API. This addition streamlines the setup process, allowing for efficient integration and management of JPMorgan (Paymentech) within merchant accounts. |
| Combined Cardholder Name Field | To improve developer experience, our API now supports a combined billingFullName field alongside the existing billingFirstName and billingLastName parameters. Merchants can now choose one of two mutually exclusive formats:* First/Last Name – using billingFirstName + billingLastName (existing method)* Full Name – using billingFullName (new alternative)Exactly one naming format must be provided per request. This update simplifies integration for merchants who collect name data as a single string. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
API Reference Guide Updates
| Changes | Description |
|---|---|
| New Integration: PaymentLync Now Available on the Portal | We are pleased to announce the integration of PaymentLync into our platform, providing merchants with a robust and versatile payment processing solution. Key Features: * Comprehensive Transaction Support: Process a wide range of transactions, including authorizations, sales, refunds, and more. * Tokenization Capabilities: Utilize both one-time and recurring tokenized transactions to enhance security and streamline payment processes. * Descriptor Flexibility: Configure either static or dynamic descriptor to ensure clear transaction labeling on customer statements. * Dynamic Routing Participation: Leverage PaymentLync in dynamic routing setups to optimize approval rates and enhance transaction success. |
| Changes | Description |
|---|---|
| New API Endpoint: Configure PaymentLync for Merchants | We have introduced a new API endpoint that enables merchants to configure PaymentLync as a payment processor directly through the API. This addition streamlines the setup process, allowing for efficient integration and management of PaymentLync within merchant accounts. |
Technical Enhancements
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Enhanced TSYS Integration | We have enhanced our integration with TSYS to improve payment approval rates. By transmitting additional transaction details during payment processing, we aim to provide more comprehensive information to the processor, facilitating better authorization decisions. No action is required from merchants; these enhancements have been seamlessly applied to the system. |
| Support for Network Token Transactions with TSYS and Nuvei | We have expanded our payment processing capabilities to support transactions using network tokens with both TSYS and Nuvei. This enhancement enables merchants to process payments using tokens issued by card networks, offering increased security and potentially higher approval rates. |
| IP Whitelisting for Enhanced Security | Merchants now have the option to enhance their account security by whitelisting specific IP addresses. This feature allows merchants to restrict access to their accounts, ensuring that only requests originating from approved IP addresses are permitted. To set up IP whitelisting, merchants should contact our support team with the IP addresses they wish to authorize. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
Documentation Portal Updates
Technical Enhancements
| Changes | Description |
|---|---|
| New Option to Request Personal Data Clearing | We have introduced a new feature on the portal that allows merchants to initiate requests for clearing personal data. A dedicated “Clear Personal Data” page is now available (Operations). Users can now navigate to the form via a dedicated link on the portal to specify the details of the data they wish to delete. Once submitted, these requests will be processed accordingly. |
| Access to Customer Support Hub | We have introduced a new feature on our portal—a dedicated icon that provides merchants with direct access to the Customer Support Hub. Through this hub, users can submit various requests, provide feedback, and access additional support resources. |
| Changes | Description |
|---|---|
| API Versioning Policy | We have introduced a API Versioning Policy to ensure a seamless experience for developers integrating with our API. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Expanding RBAC for Secure and Scalable Access Management | As part of our continuous security enhancements and alignment with PCI DSS 4.0, we are expanding the use of Role-Based Access Control (RBAC) across more infrastructure resources. |
| Enhanced Routing Rules for Recurring Transactions | We have expanded our transaction routing capabilities, allowing more flexibility in processing recurring payments. Now, the initial recurring transaction can be routed to one processor, while subsequent transactions can be directed to another, based on configurable routing rules. |
| Updated Integration with TSYS | We have refined our integration with TSYS to align with their latest recommendations and best practices. These improvements enhance stability, compatibility, and overall processing efficiency. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
API Reference Guide Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Default Order Processing Channel Selection for Merchants | Merchants can now select an Order Processing Channel when creating or editing their profiles. This channel represents the sales channel through which the shopper provides their card details and will be used as the default value sent to the processor unless explicitly specified in the payment request. Available options: E-Commerce, MOTO (Mail Order / Telephone Order). Currently, this feature is supported only for Worldpay, while for other processors, the E-Commerce value will always be used. For all merchants created before this release, the default value has been set to E-Commerce. |
| Changes | Description |
|---|---|
| Order Processing Channel | The OrderProcessingChannel parameter has been added to the structure of Authorization and Sale requests (Authorization and Capture in a single request). This parameter defines the sales channel through which the shopper provides their card details and allows merchants to specify it when initiating a transaction. Available options: ecommerce, moto. If not explicitly provided in the request, the default value set at the merchant level on the Revolv3 Portal will be used. Currently, this parameter is sent only to Worldpay, while for other processors, the default value remains E-Commerce. Updated end points: Authorize With Payment Method Details, Authorize With Payment Method Id, Sale With Payment Method Details, Sale With Payment Method Id. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Direct PAN Usage for Initial Transactions with Worldpay | Previously, during payment processing via Worldpay, we first requested a token and then executed the payment using the token. With this update, the Primary Account Number (PAN) is now directly utilized for the first transaction, streamlining the process and reducing latency for initial payments. |
| Configurable Retry Timing for Backup Processor Payments | We have introduced a feature that allows configuring the delay before the system retries a payment with the backup processor if the initial attempt with the primary processor fails. By default, the retry is immediate (0 minutes), but you can now set a delay of up to 60 minutes. This provides greater flexibility in managing transaction retries and optimizing payment workflows. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Introduction of Stateful Webhooks with Enhanced Features | We have transitioned from a stateless to a stateful webhook mechanism to align with industry best practices. This new implementation improves reliability, transparency, and efficiency when notifying external systems about events. Key Features: * Stateful Webhooks: Each webhook now includes the state of the entity at the moment of generation, ensuring accurate context for external systems. * Retry Mechanism: Supports progressive retries in case of transient failures, enhancing delivery reliability. * Preserved Order: Webhooks are processed sequentially for each merchant, preventing disorder and ensuring consistent event streams. Processing halts and resumes as issues are resolved. * Custom Configuration: Merchants can now define specific webhook types they wish to receive, reducing system load and unnecessary notifications. This update ensures a robust, scalable, and configurable webhook experience for merchants and their integrated systems. |
| Optimized EPX Transaction Processing | Transactions with EPX now process faster by using the PAN for the first payment when no token is available. Token retrieval happens in parallel, ensuring seamless processing for subsequent transactions. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Raw Processor Response | Optional parameter to return the raw processor response on a transaction - useful to find processor error codes. Data is stored after Nov 18th, 2024 |
| WorldPay Dynamic Descriptor | Allow the use of Dynamic Descriptor for WorldPay |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
Technical Enhancements
| Changes | Description |
|---|---|
| Invoice Export | A new UI feature that will export Invoices to a .csv file up to 15Mb in size based on dates |
| InvoiceId Lookup | A Invoice ID input box is added to the UI on the Invoices page to look up specific invoices |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
Core Functionality Updates
Technical Enhancements
| 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. |
| Changes | Description |
|---|---|
| Bug fixes | We’ve resolved several bugs to improve the stability and performance of the product. |
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. |
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. |
| 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. |
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: Invoices and PaymentMethod |
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).Account Updater Details in Payment Responses |