Updates & Announcements

​

Native 3DS for mobile

​

What’s new?

• Native Mobile 3DS Integration: A native 3DS SDK has been integrated into native iOS and Android SDKs, allowing merchants to handle the 3DS challenge entirely within their native app UI, eliminating jarring web-view redirects.
• Checkout Sessions 3DS Extension: The Checkout Sessions API has been extended to support 3DS authentication independently of a transaction, with new internal endpoints providing the necessary data to kick off the 3DS flow directly on the client side.
• 3DS at Vaulting: Merchants can now perform 3DS authentication at the time of vaulting a card, ensuring payment methods are authenticated and “transaction-ready” before a buyer even reaches the final checkout step.

​

Why it matters

• Total UI Control: Merchants can maintain their app’s theme and look-and-feel throughout the entire payment process.
• Seamless Transitions: No more switching between native code and web views; the entire challenge happens in-app.
• Reduced Friction: Authenticating cards during vaulting simplifies the final checkout, as the 3DS requirement is handled upfront.

​

How it works

1. Store: The mobile app stores card data securely in a Checkout Session.
2. Authenticate: The app calls the new Checkout Sessions 3DS endpoint to retrieve the data needed for the native challenge.
3. Challenge: The Native Mobile SDK uses the native 3DS integration to handle any challenge with the buyer’s bank.
4. Finalize: The resulting 3DS data is stored back in the Checkout Session, which can then be used to create a successful, authenticated transaction server-side.

​

Custom 3DS authentication amounts

​

What’s new?

• Decoupled Authentication Amounts: Merchants can now trigger a 3DS challenge for a total amount that exceeds the amount being authorized in the immediate transaction.
• New API Syntax: A new field, three_d_secure.amount, has been added to the /transactions request, allowing merchants to set the desired authentication value. The API returns the same field to confirm the amount used for the 3DS handshake.
• Validation Guards: To ensure processing integrity, the system returns a client-side validation error (HTTP 4xx, for example 422 Unprocessable Entity) if a merchant attempts to authenticate for an amount lower than the transaction amount.

​

Why it matters

​

How it works

1. Authentication: Gr4vy passes this custom amount to the 3DS provider/directory server.
2. Authorization: The payment processor receives only the standard amount defined for that specific transaction.
3. Reuse: The 3DS data returned in the response (CAVV, ECI, etc.) remains valid for the higher authenticated amount, allowing the merchant to pass this data to other providers or ancillary services via vault forwarding.

​

Inbound webhooks visibility

​

What’s new?

• Webhook Event Logs: Every incoming webhook received from a Payment Service Provider (PSP) or external system is now surfaced as a distinct transaction event on the transaction timeline.
• Payload Inspection: Merchants can inspect the raw headers and body of the inbound webhook directly from the Dashboard.
• Intelligent Transaction Linking: The system automatically identifies and links incoming callbacks to the correct transaction. To maintain a clean audit trail, events are only created when a definitive match to an existing transaction is found.

​

Why it matters

• Self-Service Debugging: Teams can now verify webhook delivery and inspect payloads directly, without reaching out to support or checking internal logs.
• Full Audit Trail: Every transaction lifecycle is now fully transparent, covering both the requests Gr4vy sends out and the updates received back.
• Faster Issue Resolution: Technical teams can quickly identify malformed payloads or mismatched references that might prevent a transaction from updating correctly.

​

How it works

1. Ingestion: Gr4vy processes the incoming request and attempts to resolve it to a specific Transaction ID.
2. Event Creation: If a match is found, a new transaction event is added to the Transaction Detail view.
3. Review: In the Events section of the Dashboard, you can click the event to view the full details of the webhook, including the exact data received from the provider.

​

Wero via Nuvei

​

What is Wero?

• The Unified Solution: Wero is designed to be the preferred, unified European alternative to non-European providers like Visa, Mastercard, and PayPal.
• Bank-Backed: It is heavily promoted by major banks across Europe as a secure, instant, and frictionless way to handle person-to-person (P2P), online shopping, and physical store payments.
• Instant Payments: Leveraging the SEPA Instant Credit Transfer scheme, Wero ensures that funds are transferred in real-time between bank accounts.

