This page provides a high-level overview of new features, enhancements, and other impactful changes. For full details on the latest API changes, SDK changes, and changes to our CLI and Postman collection, please refer to each of their GitHub pages for more details.

OpenAPI

SDKs

Tools
​
2025-08-21
ConnectorNuveiP24
Feature

​
Nuvei: Przelewy24 connector

We’ve expanded our European payment method coverage by launching Przelewy24 (P24), now available through our Nuvei connector. This is a key addition for any merchant looking to increase sales in Poland.

​
What’s new?

Przelewy24 is the most popular online payment method in Poland, allowing customers to pay for purchases using secure, real-time bank transfers. By offering Poland’s most trusted payment method, merchants can significantly reduce friction at checkout and increase conversion rates for Polish customers.

​
Why it matters

Bank transfers are the dominant form of online payment in Poland, making Przelewy24 an essential option for success in this market. By enabling this payment method through our existing Nuvei connection, we are making it simple for our merchants to cater to local payment preferences without requiring any new integration work.

​
How it works

  • The customer payment flow is simple and secure:
  • At checkout, the customer selects Przelewy24.
  • They are redirected to the Przelewy24 page to choose their bank.
  • The customer logs into their online banking portal to authorize the payment.
  • Once authorized, they are redirected back to the merchant’s site.
For more information on how to configure and use the Nuvei Przelewy24 connector, please refer to our documentation.
​
2025-08-09
ConnectorKount
Feature

​
Kount: KHASH token connector

We’ve launched a new utility connector for merchants who use Kount, an industry-leading, AI-driven fraud prevention platform. This connector provides a simple, secure way to generate a Kount-specific hash for a card number.

​
What’s new?

To perform advanced fraud analysis, Kount’s services often require a proprietary, one-way, irreversible hash of the card number, known as a KHASH. This allows Kount to identify a card across its global network without exposing the sensitive card number itself.Our new Kount KHASH connector is a utility that does one job: it securely accepts raw card details and returns the corresponding KHASH. This connector does not process payments or make fraud decisions; it is a tool to enable your own integration with Kount’s powerful Risk Inquiry Service (RIS).

​
Why it matters

This connector provides a secure and streamlined way to integrate Kount into your payment flows.
  • Reduce your PCI Scope: Generate a KHASH without having the raw card number touch your servers, simplifying your security and compliance obligations.
  • Simplify Kount Integration: Easily get the required KHASH to use in your own server-side calls to Kount’s fraud analysis APIs.
  • Enable Flexible Workflows: Use Kount’s fraud tools independently of your payment processor, allowing you to build sophisticated, multi-step fraud and payment workflows.

​
How it works

The Kount KHASH connector is configured as a new service in your Gr4vy admin panel.
  • Configure: Add the connector and enter your Kount Merchant ID.
  • Call the Connector: When you need to perform a fraud check, send the raw card details (card number, expiration date, etc.) to the Kount KHASH connector via our API.
  • Receive the KHASH: The connector will return the generated KHASH.
  • Use with Kount: You can now use this KHASH in your own server-side API calls to Kount’s Risk Inquiry Service (RIS) to get a fraud score before proceeding with a payment.
For more information on how to configure and use the Kount KHASH connector, please refer to our documentation.
​
2025-08-08
EmbedNotice
Change

​
Changes to transactionCreated event in Embed and mobile SDKs

Expected release date: Aug 27, 2025
We will be changing the payload for the transactionCreated event raised by Embed to contain less data. This change will roll out to all merchants during the regular release cycle.

​
Background

Our Embed SDK for web, iOS, and Android provides a way to listen to a transaction being created. On web, Embed has an event handler called onEvent(). This parameter allows you to listen to a transactionCreated event, which is raised when a transaction completes.
setup({
  onEvent: (name, data) => {
    if (name === "transactionCreated") {
      // inspect data
    }
  },
});
Currently, in each of these SDKs these events can include a data payload that contains most of the transaction details.
{
  "type": "transaction",
  "id": "7099948d-7286-47e4-aad8-b68f7eb44591",
  "reconciliation_id": "default",
  "merchant_account_id": "default",
  "currency": "EUR",
  "amount": 1299,
  "status": "authorization_succeeded",
  "authorized_amount": 1299,
  "captured_amount": 1299,
  "refunded_amount": 0,
  "settled_currency": "USD",
  "settled_amount": 1100,
  ...
}

