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.

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.

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.

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.

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.

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.

Revolv3 Portal Now Organized by DBA Name

To enhance clarity and align with common business practices, the Merchant Portal has been updated to organize merchant profiles based on their DBA (Doing Business As) names. Previously, merchant accounts were structured under their legal business names.

New API Endpoints for Merchant and Processor Management

We have introduced new Open API endpoints that enable automated management of merchants and their associated processors.

• Merchant Creation: Allows for the creation of merchant profiles via API, streamlining the onboarding process.

• Processor Configuration: Enables the configuration of payment processors for merchants through API calls, facilitating dynamic integration setups.

These enhancements support seamless integration and automation of merchant and processor management workflows.

New Payment Method: Apple Pay Token Support

We have added support for Apple Pay Token as a new payment method. This enhancement allows merchants to process transactions using Apple Pay tokens, providing a secure and convenient payment option for customers.

The Apple Pay Token payment method is now supported in the following API endpoints:

• One Time Payment Without Subscription
• Create Payment Method
• Sale With Payment Method Details
• Authorize With Payment Method Details

Enhanced Account Updater Response Details

We have enriched the Account Updater response data by including additional information to provide greater transparency and facilitate better integration handling.

What's New:

Update Timestamp: The response now includes the exact date and time when the account update was processed.

Processor Message: A descriptive message from the processor detailing the outcome of the account update request.

These enhancements are available for the following processors:

• Adyen: When the Account Updater feature is enabled.
• Worldpay: When the Account Updater feature is enabled.

The additional information is included in the responses of the following API endpoints:

• Sale With Payment Method Details

• Authorize With Payment Method Details

• Sale With Payment Method Id

• Authorize With Payment Method Id

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)

Order Processing Channel

The OrderProcessingChannelparameter 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

Updated end points:
• Authorize With Payment Method Details
• Authorize With Payment Method Id
• Sale With Payment Method Details
• Sale With Payment Method Id

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.

Enhanced Card Handling for Subscription Payments

Our system supports linking multiple cards to a subscription and sequentially attempting payments. If the payment with the first card fails, the system will try the second card, and so on.

With the new feature, you can configure whether the second and subsequent cards should be used on the same day as the initial attempt or only in the next recycle cycle. This added flexibility allows for better control over retry strategies and ensures alignment with business needs.

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.

Enhanced TSYS Transaction Processing

The transaction flow with TSYS has been improved to reduce delays. For the first payment method transaction without a token, the PAN is used directly, while token retrieval occurs in parallel to ensure smooth processing for future payments.

Optimization of Processor Requests

We have optimized the number of requests sent to payment processors by removing unnecessary calls. This improvement reduces the overall transaction volume and helps to minimize operational costs associated with processing fees.

Direct Integration with Nuvei for Network Transaction ID Support

To address the limitation in the Nuvei SDK, which currently does not support the network transaction ID required for linking recurring transactions into a unified stream, we have implemented a direct integration with Nuvei.

This new integration bypasses the SDK, allowing us to include the network transaction ID and ensure seamless handling of recurring transactions.

Bug fixes

We've resolved several bugs to improve the stability and performance of the product.