​

Why it matters

​

European roll-out timeline

• Live Now (Late 2024 - Early 2025): Already operational in Belgium, Germany, and France.
• Upcoming (2026): Scheduled to go live in the Netherlands and Luxembourg.
• Future Outlook: Wero aims to become the “go-to” digital wallet for all instant payments across Europe, expanding its footprint as more banks join the initiative.

​

How it works

​

Important note for sandbox testing

​

3D Secure data in Vault Forwarding

​

What’s new?

• New Template Variables: You can now inject specific 3DS fields into your Vault Forwarding request body or headers using new template keys:
  • {{ CARD_3DS_CAVV_1 }}: The Cardholder Authentication Verification Value
  • {{ CARD_3DS_ECI_1 }}: The Electronic Commerce Indicator
  • {{ CARD_3DS_VERSION_1 }}: The version of the 3DS protocol used
  • {{ CARD_3DS_RESPONSE_1 }}: The final authentication result (for example, Y)
  • {{ CARD_3DS_SERVER_TRANSACTION_ID_1 }}: The 3DS Server Transaction ID
  • {{ CARD_3DS_SCHEME_1 }}: The card scheme authenticated (for example, visa)
• Context Awareness: These variables are only available when the Vault Forwarding request is initiated using a valid checkout_session_id that contains 3DS results. Requests attempting to use these templates with a stored payment method (card ID) return a validation error.

​

Why it matters

​

How it works

{
  "card": {
    "number": "{{ CARD_NUMBER }}",
    "expiry": "{{ CARD_EXPIRATION_DATE_MM }}/{{ CARD_EXPIRATION_DATE_YY }}"
  },
  "authentication": {
    "cavv": "{{ CARD_3DS_CAVV_1 }}",
    "eci": "{{ CARD_3DS_ECI_1 }}",
    "xid": "{{ CARD_3DS_SERVER_TRANSACTION_ID_1 }}"
  }
}

​

Adyen APM direct mode support

​

What’s new?

• Platform Upgrade: The following Adyen connectors have been upgraded to our latest platform:
  • Cash App
  • Alipay
  • Sofort
• Direct Mode Support: All Adyen APM connectors now support “Direct Mode” integrations for iOS, Android, and Web, allowing merchants to use Adyen’s native Drop-in SDKs directly within their mobile apps or websites.
• Enhanced Features: The upgrade includes support for advanced features such as transaction logging and recurring payments where supported by the underlying payment method.

​

Why it matters

​

How it works

1. Initialize: The Gr4vy API provides the necessary session data to initialize the Adyen SDK on your client (iOS, Android, or Web).
2. Process: The native SDK handles the user interaction.
3. Complete: The transaction is synchronized and finalized through the Gr4vy API, ensuring a unified transaction record in your dashboard.

​

Tokenize & store payment instruments via payment links

​

What’s new?

• Existing Buyer Support: When creating a payment link, you can now specify a buyer_id or buyer_external_identifier, linking the transaction to an existing buyer record in your system.
• Tokenization & Storage: You can now enable the storing of payment methods (e.g., credit cards) on a payment link, allowing customers to save their card details for future use during the checkout process.
• Configurable Embed Options: New flags have been added to control the checkout experience, allowing you to specify if the “store card” option should be displayed and if specific billing address fields should be collected.

​

Why it matters

​

How it works

​

Limitations

• Tokenization Only: The payment link is designed to capture and tokenize a new card or payment method.
• No “Card on File” Selection: When the buyer opens the payment link, they will not see a list of their previously saved cards to choose from. They must enter payment details for the current transaction.

​

OAuth authentication for outbound webhooks

​

What’s new?

• OAuth Support: Merchants can now configure their webhook subscriptions to use OAuth authentication.
• Supported Grant Types: Both client_credentials and password grant types are supported.
• Configuration Fields: The webhook subscription setup now includes fields for:
  • OAuth Token URL
  • Client ID
  • Client Secret
  • Username (for password grant type)
  • Password (for password grant type)