​
Changes

With this change, the new data payload will be reduced to return just the ID, status, and depending on the SDK the the type and success state (React Native).
{
  "type": "transaction",
  "id": "7099948d-7286-47e4-aad8-b68f7eb44591",
  "status": "authorization_succeeded"
}

​
Impact

Please check if you are expecting this data to include all the parameters. For example, your code might perform a check to see if the authorized_amount > 0.Instead, please move this logic to your server side, and call the GET /transactions/:id API using the ID provided in this payload.
​
2025-08-04
API
Enhancement

​
Richer error responses for refunds

Following our recent update to provide better error details for voids and captures, we’ve now extended this same functionality to refunds. You can now get actionable, programmatic insight into why a refund attempt has failed.

​
What’s new?

Previously, when a POST /transactions/{id}/refunds request failed, the API would return a generic error, and the exact reason for the failure could only be found by checking the transaction details in the Gr4vy dashboard.Now, when a refund fails, the API error response will include the same rich error details that we provide for other failed payment actions. The response body will contain:
  • error_code: A standardized Gr4vy error code.
  • raw_response_code: The raw error code from the payment service provider.
  • raw_response_description: The raw, human-readable error message from the provider.
In addition, the reason for the failure will now be clearly displayed in the dashboard, making it easier for your support teams to diagnose issues quickly.

​
Why it matters

This enhancement gives you direct, programmatic access to the outcome of refund attempts. Instead of relying on manual checks, your system can now automatically handle failures by:
  • Triggering alerts for specific error codes that require manual intervention.
  • Improving internal dashboards with clear reasons for refund failures.
  • Streamlining support workflows by providing immediate context for failed refunds.
This ultimately reduces manual overhead and allows you to build more resilient refund and reconciliation processes.

​
How it works

This is not an opt-in change. The new error fields will now be returned automatically in the error response body for any failed refund request. There are no changes required to your existing integration to benefit from this feature.
​
2025-07-31
SDKsKotlinSwift
Enhancement

​
True Native Mobile SDKs for iOS & Android

We are thrilled to announce the first phase of our brand-new, truly native SDKs for iOS (Swift) and Android (Kotlin). This marks a significant evolution from our previous web-view-based SDKs, giving you the power to build a completely custom, seamless, and fully-branded checkout experience directly within your mobile applications.

​
What’s new?

While our existing mobile SDKs provide a quick way to get started using a web view, we understand that merchants want more control and a deeper integration with their app’s native user experience. This release, the first phase of many, offers a set of API helper libraries. These SDKs do not provide any UI components. Instead, they give your developers the tools to build their own checkout UI while Gr4vy handles the complex API interactions securely in the background. The initial version of our new SDKs for iOS and Android includes helpers to:
  • Initialize the SDK: Securely configure and connect to the Gr4vy API.
  • List Payment Options: Fetch the payment options available for a specific transaction.
  • Tokenize Card Details: Securely send card data to the Gr4vy vault using a checkout session, without the data hitting your servers.
  • List Stored Payment Methods: Fetch the vaulted payment methods for a known buyer.
  • Get Card Details: Fetch card metadata, like the scheme, based on the BIN.

​
Why it matters

This is a major step forward for mobile commerce on Gr4vy. You now have the ultimate flexibility to design and implement a checkout experience that perfectly matches your brand’s look and feel, without being limited to a web-based flow. This can lead to a better user experience and higher conversion rates. By building your own UI, you have more control, but it also means you must be mindful of your PCI compliance obligations. Our SDKs ensure sensitive card data is tokenized directly with our vault, but we recommend you review your PCI SAQ scope as part of your implementation.

​
What’s next?

This is just the beginning of our investment in the native mobile experience. Our roadmap includes support for 3DS, APMs, and additional pre-built components. To get started, check out the new Swift and Kotlin SDKs on GitHub. We also released 3 sample client apps for SwiftUI, UIKit, and Kotlin, to allow for a quick exploration of the SDK functionality.
​
2025-07-30
API
Feature

​
Update Transaction Data

We’ve released a powerful new feature that allows you to update transaction data after a transaction has been created. This provides a crucial new level of flexibility for data management.

​
What’s new?

