{"id":16481,"date":"2026-06-10T11:04:02","date_gmt":"2026-06-10T09:04:02","guid":{"rendered":"https:\/\/docs.centralpay.com\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/"},"modified":"2026-08-24T11:16:55","modified_gmt":"2026-08-24T09:16:55","slug":"optimize-the-frictionless-rate","status":"publish","type":"docs","link":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/","title":{"rendered":"Optimize the Frictionless Rate"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">What is \u201cfrictionless\u201d?<\/h2>\n\n<p class=\"wp-block-paragraph\">Authentication is considered \u201c<strong>frictionless<\/strong>\u201d when the cardholder&#8217;s bank approves the transaction <strong>without any interaction on the cardholder&#8217;s part<\/strong> (no challenge: no one-time code and no confirmation in the banking app). The bank authenticates \u201csilently,\u201d based on the data received and its own risk analysis (<em>Risk-Based Authentication<\/em>). <\/p>\n\n<p class=\"wp-block-paragraph\">It serves two purposes:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><strong>Better conversion<\/strong>: no extra steps for the carrier, so fewer dropouts.<\/li>\n\n\n\n<li><strong>Liability Shift<\/strong>: As with successful challenge-based authentication, a successful frictionless transaction (<code>transStatus = Y<\/code>) shifts liability for fraud to the card issuer. This is what distinguishes it from a payment without 3DS. <\/li>\n<\/ul>\n\n<pre class=\"wp-block-preformatted\">\u2139\ufe0f <strong>The final decision always rests with the issuer bank<\/strong>. No approach guarantees a frictionless experience: the issuer may require verification regardless of your integration. The strategies below <strong>maximize the chances<\/strong> of a frictionless experience; they do not guarantee it. <\/pre>\n\n<h2 class=\"wp-block-heading\">Lever 1 \u2014 Enhance authentication data<\/h2>\n\n<p class=\"wp-block-paragraph\">This is the most important lever. The more reliable contextual data about the user that the authentication request (<code>3ds2\/authentication<\/code>) contains, the better the bank can evaluate the risk and the more likely it is to provide frictionless access. Reverse, a minimal request (amount + browser data only) deprives the bank of the information it would need to bypass the challenge.  <\/p>\n\n<p class=\"wp-block-paragraph\">All of the fields below are accepted by the API <strong>in both BRW and 3RI<\/strong> formats and are marked as \u201c<em>Recommended<\/em>\u201d or \u201c<em>Conditional<\/em>\u201d (to be submitted as soon as the information is available):<\/p>\n\n<p class=\"wp-block-paragraph\"><strong>Contact information for the cardholder<\/strong><\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>Role<\/th><\/tr><\/thead><tbody><tr><td><code>email<\/code><\/td><td>cardholder&#8217;s email address (conditional: to be sent unless restricted by local regulations)<\/td><\/tr><tr><td><code>homePhone<\/code> \/ <code>mobilePhone<\/code> \/ <code>workPhone<\/code><\/td><td>cardholder&#8217;s phone numbers (area code <code>[cc]<\/code> + number <code>[subscriber]<\/code>)<\/td><\/tr><tr><td><code>deliveryEmailAddress<\/code><\/td><td>delivery email (for electronic delivery)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\"><strong>Billing and shipping address<\/strong><\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>Role<\/th><\/tr><\/thead><tbody><tr><td><code>billAddrLine1\/2\/3<\/code>, <code>billAddrCity<\/code>, <code>billAddrPostCode<\/code>, <code>billAddrState<\/code>, <code>billAddrCountry<\/code><\/td><td>billing address<\/td><\/tr><tr><td><code>shipAddrLine1\/2\/3<\/code>, <code>shipAddrCity<\/code>, <code>shipAddrPostCode<\/code>, <code>shipAddrState<\/code>, <code>shipAddrCountry<\/code><\/td><td>shipping address<\/td><\/tr><tr><td><code>shipAddressUsageInd<\/code><\/td><td>length of time the shipping address has been in use<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\"><strong>Customer account history<\/strong><\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>Role<\/th><\/tr><\/thead><tbody><tr><td><code>chAccAgeInd<\/code>, <code>chAccDate<\/code>, <code>chAccChange<\/code><\/td><td>the account holder&#8217;s account age and the date of the last change made to the account with the merchant<\/td><\/tr><tr><td><code>paymentAccAge<\/code>,  <code>paymentAccInd<\/code><\/td><td>length of time the payment method has been registered<\/td><\/tr><tr><td><code>nbPurchaseAccount<\/code><\/td><td>number of purchases over the past six months<\/td><\/tr><tr><td><code>provisionAttemptsDay<\/code><\/td><td>Number of attempts to add a card in a 24-hour period<\/td><\/tr><tr><td><code>preOrderDate<\/code>,  <code>preOrderPurchaseInd<\/code><\/td><td>pre-order information, if applicable<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<pre class=\"wp-block-preformatted\">\ud83d\udca1 Practical tip: Share <strong>all the reliable information you have<\/strong>. Inconsistent data (such as an incorrect address) is counterproductive; missing reliable data is a missed opportunity for a frictionless experience. <\/pre>\n\n<h2 class=\"wp-block-heading\">Lever 2 \u2014 Run the 3DS Method<\/h2>\n\n<p class=\"wp-block-paragraph\">Whenever <em>versioning<\/em> allows it, always run the <strong>3DS Method<\/strong>: it enables the bank to collect the technical fingerprint of the cardholder\u2019s browser in the background, which directly feeds into its risk analysis. Skipping this step deprives the bank of information that promotes a frictionless experience. See the procedure on the <a href=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/transaction-initiated-by-the-holder-cit-brw\/\">BRW<\/a> page.  <\/p>\n\n<h2 class=\"wp-block-heading\">Lever 3 \u2014 Expressing a preference and reporting exemptions<\/h2>\n\n<p class=\"wp-block-paragraph\">The <code>threeDSRequestorChallengeInd<\/code> field (optional, BRW flow) allows you to indicate your challenge preference to the bank and to specify that an exemption applies:<\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Value<\/th><th>Meaning<\/th><\/tr><\/thead><tbody><tr><td><code>01<\/code><\/td><td>No preference<\/td><\/tr><tr><td><code>02<\/code><\/td><td>No challenge desired<\/td><\/tr><tr><td><code>03<\/code><\/td><td>Desired challenge (merchant&#8217;s preference)<\/td><\/tr><tr><td><code>04<\/code><\/td><td>Desired challenge (required)<\/td><\/tr><tr><td><code>05<\/code><\/td><td>No challenge \u2014 transactional risk analysis (TRA) already completed<\/td><\/tr><tr><td><code>06<\/code><\/td><td>No challenge \u2014 data sharing only<\/td><\/tr><tr><td><code>07<\/code><\/td><td>No challenge \u2014 strong customer authentication (SCA) already completed<\/td><\/tr><tr><td><code>08<\/code><\/td><td>No challenge \u2014 \u201ctrusted beneficiary\u201d exemption (whitelist)<\/td><\/tr><tr><td><code>09<\/code><\/td><td>No challenge \u2014 invitation to whitelist if a challenge is required<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<pre class=\"wp-block-preformatted\">\u26a0\ufe0f <strong>The values <code>05<\/code>, <code>07<\/code> and <code>08<\/code> indicate that an exemption applies.<\/strong> Use them only if the corresponding exemption actually applies to your configuration: incorrectly declaring an exemption makes you liable and may result in a <em>soft decline<\/em> (see <a href=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/faq-3ds-2-2\/\">FAQ<\/a>). If in doubt, use <code>01<\/code> or <code>02<\/code>. <\/pre>\n\n<p class=\"wp-block-paragraph\">The field <code>whiteListStatus<\/code> also allows you to indicate the merchant&#8217;s &#8220;trusted beneficiary&#8221; status (<code>Y<\/code> = merchant whitelisted by the cardholder, <code>N<\/code>,  <code>E<\/code>,  <code>P<\/code>,  <code>R<\/code>,  <code>U<\/code>). When a cardholder adds your merchant to their trusted list with their bank, their subsequent payments go through more smoothly and frictionless.<\/p>\n\n<h2 class=\"wp-block-heading\">Lever 4 \u2014 Properly implement merchant-initiated transactions (MIT)<\/h2>\n\n<p class=\"wp-block-paragraph\">Once an initial CIT transaction has been authenticated, <strong>subsequent transactions initiated by the merchant (MIT)<\/strong> are processed via the <a href=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/transaction-initiated-by-the-holder-cit-brw\/\">3RI<\/a> flow and are no longer subject to strong authentication. This is one of the most direct ways to reduce friction in recurring, installment, or future payments: authenticate once (CIT), then reuse (MIT).  <\/p>\n\n<h2 class=\"wp-block-heading\">What&#8217;s beyond your control<\/h2>\n\n<p class=\"wp-block-paragraph\">Even with complete data and a requested exemption, the issuer may decide to issue a challenge (<em>step-up<\/em>). If you attempt an authorization without authentication (via exemption) and the issuer denies it, you will receive a <strong>soft decline<\/strong>: you must then retry the transaction with authentication. See the corresponding entry in the <a href=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/faq-3ds-2-2\/\">FAQ<\/a>.  <\/p>\n","protected":false},"excerpt":{"rendered":"<p>What is \u201cfrictionless\u201d? Authentication is considered \u201cfrictionless\u201d when the cardholder&#8217;s bank approves the transaction without any interaction on the cardholder&#8217;s part (no challenge: no one-time code and no confirmation in the banking app). The bank authenticates \u201csilently,\u201d based on the data received and its own risk analysis (Risk-Based Authentication). It serves two purposes: \u2139\ufe0f The [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":16466,"menu_order":3,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"doc_badge":[],"class_list":["post-16481","docs","type-docs","status-publish","hentry","no-post-thumbnail"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Optimize the Frictionless Rate - CentralPay Documentation<\/title>\n<meta name=\"description\" content=\"How to increase the frictionless 3DS authentication rate at CentralPay: enriching authentication data...\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Optimize the Frictionless Rate - CentralPay Documentation\" \/>\n<meta property=\"og:description\" content=\"How to increase the frictionless 3DS authentication rate at CentralPay: enriching authentication data...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/\" \/>\n<meta property=\"og:site_name\" content=\"CentralPay Documentation\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-24T09:16:55+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/documentation\\\/3ds-2-2-authentication\\\/optimize-the-frictionless-rate\\\/\",\"url\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/documentation\\\/3ds-2-2-authentication\\\/optimize-the-frictionless-rate\\\/\",\"name\":\"Optimize the Frictionless Rate - CentralPay Documentation\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/#website\"},\"datePublished\":\"2026-06-10T09:04:02+00:00\",\"dateModified\":\"2026-08-24T09:16:55+00:00\",\"description\":\"How to increase the frictionless 3DS authentication rate at CentralPay: enriching authentication data...\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/documentation\\\/3ds-2-2-authentication\\\/optimize-the-frictionless-rate\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/documentation\\\/3ds-2-2-authentication\\\/optimize-the-frictionless-rate\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/documentation\\\/3ds-2-2-authentication\\\/optimize-the-frictionless-rate\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/home\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentation\",\"item\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/documentation\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"3DS 2.2 authentication\",\"item\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/documentation\\\/3ds-2-2-authentication\\\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Optimize the Frictionless Rate\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/\",\"name\":\"CentralPay Documentation\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/#organization\",\"name\":\"CentralPay Documentation\",\"url\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/docs.centralpay.com\\\/wp-content\\\/uploads\\\/2023\\\/07\\\/logo-centralpay-2023.png\",\"contentUrl\":\"https:\\\/\\\/docs.centralpay.com\\\/wp-content\\\/uploads\\\/2023\\\/07\\\/logo-centralpay-2023.png\",\"width\":2382,\"height\":370,\"caption\":\"CentralPay Documentation\"},\"image\":{\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Optimize the Frictionless Rate - CentralPay Documentation","description":"How to increase the frictionless 3DS authentication rate at CentralPay: enriching authentication data...","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/","og_locale":"en_US","og_type":"article","og_title":"Optimize the Frictionless Rate - CentralPay Documentation","og_description":"How to increase the frictionless 3DS authentication rate at CentralPay: enriching authentication data...","og_url":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/","og_site_name":"CentralPay Documentation","article_modified_time":"2026-08-24T09:16:55+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/","url":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/","name":"Optimize the Frictionless Rate - CentralPay Documentation","isPartOf":{"@id":"https:\/\/docs.centralpay.com\/en\/#website"},"datePublished":"2026-06-10T09:04:02+00:00","dateModified":"2026-08-24T09:16:55+00:00","description":"How to increase the frictionless 3DS authentication rate at CentralPay: enriching authentication data...","breadcrumb":{"@id":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/optimize-the-frictionless-rate\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/docs.centralpay.com\/en\/home\/"},{"@type":"ListItem","position":2,"name":"Documentation","item":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/"},{"@type":"ListItem","position":3,"name":"3DS 2.2 authentication","item":"https:\/\/docs.centralpay.com\/en\/documentation\/documentation\/3ds-2-2-authentication\/"},{"@type":"ListItem","position":4,"name":"Optimize the Frictionless Rate"}]},{"@type":"WebSite","@id":"https:\/\/docs.centralpay.com\/en\/#website","url":"https:\/\/docs.centralpay.com\/en\/","name":"CentralPay Documentation","description":"","publisher":{"@id":"https:\/\/docs.centralpay.com\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/docs.centralpay.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/docs.centralpay.com\/en\/#organization","name":"CentralPay Documentation","url":"https:\/\/docs.centralpay.com\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/docs.centralpay.com\/en\/#\/schema\/logo\/image\/","url":"https:\/\/docs.centralpay.com\/wp-content\/uploads\/2023\/07\/logo-centralpay-2023.png","contentUrl":"https:\/\/docs.centralpay.com\/wp-content\/uploads\/2023\/07\/logo-centralpay-2023.png","width":2382,"height":370,"caption":"CentralPay Documentation"},"image":{"@id":"https:\/\/docs.centralpay.com\/en\/#\/schema\/logo\/image\/"}}]}},"author_avatar":"https:\/\/secure.gravatar.com\/avatar\/f26ba73d1afc0520e4b1044ff088c0eda58eeaf8c325f16e76f4f944099091cc?s=96&d=mm&r=g","author_name":"Victor","_links":{"self":[{"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/docs\/16481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/comments?post=16481"}],"version-history":[{"count":2,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/docs\/16481\/revisions"}],"predecessor-version":[{"id":16490,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/docs\/16481\/revisions\/16490"}],"up":[{"embeddable":true,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/docs\/16466"}],"wp:attachment":[{"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/media?parent=16481"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/doc_tag?post=16481"},{"taxonomy":"doc_badge","embeddable":true,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/doc_badge?post=16481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}