​

Why it matters

​

How it works

1. Token Request: Before delivering a webhook event, Gr4vy calls the specified OAuth Token URL using the provided credentials (Client ID/Secret, and optionally Username/Password).
2. Authentication: The external system validates the credentials and returns a Bearer token.
3. Delivery: Gr4vy includes this token in the Authorization header of the webhook request and delivers the payload to your subscription URL.

​

Enhanced refund details & error visibility

​

What’s new?

• For successful refunds: All relevant identifiers are displayed, including the payment_service_refund_id and external_identifier, along with the Refund ID and Reconciliation ID.
• For failed refunds: In addition to the status, the dashboard now clearly displays the Raw Response Code—the exact code returned by the PSP (e.g., E104)—along with descriptive error messages.

​

Why it matters

​

Who is it for?

​

PayFac support for Cybersource

​

What’s new?

• PayFac Data Fields: The Cybersource connector now supports specific data fields required for the PayFac model, including the ability to send aggregatorInformation (such as Aggregator ID and Name) and detailed subMerchant information.
• Configuration-Based Logic: These fields are managed directly within the connector configuration to ensure compliance and data integrity, ensuring that the correct PayFac and sub-merchant identities are consistently applied to every transaction.

​

Why it matters

​

How it works

​

Fiserv CardPointe connector

​

What’s new?

• Fiserv CardPointe Support: A new integration to the CardPointe Gateway, a comprehensive payment platform owned by Fiserv (formerly First Data). CardPointe is widely used by merchants for its robust terminal management, virtual terminal capabilities, and unified reporting across payment channels.
• Seamless Integration: This connector allows merchants to process card payments directly through the CardPointe API using their existing credentials.
• Full Transaction Lifecycle: The connector supports all standard card processing operations, including authorizations, captures, voids, and refunds.

​

Why it matters

​

How it works

​

ISO response codes & smarter retries

​

What’s new?

• New Data Field: A new field, iso_response_code, has been added to transaction data, storing the raw response code returned by the acquirer (e.g., 05, 51) directly from the authorization response.
• Connector Updates: Major card connectors (including Stripe, Mastercard, Braintree, Cybersource, Adyen, and others) have been updated to pass this raw code back to Gr4vy whenever it is provided by the PSP.
• Optimized Retry Logic: The retry logic now uses this ISO code as the primary “source of truth.”

​

Why it matters

• Stop Futile Retries: Instantly identify “hard declines” (like a stolen card or closed account) that should never be retried, saving processing resources.
• Maximize Approvals: Accurately identify “soft declines” (like temporary system outages) that are safe and likely to succeed on a retry.

​

How it works

1. Check: The system checks if the connector returns an iso_response_code.
2. If present: The specific code is evaluated to determine if the error is retriable. If the code indicates a hard decline (or if the connector explicitly flags skip_retry=true), processing stops immediately. If it indicates a temporary issue, the retry proceeds.
3. If absent: The system falls back to existing retry logic based on standard mapped error codes.

​

Enhanced filtering capabilities

​

What’s new?

​

Why it matters

​

How it works

1. Filter: Click on the filter icon for Status, Payment method, or Connection.
2. Multi-select: Use the checkboxes to select one or multiple items from the list.
3. Search: Use the search bar within the dropdown to find specific connections or methods quickly.
4. Bulk Actions: Use the new “Clear all” buttons at the top of the dropdown to instantly reset your selection.

​

Chase settlement reporting

​

What’s new?

• Transaction Coverage: The integration captures Deposits (Action code DP) and Refunds (Action code RF).
• File Parsing: Specifically targets the ACT0010 (Settlements) and ACT0002 (Settlement failures) file types within the daily batch.
• Currencies: The system currently maps settlement currency directly to gross and net currency (supporting USD and CAD).

​

Why it matters

​

How it works

​

Direct APM integrations

​

The problem with redirects

​

What’s new: The “Direct Integration” flow