Previously, transaction data was largely immutable and could only be updated by our internal system during payment processing or via webhooks. This meant that simple updates, like adding an order ID for reconciliatio was not possible. To solve this, we have introduced a new API endpoint, PUT /transactions/{id}, that allows for direct updates to specific fields on a transaction resource.

​
How it works

A merchant can now programmatically update a transaction’s external_identifier, metadata, and connection_options. This is perfect for adding an internal order ID after a payment is authorized or for enriching a transaction with metadata required for a reconciliation process.To update a transaction, make a PUT request to the /transactions/{id} endpoint with the fields you wish to change. This requires the transactions.write scope.
Important: Updating metadata is a replace operation, not a merge. You must provide the complete metadata object in your request.
curl -X PUT https://api.gr4vy.com/transactions/{transaction_id} \
  -H "Authorization: bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "external_identifier": "order-id-12345",
    "metadata": {
      "new_key": "new_value",
      "another_key": "another_value"
    }
  }'
Every update made via this endpoint is tracked. A new transaction event is created for every change, and we log which API key initiated the update. All changes are captured in an audit log for full visibility.

​
Limitations

This update does not allow for editing or refunds and payment methods, as they are separate resources.
​
2025-07-25
ConnectorBraintreeVenmo
Feature

​
Venmo: Recurring payments & other enhancements

We’ve upgraded our Venmo (via Braintree) integration to our latest connector framework which brings with it improved performance, reliability, and new features to one of our most important payment methods for US-based merchants.

​
What’s new?

Our Venmo connector, which is powered by Braintree, has been completely rebuilt. This upgrade was prioritized to support key merchants who rely on Venmo for both one-time and recurring donations and payments.Key supported features in this new version include:
  • One-time transactions: Standard Venmo payments for web checkouts.
  • Recurring transactions: Support for vaulted payment methods to enable ongoing donations and subscriptions.
  • Transaction Sync: More reliable synchronization of transaction statuses between Gr4vy and Braintree.
  • Billing data ingestion: Allowing a merchant to ingest billing details from a Venmo account*. Please see limitations below for more details.

​
Why it matters

Venmo is a critical payment method for engaging with a younger, mobile-first demographic in the United States. By upgrading this connector, we are ensuring our merchants have a robust and scalable solution for both one-time and recurring payments. This is especially important for non-profits, subscription-based services, and any merchant looking to build long-term relationships with their customers.

​
What’s next?

This upgrade is the first part of an exxciting two-phase plan for Venmo, more on that soon! For now, all merchants using our Venmo via Braintree connector will benefit from the improved features of this connector. Please refer to our Venmo connector documentation for any configuration questions.
​
2025-07-24
API
Enhancement

​
Richer error responses for voids & captures

We’ve enhanced our API to provide you with more actionable insight when a void or capture action fails. You can now opt-in to receive a detailed response object that explains exactly why the action could not be completed.

​
What’s new?

Previously, when a POST /transactions/{transaction_id}/void or POST /transactions/{transaction_id}/capture request failed at the payment service provider level, our API would return the original transaction object with its status unchanged. To understand the reason for the failure, you had to check the Gr4vy dashboard.Now, you can receive a dedicated transaction-void or transaction-capture response object. This new object clearly states the status of the action (e.g., failed, declined) and provides the same rich error details you’re used to seeing for failed payments, including:
  • code: A standardized Gr4vy error code.
  • raw_response_code: The raw error code from the PSP.
  • raw_response_description: The raw error message from the PSP.

​
Why it matters

This enhancement gives you direct, programmatic access to the outcome of void and capture attempts. Instead of relying on manual checks in the dashboard, your system can now automatically handle failures by:
  • Triggering automated retries for temporary service errors.
  • Alerting internal teams to investigate specific declines.
  • Providing more context to your support staff without leaving your own systems.
This ultimately reduces manual overhead and allows you to build more resilient payment operations.

​
How it works

This feature is an opt-in enhancement to ensure full backward compatibility with existing integrations. To receive the new, detailed response objects, you need to include a Prefer header in your API request.
  • To get the new response for a void request, include the following header: Prefer: resource=transaction-void
  • To get the new response for a capture request, include this header: Prefer: resource=transaction-capture
If the Prefer header is not included, the API will continue to return the standard transaction object, just as it does today.

​
Example failure response

