{"title":"Enable Adyen Uplift","category":"default","creationDate":1784905308,"content":"

Adyen Uplift<\/a> helps merchants strike a balance between conversion, risk, and cost. Adyen Uplift provides recommendations, experiments, and automation across five modules: Protect, Tokenize, Authenticate, Optimize, and Personalize.<\/p>\n

For your customers to benefit from Adyen Uplift, their integration must support specific features. This page explains which features to enable and what decisions you must make for each Adyen Uplift module. If you have not built a partner integration yet, start with the partner integration checklist<\/a>.<\/p>\n

Requirements<\/h2>\n

Before your customers can use any Adyen Uplift module, their integration must meet the following general requirements.<\/p>\n\n\n\n\n\n\n\n\n\n
Requirement<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
Integration type<\/strong><\/td>\nRecommended:
Webhooks<\/strong><\/td>\nAccept and process webhooks<\/a>.<\/td>\n<\/tr>\n
Application information<\/strong><\/td>\nInclude application information<\/a> in all payment requests.<\/td>\n<\/tr>\n
Shopper identifiers<\/strong><\/td>\nInclude shopperEmail<\/code> at minimum in payment requests. To get the best results, we highly recommend to also include fields such as shopperReference<\/code>, shopperIP<\/code>, and billingAddress<\/code>.<\/td>\n<\/tr>\n
Other fields<\/strong><\/td>\nFor a full list of required and recommended fields to include in payment requests, see Adyen Uplift requirements<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

How it works<\/h2>\n

Adyen Uplift consists of five modules. Each module requires you to enable specific features or make specific decisions. The following table shows an overview.<\/p>\n

\n \n\n\n\n\n\n\n\n\n\n
Module<\/th>\nWhat it does for your customers<\/th>\nWhat you need to do<\/th>\n<\/tr>\n<\/thead>\n
Protect<\/a><\/td>\nFraud management and risk optimization<\/td>\nEnable risk, dispute, and data collection features<\/td>\n<\/tr>\n
Tokenize<\/a><\/td>\nToken-based payments and card details management<\/td>\nEnable tokenization and account updater features<\/td>\n<\/tr>\n
Authenticate<\/a><\/td>\n3D Secure and authentication optimization<\/td>\nEnable 3D Secure 2 support<\/td>\n<\/tr>\n
Optimize<\/a><\/td>\nConversion and cost optimization through routing, data, and retries<\/td>\nEnable Enhanced Scheme Data, Intelligent Payment Routing, and Auto Rescue; configure payment methods<\/td>\n<\/tr>\n
Personalize<\/a><\/td>\nCheckout experience optimization<\/td>\nMake sure to use a supported Web integration type<\/a>, preferably the Sessions flow.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n\n

Protect<\/h2>\n

Enable the Protect module so that your customers can use Adyen's risk engine<\/a> to detect and prevent fraud, reduce chargebacks, and maximize authorization rates. Effective risk management directly increases net revenue: fewer false declines means that more legitimate payments go through, and fewer chargebacks means lower operational costs and potential scheme fines.<\/p>\n

For the best synergy with other modules, recommend your customers to enable premium features<\/a>.<\/p>\n

\n \n\n\n\n\n\n\n\n\n\n
Feature<\/th>\nWhat you need to do<\/th>\nYour decision<\/th>\nWho does what<\/th>\n<\/tr>\n<\/thead>\n
Risk profiles<\/td>\nSupport assigning a risk profile<\/a> to a merchant account or to individual payments.<\/td>\nDecide whether your customers can configure their own risk profile (configurable), or whether you apply a fixed profile for all customers (static).<\/td>\nYou build the feature. Your customers choose or fine-tune their risk profile.<\/td>\n<\/tr>\n
Disputes<\/td>\nSupport dispute and chargeback<\/a> management.<\/td>\nDecide whether you capture dispute webhooks centrally, or whether your customers manage disputes entirely from their Customer Area.<\/td>\nAdyen sends webhooks. You decide whether to process them. Your customers manage disputes from their Customer Area.<\/td>\n<\/tr>\n
Data collection<\/td>\nCollect device and behavior data to help detect fraud.<\/td>\nDecide whether to only include the risk data SDK in checkout pages (automatic for certain integration types), or to collect data from additional pages as well.<\/td>\nYou implement data collection. See fraud data collection<\/a>.<\/td>\n<\/tr>\n
Data quality<\/td>\nInclude as many recommended fields as possible in payment requests. High-quality data improves machine learning accuracy and reduces false declines. See risk field reference<\/a>.<\/td>\nNone. This is a best practice, not a toggle. The more data you include, the better Protect performs.<\/td>\nYou include the fields. Adyen uses them for risk evaluation.<\/td>\n<\/tr>\n
Manual transaction review<\/td>\nSupport manual review of flagged transactions.<\/td>\nDecide whether to offer case management. Requires Protect premium. If you do, listen to webhooks or use the API response to flag transactions.<\/td>\nYou build the feature. Your customers review flagged transactions. Adyen sends case management<\/a> webhooks.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n
\n

We recommend making risk configurable so that your customers can fine-tune their risk profile to their specific business needs.<\/p>\n<\/div>\n

How to enable Protect<\/h3>\n
    \n
  1. Include the risk enabled flag in your configuration object.<\/li>\n
  2. Implement fraud data collection<\/a> to automatically collect and send data such as device information, or send the data manually using riskData.clientData<\/code> in the payment request.<\/li>\n
  3. Include as many recommended fields as possible in payment requests to maximize data quality<\/a>. At minimum, include shopperEmail<\/code>, shopperReference<\/code>, shopperIP<\/code>, and billingAddress<\/code>.<\/li>\n
  4. Accept and process CHARGEBACK<\/a> and related dispute event webhooks<\/a>.<\/li>\n
  5. If you offer manual review, listen to case management webhooks and update the transaction status accordingly.<\/li>\n<\/ol>\n

    Tokenize<\/h2>\n

    Enable the Tokenize module so that your customers can securely store payment details<\/a> and use tokens for subsequent payments. Tokenization increases authorization rates because network tokens stay up to date when cards are renewed or replaced. This reduces involuntary churn for subscription businesses and improves the returning shopper experience.<\/p>\n

    \n \n\n\n\n\n\n\n\n\n
    Feature<\/th>\nWhat you need to do<\/th>\nYour decision<\/th>\nWho does what<\/th>\n<\/tr>\n<\/thead>\n
    Adyen tokenization<\/td>\nImplement tokenization<\/a> with the required fields: shopperReference<\/code>, storePaymentMethod<\/code>, recurringProcessingModel<\/code>, and shopperInteraction<\/code>. See recurring payment types<\/a>.<\/td>\nNone. This is required for the Tokenize module.<\/td>\nYou build the feature.<\/td>\n<\/tr>\n
    Network Tokenization<\/td>\nEnable network tokenization<\/a> for your customers. You can also manage network tokens yourself<\/a> to provision, update, and delete tokens on behalf of your customers.<\/td>\nDecide whether to offer this. It improves authorization rates but requires Adyen-side configuration. Also decide whether you manage tokens centrally or let your customers manage them.<\/td>\nYou work with your Adyen partner manager to enable it. Adyen configures it. You can manage tokens through the API.<\/td>\n<\/tr>\n
    Real Time Account Updater<\/td>\nSupport the Real Time Account Updater<\/a>. This is an optional paid feature. RTAU does not send webhooks. When it triggers a card update, read the updated card details from the payment response<\/a> and update your system accordingly.<\/td>\nDecide whether to support this. We recommend that you read additional data in the payment response so your system stays up to date when RTAU triggers a card update.<\/td>\nYour customers decide to enable RTAU (paid feature). You read updated card details from the payment response and update your system.<\/td>\n<\/tr>\n
    Batch Account Updater<\/td>\nUpdate stored card details in batch.<\/td>\nNot recommended due to setup complexity. Use the Real Time Account Updater instead.<\/td>\n-<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n

    How to enable Tokenize<\/h3>\n
      \n
    1. Implement tokenization<\/a> by including the required fields in payment requests.<\/li>\n
    2. If you offer Network Tokenization, work with your Adyen partner manager to enable it for your customers. Optionally, use the API to manage network tokens<\/a> yourself.<\/li>\n
    3. If your customers enable the Real Time Account Updater, read the updated card details from the payment response<\/a> and update your system accordingly.<\/li>\n<\/ol>\n

      Authenticate<\/h2>\n

      Enable the Authenticate module so that your customers can apply the right authentication<\/a> mechanism for each transaction to balance security, regulation, and conversion. Smart authentication reduces unnecessary friction for shoppers, which directly improves conversion rates. It also shifts fraud liability to the issuer for authenticated transactions.<\/p>\n

      \n \n\n\n\n\n\n\n\n\n\n\n
      Feature<\/th>\nWhat you need to do<\/th>\nYour decision<\/th>\nWho does what<\/th>\n<\/tr>\n<\/thead>\n
      Native 3D Secure 2<\/td>\nImplement native 3D Secure 2<\/a>.<\/td>\nChoose between native and redirect (or both). Native gives more control over the UX but requires regular upgrades.<\/td>\nYou build the feature.<\/td>\n<\/tr>\n
      Redirect 3D Secure 2<\/td>\nImplement redirect 3D Secure 2<\/a>.<\/td>\nChoose between native and redirect (or both). Redirect is quicker to implement and requires less maintenance.<\/td>\nYou build the feature.<\/td>\n<\/tr>\n
      Override 3D Secure per transaction<\/td>\nLet your customers override the 3D Secure decision for specific transactions.<\/td>\nDecide whether to expose this to your customers.<\/td>\nYou build the feature. Your customers use it per transaction.<\/td>\n<\/tr>\n
      Rule-based dynamic 3D Secure 2<\/td>\nLet your customers create rules to determine when to apply 3D Secure.<\/td>\nDecide whether to expose this to your customers.<\/td>\nYour customers set up dynamic 3D Secure<\/a> rules in their Customer Area.<\/td>\n<\/tr>\n
      Dynamic 3D Secure 2<\/td>\nAdyen's Authentication Engine<\/a> automatically decides when to apply 3D Secure for optimal conversion.<\/td>\nNone. This is included when you implement 3D Secure 2.<\/td>\nAdyen handles this automatically.<\/td>\n<\/tr>\n
      Risk-based authentication<\/td>\nIn combination with the Protect module, and when premium features are enabled, risk-based authentication<\/a> is enabled by default.<\/td>\nNone. This is included when you enable the Protect premium module in combination with 3D Secure 2.<\/td>\nAdyen handles this automatically.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n

      How to enable Authenticate<\/h3>\n
        \n
      1. Implement either native<\/a> or redirect<\/a> 3D Secure 2 (or both).<\/li>\n
      2. Make sure you handle the threeDS2<\/code> additional action in the payment response.<\/li>\n
      3. Include browserInfo<\/code> in payment requests for the Advanced flow.<\/li>\n<\/ol>\n

        Optimize<\/h2>\n

        Enable the Optimize module so that your customers can reduce cost and increase conversion through smart routing, data enrichment, and payment retries. Intelligent Payment Routing uses machine learning to select the lowest-cost or highest-converting route for each transaction. Enhanced Scheme Data lowers interchange fees on qualifying transactions. Auto Rescue recovers revenue from failed recurring payments by automatically retrying at the optimal time.<\/p>\n

        \n \n\n\n\n\n\n\n\n\n\n
        Feature<\/th>\nWhat you need to do<\/th>\nYour decision<\/th>\nWho does what<\/th>\n<\/tr>\n<\/thead>\n
        Enhanced Scheme Data (L2\/L3)<\/td>\nInclude Enhanced Scheme Data<\/a> in payment requests. Listen to webhooks for L2\/L3 data outcome.<\/td>\nDecide whether to offer this. It lowers interchange fees on US domestic card payments.<\/td>\nYou build the feature.<\/td>\n<\/tr>\n
        Payment methods<\/td>\nSupport co-badged cards<\/a> and let your customers add payment methods<\/a>.<\/td>\nDecide which payment methods to support.<\/td>\nYou build support for co-badged cards. Your customers choose which payment methods to enable.<\/td>\n<\/tr>\n
        Intelligent Payment Routing<\/td>\nUse machine learning to route each transaction to the highest-converting or lowest-cost acquirer or network. Requires at least two available routes (for example, a local scheme and an international scheme). No integration work is needed.<\/td>\nDecide whether to enable this for your customers. It is off by default and requires a one-click enablement in the Customer Area. For US and Australia, choose between: balance conversion and cost (recommended), prioritize cost, or prioritize conversion.<\/td>\nYou make sure multiple routes or MCCs are configured. Your customers enable routing optimization in their Customer Area under Uplift<\/strong> > Optimize<\/strong>. Adyen handles routing.<\/td>\n<\/tr>\n
        Smart Payment Messaging<\/td>\nAdyen optimizes issuer messaging (for example, CVC and AVS fields) to increase authorization rates on low-risk transactions.<\/td>\nThis is enabled by default. Your customers can adjust the optimization level in their Customer Area under Uplift<\/strong> > Optimize<\/strong>. Decide whether to expose this setting.<\/td>\nAdyen handles this automatically. Your customers can change the optimization level.<\/td>\n<\/tr>\n
        Auto Rescue<\/td>\nEnable Auto Rescue<\/a> to automatically retry failed recurring payments. This recovers revenue that would otherwise be lost to soft declines.<\/td>\nDecide whether to enable Auto Rescue per transaction or on the merchant account level.<\/td>\nYou choose the level (transaction or merchant account). Adyen retries the payment. You process the webhooks to update your system.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n
        \n

        The Excessive Retry Prevention Service (ERPS) blocks transactions that would incur Visa or Mastercard excessive retry penalty fees. It is opt-in, not priced, and in maintenance mode. ERPS can reduce scheme penalty fees but may have a negative impact on authorization rates. Contact your Adyen partner manager if your customers need this.<\/p>\n<\/div>\n

        How to enable Optimize<\/h3>\n
          \n
        1. Include Enhanced Scheme Data fields (additionalData.enhancedSchemeData<\/code>) in payment requests for US domestic card payments.<\/li>\n
        2. Listen to webhooks for L2\/L3 data outcome to verify that the scheme accepted the enhanced data.<\/li>\n
        3. Support co-badged cards<\/a> (Web Drop-in or Components v6.16.0 minimum, recommended v6.18.1).<\/li>\n
        4. If you offer Auto Rescue, enable it<\/a> per transaction or on the merchant account. Process the Auto Rescue webhooks to update your system with the retry outcome.<\/li>\n
        5. For Intelligent Payment Routing, make sure at least two routes (schemes or MCCs) are configured. Your customers enable routing optimization in their Customer Area. No integration changes are required.<\/li>\n
        6. Smart Payment Messaging works automatically. No integration changes are required.<\/li>\n<\/ol>\n

          Personalize<\/h2>\n

          Enable the Personalize module so that your customers can optimize the checkout experience for shoppers. This module includes dynamic payment method ordering<\/a> and checkout experiments<\/a>. Showing the right payment method at the right time increases conversion and reduces drop-off at checkout.<\/p>\n

          \n \n\n\n\n\n\n\n\n
          Feature<\/th>\nWhat you need to do<\/th>\nYour decision<\/th>\nWho does what<\/th>\n<\/tr>\n<\/thead>\n
          Dynamic Payment Method Ordering<\/td>\nDynamically order payment methods to optimize conversion or cost.<\/td>\nIf you use the Sessions flow, this works automatically. For the Advanced flow, make sure payment methods display in the same order as returned in the response.<\/td>\nAdyen determines the optimal order. You display it.<\/td>\n<\/tr>\n
          Experiments<\/td>\nLet your customers run A\/B tests on payment methods or ordering strategies.<\/td>\nNone. This is managed entirely from the Customer Area.<\/td>\nYour customers manage this. You do not need to make any changes.<\/td>\n<\/tr>\n
          Shopper conversion identifier<\/td>\nLink a shopper to a single checkout session for better personalization.<\/td>\nRequired for the Advanced flow. Include shopperConversionId<\/code> in \/payments<\/a> and \/paymentMethods<\/a> requests.<\/td>\nYou build this into the integration.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n
          \n

          If you use the Sessions flow, Personalize works automatically. For the Advanced flow, include shopperConversionId<\/code> to link a shopper to a single checkout session<\/a> and make sure payment methods display in the same order as returned in the API response.<\/p>\n<\/div>\n

          How to enable Personalize<\/h3>\n
            \n
          1. Include shopper identifiers in payment requests. At minimum, include shopperEmail<\/code>.<\/li>\n
          2. For the Advanced flow, generate and include a shopperConversionId<\/code> in the \/payments<\/a> and \/paymentMethods<\/a> requests.<\/li>\n
          3. Make sure the order of payment methods in the checkout matches the order returned in the payment methods response.<\/li>\n<\/ol>\n

            See also<\/h2>\n