1. Initiate Transaction: When creating a transaction, merchants can now pass an integration_client parameter with a value of web, android, or ios (instead of the default redirect).
2. Get Session Token: For any of these values, the Gr4vy API will return a session_token in the response, indicating that a direct integration session has been started.
3. Fetch Session Data: From the client-side (website or mobile app), merchants can call the new POST /transactions/{id}/session endpoint, passing the session_token.
4. Render Widget: The API responds with the specific data (e.g., keys, session IDs) required to initialize the APM’s own native widget or SDK. Merchants can then render the APM’s payment experience directly within their own UI.

​

Available now: Trustly direct

​

SPEI via Monato

​

What’s new?

• New Connector for Monato: A new connector has been added to the platform to integrate with the Monato payment service.
• SPEI Payment Support: This connector is specifically designed to process SPEI (Sistema de Pagos Electrónicos Interbancarios) transactions. This is a “push payment” method, where the customer is provided with details to complete the payment from their own bank account.
• Flexible Approval URL: To provide merchants with greater control over the customer experience, this connector allows a custom approval URL to be set either as a credential or as a connection option, similar to capabilities in other connectors.

​

Why it matters

​

How it works

​

Anti-Fraud Silent Mode

​

What’s new?

• Active vs Silent: Designate one anti-fraud service as “active” (its decision controls transaction flow) and run any number of additional services in “silent mode” (decisions recorded but not enforced).
• Asynchronous Processing: Silent mode checks happen in the background with zero impact on checkout performance.
• Full Visibility: Silent service decisions appear as separate events on transaction timelines, allowing side-by-side comparison with your active service.

​

Why it matters

• Risk-Free Testing: Compare new anti-fraud providers against your current solution using real transaction data.
• Model Warm-Up: Machine learning-based fraud services perform better when trained on live data. Silent mode lets you warm up new services for weeks or months before activation.
• Zero Impact: Because processing is asynchronous, customer checkout experience remains fast and unaffected.

​

How it works

​

Additional Level 2 & Level 3 Data Support

​

What’s new?

• L2 data: merchant_tax_id, purchase_order_number, customer_reference_number, tax_amount, duty_amount, shipping_amount
• L3 data: tax_exempt, description, duty_amount, shipping_amount

​

Why it matters

• Reduce Processing Costs: Qualify for lower interchange fees on B2B/B2G transactions
• Reduce Fraud & Chargebacks: Additional data provides greater transparency and validation
• Improve Reporting: Provide corporate and government clients the detailed data required for accounting and expense management

​

How it works

​

Chargeback Visibility via Settlement Reports

​

What’s new?

• Dashboard Integration: Chargebacks ingested via settlement reports now appear in your dashboard
• Quick Filter: New “disputed” filter on the transaction dashboard shows all transactions with chargebacks or chargeback reversals
• API Endpoints: Separate endpoints for chargebacks and chargeback reversals
• Transaction Association: Chargebacks are separate entities (similar to settlements) attached to transactions, not transaction statuses

​

Why it matters

​

How it works

​

Limitations

​

Fiserv PayFac Support

​

What’s new?

• PayFac API Integration: Full support for Fiserv’s PayFac API, providing a robust and compliant payment processing solution for Payment Facilitators
• Payment Facilitator Data: Pass additional data fields required for PayFac models, including paymentFacilitator information and sub-merchant details
• Zero-Dollar Authorizations: Corrected implementation for zero-dollar authorizations, essential for card verification and tokenization

​

Why it matters

​

How it works

​

UPI connector via dLocal

​

What’s new?

​

Why it matters

• Market Expansion: UPI is the fastest-growing payment method in India, making it essential for merchants targeting the Indian market.
• Increased Conversion: Offering UPI at checkout reduces friction for customers familiar with this payment method, leading to higher conversion rates.
• Regulatory Compliance: The integration includes support for PAC-B regulations in India, which may require tax identification for transactions above a certain threshold.

​

How it works

​

Recurring UPI Payments via dLocal

​

What’s new?