Here is an example of the new transaction-void object that is returned when a void action fails and the Prefer header is used.
{
  "type": "transaction-void",
  "status": "failed",
  "code": "service_error",
  "raw_response_code": "1001",
  "raw_response_description": "Internal error, please retry",
  "transaction": {
    "type": "transaction",
    "id": "1a032928-abc0-4fb8-971e-fb917291e75f"
    // ... all other transaction fields
  }
}
For more information on how to use this feature, please refer to our updated reference documentation for the void and capture endpoints
​
2025-07-17
ConnectorBuckaroo
Feature

​
Buckaroo: Card

We are pleased to announce the launch of our new connector for Buckaroo, a leading payment service provider in the Netherlands. This initial integration focuses on card payments and was developed to support the specific needs of our enterprise client, Corendon Airlines.

​
About Buckaroo

Founded in 2005, Buckaroo is a major Dutch PSP that provides a comprehensive suite of payment solutions for thousands of businesses.

​
Why this matters

  • Gateway to the Dutch Market: This provides our merchants with a direct connection to a key payment provider in the Netherlands, helping them to increase local payment acceptance and conversion.
  • Enterprise-Ready: Built and tested to meet the needs of Corendon Airlines, our sales teams can confidently position this connector for other large-scale businesses, particularly in the travel and e-commerce sectors.

​
Integration details

The initial version of our Buckaroo connector supports the most of the common features for card payments, except digital wallets, airline data, and open loop cascading.Please direct merchants to our official documentation for full configuration details. This new connector is a significant addition to our portfolio and a great talking point for engaging with prospects targeting the Dutch market.
​
2025-07-15
Embed
Enhancement

​
New in Embed: Real-time BIN events

To give our merchants more control over the checkout experience, we have launched a powerful new event in Embed, namely BIN Events.

​
What’s new?

Merchants can now subscribe to a new event that fires in real-time as a customer enters their card number into Embed. This event provides key information about the card’s Bank Identification Number (BIN) as soon as we can determine it. This allows for a dynamic and responsive checkout that can be tailored on the fly based on the customer’s card details.

​
How it works

As a user types a card number into the Embed element, a cardDetailsChanged event will be triggered whenever our system identifies a change in the card’s details.The event payload will include:
  • 6-digit BIN: The first six digits of the card number.
  • Scheme: The card network (e.g., visa, mastercard, amex).
  • Card Type: The type of card (e.g., credit, debit, prepaid).
The event will fire multiple times if the determination changes as more digits are entered (e.g., from Visa to Mastercard), providing the most up-to-date information at all times.

​
Merchant use cases & benefits

This feature unlocks several valuable use cases:
  • Dynamic UI: Merchants can now display the card specific UI the instant it’s recognized, improving user confidence and customization.
  • Early Card Validation: Prevent a user from completing the form if they are using an unsupported card scheme, reducing errors and saving the customer time.

​
Getting started

This feature is available now for all merchants using Embed. They can implement it by adding a JavaScript event listener to their frontend code.
​
2025-07-14
ConnectorAdyen
Feature

​
Adyen: BLIK

We’re excited to announce that we have expanded our payment method offerings by adding support for BLIK, which is now available for merchants to configure through our Adyen connector.

​
What is BLIK?

BLIK is the dominant mobile payment system in Poland, used by over 90% of all customers of Polish financial institutions. It allows users to make instant, secure payments for online shopping, in-store purchases, and cash withdrawals without needing a physical card. Instead of card details, transactions are authorized using a unique, 6-digit code generated within the user’s mobile banking app. Given its massive adoption and preference among Polish consumers, supporting BLIK is a critical step for any merchant looking to increase conversion in this market.

​
How does the customer flow work?

The payment process is designed to be fast and secure:
  • At checkout, the customer selects BLIK as their payment method.
  • The customer opens their mobile banking app on their smartphone to generate a unique, 6-digit BLIK code.
  • They enter this code into the payment interface on the merchant’s site.
  • The customer receives a push notification in their banking app to confirm the transaction details and approves the payment.
  • The entire process is seamless and typically completed in seconds.

​
Why this matters to you

Unlock the Polish Market: By offering Poland’s most popular payment method, merchants can significantly reduce friction at checkout and increase conversion rates for Polish customers.
  • No Additional Integration: Merchants already using our Adyen connection can enable BLIK with a simple configuration change in our admin panel—no development work required.
  • Increased Security: The two-step authentication process (code generation and in-app confirmation) provides a high level of security for both the merchant and the customer.

