The latest product news, changes, and other announcements
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.
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.
Founded in 2005, Buckaroo is a major Dutch PSP that provides a comprehensive suite of payment solutions for thousands of businesses.
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.
To give our merchants more control over the checkout experience, we have launched a powerful new event in Gr4vy Embed: BIN Events.
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.
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:
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.
This feature unlocks several valuable use cases:
This feature is available now for all merchants using Embed. They can implement it by adding a JavaScript event listener to their frontend code.
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.
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.
The payment process is designed to be fast and secure:
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.
Merchants who wish to offer BLIK to their customers can now enable it within their Adyen connector settings in the Gr4vy admin panel.
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.
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 the Gr4vy platform, taking advantage of Merchant Warrior’s powerful infrastructure while keeping your checkout flow seamless and secure.
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.
partial_match_name
AVS responseWe 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.
Gr4vy 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.
Gr4vy 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.
Currently, these events include a data payload that is a string.
This is inconsistent with other payloads where data is an object.
With this change, the new data payload will return an object instead of a string.
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'
.
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.
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 Gr4vy 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.
To support the new SDKs, we have launched a comprehensive update to our public documentation.
Key highlights include:
Gr4vy now supports 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.
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.
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.
Gr4vy now has 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.
Gr4vy now has 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 Gr4vy support representative.
Gr4vy now displays 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.
Gr4vy now supports 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 Gr4vy 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.
Gr4vy now supports 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.
Gr4vy now offers 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 Gr4vy, 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.
Gr4vy now supports 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 Gr4vy now reads and returns 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.
Gr4vy has 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 Gr4vy support representative.
Gr4vy is 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, Gr4vy now supports 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 Gr4vy support representative.
Gr4vy now supports 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:
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 Gr4vy support representative.
For updates prior to this date, please reach out to our support team for our backlog of newsletter updates.