• Recurring UPI Mandates: Customers can authorize recurring payments via UPI, creating a mandate for future automated debits
• Seamless Subscription Billing: Automated billing cycles for subscription-based services and products in the Indian market
• Automated Payment Flow: After initial authorization, future payments are processed automatically with 24-hour advance notification to customers

​

Why it matters

​

How it works

​

BlueSnap Card Connector

​

What’s new?

• Global Coverage: Payment processing from all over the world
• Recurring Payments: Easy setup and management of subscription-based payments
• 3D Secure: Extra layer of security for online transactions
• Anti-Fraud: Built-in fraud prevention capabilities

​

Why it matters

​

How it works

​

Settlement reporting: dLocal

​

What’s new?

​

Why it matters

• Accurate Reconciliation: Merchants can easily match their transaction records with settlement data, simplifying financial reconciliation processes.
• Financial Visibility: Gain detailed insights into settlement timelines and amounts, enabling better financial planning and forecasting.
• Operational Efficiency: Streamlined reporting reduces manual reconciliation work and improves accuracy.

​

How it works

​

Klarna connector upgrade

​

What’s new?

​

Why it matters

• Recurring Payments: Merchants can now process subscription and recurring payment use cases with Klarna, expanding their business models.
• Enhanced Data: Transactions now include richer data, providing better insights into payment flows and customer behavior.
• Framework Benefits: The migration brings all the improvements inherent to our new connector framework, ensuring consistency and reliability across platforms.

​

How it works

​

Insights Dashboard: Authentication Tab

​

What’s new?

• Where authentications occur and their outcomes
• Issuer behaviors and liability shift implications
• Impact of your 3DS/SCA rules on conversion
• Friction points in the checkout process

​

Key capabilities

• Cross-filter feature to deep dive across multiple variables
• Same presets, sharing, and download capabilities as other insights tabs
• Understand the impact of authentication rules on transaction conversion

​

How it works

​

Insights Dashboard Presets

​

What’s new?

• Save Presets: Store your selected filters as named presets linked to your merchant account
• Preset Menu: Access saved presets from a dropdown for quick switching between views
• Manage Presets: Delete presets you no longer need
• Share Data: Share preset links with team members for collaborative analysis
• Download Data: Export filtered data as an Excel file for external analysis

​

Why it matters

​

How it works

​

iDEAL via Buckaroo Connector

​

What’s new?

• iDEAL 2.0: Modern issuer selection on a hosted page for a seamless, secure checkout experience
• Direct Captures: Immediately capture funds after authorization
• Full & Partial Refunds: Flexible refund management
• Deep Links: Redirect customers to mobile apps after successful payment

​

Why it matters

​

How it works

​

Stripe Card Connector API Upgrade

​

What’s new?

• Enhanced Digital Wallets Flow: Improved processing for digital wallet transactions
• Better Network Token Support: Streamlined network token handling
• More Efficient API Integration: Optimized communication with Stripe’s latest APIs

​

Why it matters

• Improved Performance: Faster and more efficient APIs result in quicker transaction processing
• Enhanced Security: Latest APIs include additional security enhancements protecting against fraud
• Better Reliability: More stable with fewer errors, ensuring consistent service
• Future-Proof: Ensures access to new Stripe features and capabilities as they’re released

​

How it works

​

Sardine Anti-Fraud Connector

​

What’s new?

• Device Fingerprinting: Advanced device intelligence and behavioral biometrics for enhanced transaction security
• Review Queue & Webhooks: Manage suspicious transactions directly from Sardine dashboard with real-time notifications
• Post-Transaction Events: Send transaction events to Sardine for improved fraud scoring and customer journey insights

​

Why it matters

• Reduced Fraud: AI-powered platform helps reduce fraud losses and automate manual review processes
• Improved Compliance: Meet compliance obligations and reduce money laundering risks
• Enhanced Customer Experience: Reduce friction and false positives for smoother checkout

​

How it works

​

Chase Orbital Connector Upgrade

​

What’s new?