​
Getting started

Merchants who wish to offer BLIK to their customers can now enable it within their Adyen connector settings in our admin panel.
​
2025-06-26
ConnectionMerchant Warrior
Change

​
Merchant Warrior

We are excited to announce the launch of our new direct integration with Merchant Warrior, a premier Australian payment gateway that provides robust and flexible payment solutions for merchants worldwide.

​
About Merchant Warrior

Founded in 2009, Merchant Warrior is a Brisbane-based fintech that offers a comprehensive suite of payment products, including credit/debit card processing, direct debit, multi-currency support, and enhanced security features. Their platform is designed to help businesses increase revenue, reduce fraud, and leverage the latest in payment technology. Our new connector empowers you to process card payments directly through our platform, taking advantage of Merchant Warrior’s powerful infrastructure while keeping your checkout flow seamless and secure.

​
Integration

Our new integration supports card payments including 0-dollar authentication, delayed captures, Apple and Google Pay, and more. For more details see our Merchant Warrior guide.
​
2025-06-26
EmbedNotice
Change

​
New partial_match_name AVS response

We have added a new possible avs_response_code value to our transaction API.The value partial_match_name is now returned for some connectors when a name matched is returned. This is mainly related to American Express payments.
​
2025-06-26
EmbedNotice
Change

​
Changes to transactionCancelled event in Embed

Expected release date: July 17, 2025
We will be changing the payload for the transactionCancelled event raised by Embed to contain more data. This change will roll out to all merchants during the regular release cycle.

​
Background

Embed has an event handler called onEvent(). This parameter allows to listen to transactionCancelled events, which are raised when the Apple Pay / Google Pay payment sheets are dismissed.
setup({
  onEvent: (name, data) => {
    if (name === "transactionCancelled") {
      // inspect data
    }
  },
});
Currently, these events include a data payload that is a string.
"Apple Pay: Session cancelled"
This is inconsistent with other payloads where data is an object.

​
Changes

With this change, the new data payload will return an object instead of a string.
{
  "type": "cancellation",
  "method": "apple_pay",
  "message": "Session cancelled"
}

​
Impact

Please check if you are expecting the data property to be a string. For example, your code might perform a check to see if data === 'Apple Pay: Session cancelled'.Instead, please check any of the new object’s properties, for example data.method === 'applepay' && data.type === 'cancellation'.
​
2025-06-25
ConnectorAffirm
Feature

​
Affirm

We have added support a direct connection to Affirm.Affirm is a “buy now, pay later” service that allows consumers to purchase items and split the cost into a series of installments. Offered at the checkout of numerous retailers, it provides shoppers with short-term, often interest-free payment plans, or longer-term loans for larger purchases that may carry interest. This model serves as an alternative to traditional credit cards, allowing for immediate purchase while managing payments over time, with Affirm paying the merchant upfront and assuming the repayment risk.
​
2025-06-20
SDKsDocs
Feature

​
New SDKs for C#, Go, Java, PHP, Python, and TypeScript

We’re thrilled to announce a significant milestone for our developer experience: the launch of a full suite of new server-side SDKs, now available for Java, TypeScript, Python, Go, C#, and PHP.This is a huge step forward in making integrations with our API faster, more reliable, and more consistent. These SDKs are automatically generated and updated, which marks a fundamental shift in how we build and maintain them.

​
✨ Major documentation enhancements

To support the new SDKs, we have launched a comprehensive update to our public documentation.Key highlights include:
  • SDK Code Samples on Every Endpoint: Every API reference page now features ready-to-use code samples for all six new SDKs, making it easier than ever for developers to get started.
  • Refreshed Look & Feel: The documentation now features a cleaner navigation and improved structure. Guides have been reorganized into a new dashboard tab, and API-specific pages are now located directly under the API Reference section for better accessibility.
  • AI-Powered Assistance: We have integrated support for ChatGPT, Claude, and other LLMs on every page, enabling developers to ask questions and receive instant help.
  • Interactive API Playground: The Mintlify-powered API playground is now available, allowing users to make live API calls directly from the documentation.
​
2025-06-02
FlowDashboard
Feature

​
Split routing conditions