• Network Token Support: Improved authorization rates and reduced fraud risk
• Digital Wallets: Apple Pay and Google Pay support for more payment options
• Modern Framework: Migration to latest platform framework with enhanced capabilities

​

Why it matters

​

How it works

​

PSE via Nuvei Connector

​

What’s new?

• Real-time Bank Transfers: Secure, real-time payments directly from customer bank accounts
• Wide Bank Coverage: Supported by a large number of Colombian banks
• Secure Authentication: Customers authenticate directly in their banking environment

​

Why it matters

​

How it works

​

3DS: Failover orchestration

​

What’s new?

• New 3DS Server: Enhanced multi-provider support with modern 3DS protocols (2.3 and above) and broader scheme coverage, including EFTPOS.
• Failover Orchestration: An intelligent orchestration layer routes 3DS requests between multiple providers, automatically failing over to ensure continued service availability if one provider experiences issues.
• Provider Preference: Gr4vy can configure a preferred 3DS provider for each instance, providing more control over 3DS setup and enabling merchants to leverage specific features of each provider.

​

Why it matters

• Improved Reliability: The failover orchestration makes the 3DS service more resilient to outages.
• Enhanced Scheme Support: Access to a wider range of 3DS schemes, including EFTPOS and Cartes Bancaires, is critical for merchants in Australia and France.
• Future-Proofing: Support for the latest 3DS protocols ensures compatibility with new features and security enhancements.

​

How it works

​

3DS support for Cartes Bancaires

​

What’s new?

​

Why it matters

• Increased Security: 3DS adds an extra layer of authentication, protecting merchants from fraudulent transactions and reducing chargeback risk.
• Regulatory Compliance: Offering 3DS is a key requirement for processing payments in Europe and ensures merchants can meet their obligations when serving French customers.
• Improved Customer Trust: Displaying the Cartes Bancaires logo and offering a secure 3DS flow increases customer confidence, leading to higher conversion rates.

​

How it works

​

Postal Code Field in Secure Fields

​

What’s new?

• Optional Postal Code Field: Dedicated input for secure postal/zip code collection
• Flexible Configuration: Can be marked as required or optional
• Supported in Multiple Scenarios: Works with new cards and stored card CVV re-entry

​

Why it matters

• Higher Authorization Rates: Postal code is critical for AVS checks, significantly improving authorization success
• Reduced Friction: Fewer payment declines means smoother checkout experience
• Secure Collection: PCI-compliant data collection reduces compliance scope

​

How it works

​

PANTsights BIN Service Fallback Mechanism

​

What’s new?

• Delta Validation: Failsafes prevent application of faulty BIN file changes with excessive deltas
• Pattern Matching: Rudimentary pattern matching for when BIN lookup fails, ensuring transactions proceed with main scheme
• Provider Verification: Issues with large deltas trigger verification requests to BIN data provider

​

Why it matters

• Improved Reliability: Fallback mechanisms ensure card transactions process even with incomplete or faulty BIN data
• Reduced Failures: Pattern matching resolves ERP system issues for many merchants
• Data Integrity: Validation gates prevent bad BIN updates from affecting transaction processing

​

How it works

​

Secure Fields: postal code support

​

What’s new?

• New Cards: When a customer is entering the details for a new card.
• Stored Cards: When a customer is using a stored card and is only required to re-enter their CVV.

​

Why it matters

• Higher Authorization Rates: The postal code is a critical component of Address Verification Service (AVS) checks. Including it in a transaction significantly increases the likelihood of a successful authorization from the issuing bank.
• Improved Customer Experience: By collecting the postal code upfront, merchants can reduce payment declines and the friction associated with failed transactions, leading to a smoother checkout process for their customers.
• Secure Data Collection: Like all Secure Fields, the postal code field isolates sensitive data from the merchant’s environment, helping to reduce their PCI compliance scope while still collecting the necessary information.

​

How it works

​

Adyen: auto-rescue cancellation

​

What’s new?

​

Why it matters

• Improved Customer Experience: Merchants can now prevent unnecessary declines on an old card when a customer has already provided a new one. This avoids confusing payment failures and reduces customer churn.
• Increased Control: This new endpoint gives merchants more granular control over the payment lifecycle, allowing them to intervene in automated processes when necessary.

​

How it works

​

Moneris connector

​

Why it matters

• Canadian Market Expansion: This integration provides merchants with a direct connection to a key player in the Canadian payments landscape, enabling them to offer a seamless and trusted payment experience to their Canadian customers.
• Enterprise-Ready: Built to the specifications of a global events leader, this connector is ready to support high-volume, complex payment needs.
• Digital Wallet Support: The connector supports decrypted Apple Pay and Google Pay, allowing merchants to offer a frictionless checkout experience to their customers.

​

Integration details

​

Nuvei: Przelewy24 connector

​

What’s new?

​

Why it matters

​

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.

​

Kount: KHASH token connector

​

What’s new?

​

Why it matters

• Reduce your PCI Scope: Generate a KHASH without having the raw card number reach 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

• 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 the API.
• Receive the KHASH: the connector returns 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.

​

Changes to transactionCreated event in Embed and mobile SDKs

​

Background

setup({
  onEvent: (name, data) => {
    if (name === "transactionCreated") {
      // inspect data
    }
  },
});

{
  "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

{
  "type": "transaction",
  "id": "7099948d-7286-47e4-aad8-b68f7eb44591",
  "status": "authorization_succeeded"
}

​

Impact

​

Richer error responses for refunds

​

What’s new?

• 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.

​

Why it matters

• 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.

​

How it works

​

True Native Mobile SDKs for iOS & Android

​

What’s new?

• 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

​

What’s next?

​

Update Transaction Data

​

What’s new?

​

How it works

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"
    }
  }'

​

Limitations

​

Venmo: Recurring payments & other enhancements

​

What’s new?

• 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

​

What’s next?

​

Richer error responses for voids & captures

​

What’s new?

• 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

• Triggering automated retries for temporary service errors.
• Alerting internal teams to investigate specific declines.
• Providing more context to support staff without leaving internal systems.

​

How it works

• 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

​

Example failure response

{
  "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
  }
}

​

Buckaroo: Card

​

About Buckaroo

​

Why this matters

• Gateway to the Dutch Market: This provides 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 to meet the needs of enterprise merchants, this connector is ready for large-scale deployments, particularly in the travel and e-commerce sectors.

​

Integration details

​

New in Embed: Real-time BIN events

​

What’s new?

​

How it works

• 6-digit BIN: The first six digits of the card number.
• Scheme: The card network (for example, Visa, Mastercard, American Express).
• Card Type: The type of card (for example, credit, debit, prepaid).

​

Merchant use cases & benefits

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

​

Getting started

​

Adyen: BLIK

​

What is BLIK?

​

How does the customer flow work?

• 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

• No Additional Integration: Merchants already using the Adyen connection can enable BLIK with a simple configuration change in the administrator 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

​

Merchant Warrior

​

About Merchant Warrior

​

Integration

​

New partial_match_name AVS response

​

Changes to transactionCancelled event in Embed

​

Background

setup({
  onEvent: (name, data) => {
    if (name === "transactionCancelled") {
      // inspect data
    }
  },
});

"Apple Pay: Session cancelled"

​

Changes

{
  "type": "cancellation",
  "method": "apple_pay",
  "message": "Session cancelled"
}

​

Impact

​

Affirm

​

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

​

✨ Major documentation enhancements

• 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: Support for ChatGPT, Claude, and other LLMs has been integrated 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.

​

Split routing conditions

​

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

​

Worldpay: WPG

​

Nuvei: iDEAL

​

Real-time account updater

​

PayPal settlement reporting

​

Transaction request logging

​

Webhook signatures

​

Numeric metadata conditions in Flow

​

OXXO Pay connector

​

Merchant advice codes

​

Latitude and Gem Interest Free

​

Worldline TravelHub gateway

​

Original Credit Transaction (OCT) payouts via Adyen

• Refunds outside the context of a purchase
• Disbursements for insurance claims
• Prize or reward payments
• Marketplace seller payouts