We now support an additional mechanism for A/B testing through Flow. We have introduced a new Flow condition that enables merchants to split traffic between rules based on a configurable percentage.With this new condition, merchants can route only a specified percentage of traffic to a rule, with unmatched traffic cascading to subsequent rules in the list.

​
FAQ

  • What happens if the rule has other conditions as well? The rule will only trigger if all other conditions are also met. For example, a 20% condition will route 20% of the traffic that matches all other criteria.
  • Can I chain multiple Flow rules with this new condition? Yes, you can chain multiple Flow rules with percentage-based routing. For instance, if you have rule A and rule B, each with a 20% condition, rule B will apply to 20% of the remaining 80% that did not match rule A. In other words (assuming no other rules or conditions):
    • Rule A: 20% of traffic matches
    • Rule B: 20% of the remaining 80% = 16% of traffic matches
    • Remaining: 64% of traffic continues to other rules or follows default behavior
​
2025-05-22
ConnectorWorldpay
Feature

​
Worldpay: WPG

Worldpay WPG is now available as a card connector. Worldpay’s Worldwide Payment Gateway is our second integration with Worldpay after VAP. While VAP focuses on the US market, WPG is available globally and supports processing in any currency, local debit schemes, and more. This connector was developed in close collaboration with Worldpay and is fully certified.
​
2025-05-22
ConnectorNuvei
Feature

​
Nuvei: iDEAL

We have added support for iDEAL via Nuvei.iDEAL is the leading online payment method in the Netherlands, enabling consumers to pay for purchases through direct online transfers from their bank accounts. At checkout, users are securely redirected to their online banking environment to authorize the transaction, providing merchants with real-time payment confirmation. This process is highly secure, as no financial details are shared.Nuvei is a global payment technology company offering a comprehensive suite of payment solutions. Its platform enables merchants to accept a wide variety of payment methods, manage payouts, and utilize services such as card issuing, risk management, and analytics. Nuvei helps businesses connect with customers across more than 200 markets through a single integration.
​
2025-05-08
Account UpdaterAPI
Feature

​
Real-time account updater

We now have support for a real-time account (RTAU) updater for Visa and Mastercard cards.An Account Updater provides a card inquiry service at the schemes. It’s an API that can be called to retrieve an update to a card. We previously had implemented the Batch Account updater (BAU), which allows cards to be scheduled for updates which then arrive a few days later. This worked but was not cost-effective for us or our merchants.A real-time account update instead provides immediate updates from the issuers on the validity and existence of cards. It functions the same way as batch account updater, in the sense that the same responses are provided, it is however real time and functions as a great tool to recover transactions. As part of this update we also made a slew of extra enhancements to ensure we don’t retry cards previously marked as dead, to both the RTAU and BAU.
​
2025-05-07
SettlementPayPal
Feature

​
PayPal settlement reporting

We now have support for settlement reporting through PayPal.Settlement reporting provides merchants with detailed information about the settlement of their PayPal transactions. This includes data on when funds are transferred, the amounts settled, and any associated fees or adjustments. With this feature, merchants can more easily reconcile their PayPal transactions, track settlement timelines, and ensure accurate financial reporting.To enable PayPal settlement reporting or to learn more about how to access these reports, please refer to our PayPal settlement documentation or contact your support representative.
​
2025-04-28
ObservabilityDashboard
Feature

​
Transaction request logging

API log
We now display the original HTTP request body and headers on the dashboard, as well as the corresponding API response for each transaction.This enhancement enables merchants to gain deeper insight into the exact payloads sent to our API and the responses returned. With this feature, platforms can more effectively support their customers, making it easier to diagnose and resolve any issues that may arise during API integration.The logging includes API calls for the original authorization or sale request, as well as any subsequent capture, void, or refund operations. It does not include events that were not accepted, such as those resulting from invalid JWTs, invalid requests (e.g., missing parameters), or insufficient permissions. These 4XX errors can be found in our API logs.
​
2025-04-15
Webhooks
Feature

​
Webhook signatures

We now support signatures for webhooks. These signatures enable verification of the authenticity and integrity of received webhook notifications. By validating the webhook signature, merchants can ensure that notifications originate from our system and have not been tampered with by unauthorized parties.For further guidance on secrets management, signature verification, and signature rotation, please refer to the documentation.
​
2025-04-15
FlowDashboard
Enhancement

​
Numeric metadata conditions in Flow

We now support numeric metadata conditions in Flow. This enhancement enables merchants to pass numeric metadata values via the transaction API and perform numeric comparisons to drive logic within Flow.Previously, only string comparisons of metadata were possible. To address this limitation, a new Flow condition has been introduced that allows for numeric comparisons against metadata values. Please note that while the API continues to accept only string values, Flow will automatically convert these values to numeric form for comparison purposes.
​
2025-04-02
OXXOConnector
Feature

​
OXXO Pay connector

We now offer support for OXXO Pay, a widely used voucher-based payment method in Mexico.OXXO Pay enables customers to complete online purchases by generating a unique reference code, which can be used to pay in cash at any OXXO convenience store. Upon selecting OXXO Pay at checkout, customers receive this reference code and instructions for payment. Since payments are made in person, there is an inherent processing delay until the payment is confirmed by OXXO and the funds are settled.Merchants can leverage the default hosted payment flow provided by us, which displays the reference code and payment instructions to the customer. Alternatively, merchants may configure a custom approval URL to present their own branded barcode or reference page.OXXO Pay is an important payment option for merchants seeking to reach consumers in Mexico who prefer or require cash-based payment methods. For further details on enabling and configuring OXXO Pay, please refer to the OXXO Pay documentation.
​
2025-03-28
API
Enhancement

​
Merchant advice codes

We now support Merchant Advice Codes (MACs), a feature introduced by Mastercard to provide merchants with greater insight into declined transactions. MACs are two-digit codes included in transaction responses that indicate the specific reason for a decline and offer recommendations regarding subsequent actions, such as whether a transaction may be retried.For example, a MAC of "01" signifies “New account information available.” Payment service providers (PSPs) pass this code through in the transaction response, and we now read and return this value to merchants via our API. This enhancement is also planned for integration with our Real-Time Account Updater (RTAU) functionality.Merchant Advice Codes are now available through both the API and the dashboard, and have been enabled for Cybersource, Mastercard, Checkout, Adyen, and Stripe connections.
​
2025-03-19
LatitudeGemConnectorWorldlineConnector
Feature

​
Latitude and Gem Interest Free

We have launched new connectors to support Latitude Interest Free (Australia) and Gem Interest Free (New Zealand). These integrations enable merchants to offer eligible Latitude and Gem cardholders the ability to split purchases into interest-free instalments at checkout.By supporting these payment options, merchants can provide greater flexibility to consumers, potentially increasing conversion rates and average order values. For more information on enabling Latitude or Gem Interest Free, please refer to the relevant connector documentation or contact your support representative.
​
2025-03-19
LatitudeGemConnectorWorldlineConnector
Feature

​
”Worldline TravelHub gateway

We are pleased to announce the release of our connector for Worldline TravelHub, a payment gateway specifically designed for the travel industry. Worldline TravelHub provides access to a broad range of payment methods, including both card payments and numerous local and alternative payment methods (LPMs and APMs). This gateway is generally available to merchants operating within the travel sector.With this new connector, we now support card payments through Worldline TravelHub, in addition to previously supported payment methods such as iDEAL and Sofort. The connector offers a comprehensive set of features, including direct capture, support for both partial and full refunds, airline data fields, cart itemization, and more.This enhancement was developed in response to merchant requests, including those from Corendon, and is intended to provide greater flexibility and functionality for travel merchants processing payments globally.For further information on enabling and configuring the Worldline TravelHub Card connector, please refer to the official documentation or contact your support representative.
​
2025-03-12
PayoutsAdyen
Feature

​
Original Credit Transaction (OCT) payouts via Adyen

We now support Original Credit Transaction (OCT) payouts through Adyen. This enhancement expands our existing payout capabilities, which previously included support for Checkout and Nuvei.OCT payouts allow merchants to send funds directly to customer cards, enabling use cases such as:
  • Refunds outside the context of a purchase
  • Disbursements for insurance claims
  • Prize or reward payments
  • Marketplace seller payouts
With the addition of Adyen as a payout provider, merchants now have greater flexibility in choosing the optimal payment processor for their specific payout needs based on factors such as geographic coverage, pricing, and existing integrations.For more information on implementing OCT payouts via Adyen, please refer to our payouts documentation or contact your support representative.
For updates prior to this date, please reach out to our support team for our backlog of newsletter updates.