{"id":16477,"date":"2024-06-27T15:08:54","date_gmt":"2024-06-27T13:08:54","guid":{"rendered":"https:\/\/docs.centralpay.com\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/"},"modified":"2026-08-20T17:09:08","modified_gmt":"2026-08-20T15:09:08","slug":"merchant-initiated-transaction-mit-3ri","status":"publish","type":"docs","link":"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/","title":{"rendered":"Merchant-initiated transaction (MIT \u2013 3RI)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The <strong>3RI<\/strong> (3DS Requestor Initiated) flow applies to merchant-initiated transactions (<strong>MIT<\/strong>): the merchant initiates the debit <strong>without the cardholder\u2019s involvement<\/strong>, under a pre-existing authorization, based on a previously authenticated CIT transaction.<\/p>\n\n<p class=\"wp-block-paragraph\">It covers all MIT scenarios: recurring billing, <strong>variable amounts<\/strong>, <em>usage-based<\/em> templates, <strong>one-time fees<\/strong>, and deferred debits (no-shows, penalties), not just fixed-rate subscriptions.<\/p>\n\n<p class=\"wp-block-paragraph\">\ud83d\udc49 If the cardholder is present and authorizes the payment themselves, <a href=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/transaction-initiated-by-the-holder-cit-brw\/\">use the BRW flow<\/a>. For information on the contractual framework, Strong Customer Authentication (SCA) exemptions, and the validity period of a CIT, see the <a href=\"https:\/\/docs.centralpay.com\/documentation\/documentation\/bonnes-pratiques\/merchant-initiated-transaction-mit\/\">Best Practices \u2014 Merchant Initiated Transaction (MIT)<\/a> page. <\/p>\n\n<h2 class=\"wp-block-heading\">1. Prerequisite: a CIT transaction that has already been authenticated<\/h2>\n\n<p class=\"wp-block-paragraph\">Since the cardholder is absent, the 3RI does not re-authenticate anyone: <strong>it reuses the authentication proof<\/strong> generated during a previous CIT transaction (with the cardholder present) carried out via the <a href=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/transaction-initiated-by-the-holder-cit-brw\/\">BRW<\/a> flow.<\/p>\n\n<p class=\"wp-block-paragraph\">During this CIT, the issuing bank&#8217;s server that authenticated the cardholder \u2014 the <strong>ACS<\/strong> (<em>Access Control Server<\/em>) \u2014 generated a unique identifier for this authentication: the<strong><code>acsTransID<\/code><\/strong>. This is the <code>acsTransID<\/code> that you will associate with each of your MITs to prove to the bank that the card was indeed authenticated for the first time with the cardholder&#8217;s consent.<\/p>\n\n<pre class=\"wp-block-preformatted\">\u26a0\ufe0f <strong>Keep the<\/strong> <code>acsTransID<\/code> from the CIT. Without a previously authenticated CIT \u2014 and therefore without <code>acsTransID<\/code> \u2014 a 3RI transaction cannot be completed. If you don't have one, first perform a CIT in <a href=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/transaction-initiated-by-the-holder-cit-brw\/\">BRW<\/a> to authenticate and tokenize the card. <\/pre>\n\n<h2 class=\"wp-block-heading\">2. (3RI) Authentication<\/h2>\n\n<p class=\"wp-block-paragraph\">The request is sent to the CentralPay API URL <code>3ds2\/authentication<\/code>, just like for the BRW flow, but with two key differences:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><strong>The channel is different.<\/strong> <code>deviceChannel=03<\/code> Indicates a transaction initiated by the merchant (3RI), without the cardholder using a browser. The <code>browser*<\/code> parameters in the BRW flow are therefore unnecessary here. <\/li>\n\n\n\n<li><strong>The CIT is referenced<\/strong>. The <code>acsTransID<\/code> value retained in step 1 is placed in the <strong><code>threeDSReqPriorRef<\/code><\/strong> field, which refers to \u201cthe previous authentication associated with this transaction.\u201d<\/li>\n<\/ul>\n\n<p class=\"wp-block-paragraph\"><strong>Card identification<\/strong>. Since the cardholder is not present, no card is scanned during the session: the card already stored for the customer (<code>Customer<\/code>) is referenced by transmitting <code>customerId<\/code> + <code>cardId<\/code>.<\/p>\n\n<pre class=\"wp-block-preformatted\">\ud83d\udca1 <strong>Send only one card source<\/strong>. Combining two sources (e.g., <code>cardId<\/code> + a token, or a PAN + a token) triggers the error \u201cThere is no unique source of card\u201d (see the <a href=\"https:\/\/docs.centralpay.com\/documentation\/documentation\/authentification-3ds-2-2\/faq-3ds-2-2\/\">FAQ<\/a>). <\/pre>\n\n<p class=\"wp-block-paragraph\"><strong>Sample (curl) :<\/strong><\/p>\n\n<pre class=\"wp-block-code\"><code class=\"\">curl --location --request POST 'https:\/\/test-api.centralpay.net\/v2\/rest\/3ds2\/authentication' \\\n--header 'Content-Type: application\/x-www-form-urlencoded' \\\n--header 'Authorization: Basic ZG9jdGVzdDo0STlISlJUZA==' \\\n--data-urlencode 'customerId=aae4d8c0-a555-4c2f-bfdf-18d5636b78a4' \\\n--data-urlencode 'cardId=44d0691b-b117-4799-ba07-31e0b02c5b08' \\\n--data-urlencode 'pointOfSaleId=08960d92-874b-4447-800b-aaa53fa976f5' \\\n--data-urlencode 'deviceChannel=03' \\\n--data-urlencode 'messageCategory=01' \\\n--data-urlencode 'acctType=03' \\\n--data-urlencode 'cardExpiryDate=9999' \\\n--data-urlencode 'purchaseAmount=4880' \\\n--data-urlencode 'purchaseCurrency=978' \\\n--data-urlencode 'purchaseExponent=2' \\\n--data-urlencode 'purchaseDate=20230101122345' \\\n--data-urlencode 'recurringExpiry=20330101' \\\n--data-urlencode 'recurringFrequency=1' \\\n--data-urlencode 'chAccAgeInd=03' \\\n--data-urlencode 'chAccChange=20220901' \\\n--data-urlencode 'chAccDate=20220901' \\\n--data-urlencode 'email=support@centralpay.eu' \\\n--data-urlencode 'nbPurchaseAccount=2' \\\n--data-urlencode 'paymentAccAge=20221001' \\\n--data-urlencode 'paymentAccInd=03' \\\n--data-urlencode 'threeDSReqPriorAuthMethod=02' \\\n--data-urlencode 'threeDSReqPriorAuthTimestamp=202209010123' \\\n--data-urlencode 'threeDSReqPriorRef=375d90ad-3873-498b-9133-380cbbc8d99d' \\\n--data-urlencode 'threeDSRequestorDecReqInd=N' \\\n--data-urlencode 'threeDSRequestorAuthenticationInd=02' \\\n--data-urlencode 'threeRIInd=01'\n<\/code><\/pre>\n\n<h3 class=\"wp-block-heading\">2.1. Explanation of the main parameters<\/h3>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Parameters<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr><td><code>deviceChannel<\/code><\/td><td><code>03<\/code> \u2192 3DS Requestor Initiated (transaction initiated by the merchant, without the cardholder using a browser)<\/td><\/tr><tr><td><code>messageCategory<\/code><\/td><td><code>01<\/code> \u2192 PA (Payment Authentication) = Authentication associated with a payment (e.g., recurring transaction)<br \/><code>02<\/code> \u2192 NPA (Non-Payment Authentication) = authentication that does not involve a payment (e.g., registration or card verification without a charge).<\/td><\/tr><tr><td><code>threeDSReqPriorRef<\/code><\/td><td><strong>must contain the <code>acsTransID<\/code> from the previous CIT (BRW) transaction<\/strong> (see step 1)<\/td><\/tr><tr><td><code>purchaseAmount<\/code><\/td><td>amount of the current purchase<\/td><\/tr><tr><td><code>purchaseCurrency<\/code><\/td><td>currency in ISO format<\/td><\/tr><tr><td><code>purchaseExponent<\/code><\/td><td>minor unit of the current currency<\/td><\/tr><tr><td><code>purchaseDate<\/code><\/td><td>date of purchase<\/td><\/tr><tr><td><code>recurringExpiry<\/code><\/td><td>the date after which no further authorizations may be issued<\/td><\/tr><tr><td><code>recurringFrequency<\/code><\/td><td>minimum number of days between two authorizations<\/td><\/tr><tr><td><code>acctType<\/code><\/td><td>account type (<code>03<\/code> = debit)<\/td><\/tr><tr><td><code>chAccAgeInd<\/code><\/td><td>length of time the account holder has had an account with the 3DS requester:<br \/><code>01<\/code> \u2192 no account<br \/><code>02<\/code> \u2192 created during the transaction<br \/><code>03<\/code> \u2192 less than 30 days<br \/><code>04<\/code> \u2192 between 30 and 60 days<br \/><code>05<\/code> \u2192 more than 60 days<\/td><\/tr><tr><td><code>chAccChange<\/code><\/td><td>date of the last change to the account holder&#8217;s account (format <code>YYYYMMDD<\/code>)<\/td><\/tr><tr><td><code>chAccDate<\/code><\/td><td>account holder&#8217;s account opening date (format <code>YYYYMMDD<\/code>)<\/td><\/tr><tr><td><code>nbPurchaseAccount<\/code><\/td><td>number of purchases made with this account over the past six months<\/td><\/tr><tr><td><code>paymentAccAge<\/code><\/td><td>date the payment account was credited to the account holder&#8217;s account<\/td><\/tr><tr><td><code>paymentAccInd<\/code><\/td><td><em>lenght of time the payment account has been registered:<\/em><br \/><code>01<\/code> \u2192 no account<br \/><code>02<\/code> \u2192 created during the transaction<br \/><code>03<\/code> \u2192 less than 30 days<br \/><code>04<\/code> \u2192 between 30 ans 60 days<br \/><code>05<\/code> \u2192 more than 60 days<\/td><\/tr><tr><td><code>threeDSReqPriorAuthMethod<\/code><\/td><td>Initial CIT Authentication Method: <br \/><code>01<\/code> \u2192 if frictionless<br \/><code>02<\/code> \u2192 if the cardholder has completed a challenge<br \/><code>03<\/code> \u2192 AVS<br \/><code>04<\/code> \u2192 other<\/td><\/tr><tr><td><code>threeDSReqPriorAuthTimestamp<\/code><\/td><td>date and time (UTC) of the previous authentication (format <code>YYYYMMDDHHMM<\/code>)<\/td><\/tr><tr><td><code>threeDSRequestorDecReqInd<\/code><\/td><td><code>N<\/code> \u2192 do not use decoupled authentication<\/td><\/tr><tr><td><code>threeDSRequestorAuthenticationInd<\/code><\/td><td><code>02<\/code> \u2192 recurring transaction<\/td><\/tr><tr><td><code>threeRIInd<\/code><\/td><td>Type of 3RI transaction:<br \/><code>01<\/code> \u2192 recurring transaction<br \/><code>02<\/code> \u2192 installment transaction<br \/><code>03<\/code> \u2192 add a card<br \/><code>04<\/code> \u2192 maintenance<br \/><code>05<\/code> \u2192 account verification<br \/><code>06<\/code> \u2192 split\/delayed shipment<br \/><code>07<\/code> \u2192 recharging<br \/><code>08<\/code> \u2192 mail-order sales<br \/><code>09<\/code> \u2192 telephone sales<br \/><code>10<\/code> check whitelist status<br \/><code>11<\/code> \u2192 other payment<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\"><strong>Sample of response:<\/strong><\/p>\n\n<pre class=\"wp-block-code\"><code class=\"\">{\n    \"threeDSServerTransID\": \"67dc456c-6c7a-987f-92cf-f68752525d0c\",\n    \"transStatus\": \"Y\",\n    \"eci\": \"02\",\n    \"contractId\": \"fb8736a5-8741-19b6-9d38-ec135888e0bf\"\n}\n<\/code><\/pre>\n\n<p class=\"wp-block-paragraph\">Here, <code>threeDSServerTransID<\/code> is the transaction ID generated by CentralPay (to be included in the transaction), and <code>eci<\/code> (<em>Electronic Commerce Indicator<\/em>) indicates the level of authentication achieved, which determines the transfer of liability in the event of fraud.<\/p>\n\n<h3 class=\"wp-block-heading\">2.2. Returned statuses (transStatus) and recommended course of action<\/h3>\n\n<p class=\"wp-block-paragraph\">The goal is to achieve <em>frictionless<\/em> authentication, that is, a <code>transStatus<\/code> = <code>Y<\/code>. Always try the 3RI first, then proceed according to the <code>transStatus<\/code> returned. <\/p>\n\n<pre class=\"wp-block-preformatted\">\u2139\ufe0f Support for 3RI depends on the card's scheme and the issuing bank's 3DS version: it is never guaranteed in advance. Hence the \u201cbest effort\u201d approach described below \u2014 you attempt 3RI, and you only rely on the result if it is positive. <\/pre>\n\n<p class=\"wp-block-paragraph\">\u2705 <strong>Authentication successful \u2014 use the results (transfer of responsibility)<\/strong><\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Status (<code>transStatus<\/code>)<\/th><th>Meaning<\/th><\/tr><\/thead><tbody><tr><td><strong>Y<\/strong><\/td><td>Authentication successful.<\/td><\/tr><tr><td><strong>A<\/strong><\/td><td>Attempt made. Not authenticated\/verified, but a proof of the attempt is provided. <\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">\u2192 Complete the transaction by submitting the 3DS data from the 3RI (see Step 3). Liability shifts to the issuer. <\/p>\n\n<p class=\"wp-block-paragraph\">\u26a0\ufe0f <strong>3RI failed \u2014 complete the transaction without authentication (\u201cbest effort\u201d)<\/strong><\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Status (<code>transStatus<\/code>)<\/th><th>Meaning<\/th><\/tr><\/thead><tbody><tr><td><strong>N<\/strong><\/td><td>Not authenticated\/unverified account.<\/td><\/tr><tr><td><strong>U<\/strong><\/td><td>Authentication\/verification failed (technical issue or other problem).<\/td><\/tr><tr><td><strong>I<\/strong><\/td><td>For informational purposes only.<\/td><\/tr><tr><td><strong>C<\/strong> \/ <strong>D<\/strong><\/td><td>Challenge requested (not possible in MIT because the cardholder is absent \u2014 see note below).<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">\u2192 You can perform the standard transaction without the 3RI data: the <code>Customer<\/code> (<code>customerId<\/code> + <code>cardId<\/code>) ensures automatic linking to the initial CIT. <strong>Please note<\/strong>: In this case, the transfer of responsibility does not apply (increased risk of dispute), and the risk of authorization denial is higher.<\/p>\n\n<pre class=\"wp-block-preformatted\">\u26a0\ufe0f <strong>MIT Challenge (C \/ D)<\/strong>. A challenge requires the cardholder to be present, which, by definition, is not the case with MIT. There are two scenarios: if the cardholder can return (e.g., subscription with a customer portal), reprocess a CIT in <a href=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/transaction-initiated-by-the-holder-cit-brw\/\">BRW<\/a> to re-authenticate the card; otherwise, treat it as an unsuccessful 3RI and complete the transaction without authentication (best effort). See <a href=\"https:\/\/docs.centralpay.com\/documentation\/documentation\/bonnes-pratiques\/merchant-initiated-transaction-mit\/\">Best Practices \u2014 MIT<\/a>.  <\/pre>\n\n<p class=\"wp-block-paragraph\">\u274c <strong>Explicit refusal \u2014 do not attempt the transaction<\/strong><\/p>\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Status (<code>transStatus<\/code>)<\/th><th>Meaning<\/th><\/tr><\/thead><tbody><tr><td><strong>R<\/strong><\/td><td>Authentication declined: the sender requests that you do not attempt to obtain authorization.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<p class=\"wp-block-paragraph\">\u2192 Do not complete the transaction, even without a 3RI.<\/p>\n\n<h2 class=\"wp-block-heading\">3. Transaction<\/h2>\n\n<p class=\"wp-block-paragraph\">Once 3RI authentication is successful (<code>Y<\/code> or <code>A<\/code>), enter the following 3DS data in the <code>transaction<\/code> call:<\/p>\n\n<ul class=\"wp-block-list\">\n<li><code>3ds[threeDSServerTransID]<\/code> = <code>threeDSServerTransID<\/code> <strong>generated by 3RI authentication<\/strong> (not the one from a previous transaction)<\/li>\n\n\n\n<li><code>3ds[status]<\/code> = <code>transStatus<\/code><\/li>\n\n\n\n<li><code>3ds[eci]<\/code> = <code>eci<\/code> (required if available)<\/li>\n\n\n\n<li><code>3ds[xid]<\/code> = custom parameter, free-form reference for merchants<\/li>\n<\/ul>\n\n<pre class=\"wp-block-preformatted\">\u26a0\ufe0f <strong>Do not send<\/strong> <code>3ds[cavv]<\/code> in3RI. The <code>cavv<\/code> (<em>Cardholder Authentication Verification Value<\/em>, the cryptogram that verifies authentication) is specific to the BRW stream; it is not included in the 3RI response and should not be transmitted here.<\/pre>\n\n<p class=\"wp-block-paragraph\"><strong>Sample (curl) :<\/strong><\/p>\n\n<pre class=\"wp-block-code\"><code class=\"\">curl --location --request POST 'https:\/\/test-api.centralpay.net\/v2\/rest\/transaction' \\\n--header 'Origin: https:\/\/example.centralpay.net' \\\n--header 'Authorization: Basic ZG9jdGVzdDo0STlISlJUZA==' \\\n--header 'Content-Type: application\/x-www-form-urlencoded' \\\n--data-urlencode 'currency=EUR' \\\n--data-urlencode 'amount=1500' \\\n--data-urlencode 'endUserIp=9.64.32.8' \\\n--data-urlencode 'endUserLanguage=ita' \\\n--data-urlencode 'merchantTransactionId=cpcg_12654de89ce44' \\\n--data-urlencode 'pointOfSaleId=1beb8574-cf4c-4b12-b065-d12b3f0eaa90' \\\n--data-urlencode 'browserUserAgent=Mozilla\/5.0 (iPhone; CPU iPhone OS 16_1_1 like Mac OS X) AppleWebKit\/605.1.15 (KHTML, like Gecko) Version\/16.1 Mobile\/15E148 Safari\/604.1' \\\n--data-urlencode 'browserAcceptLanguage=it_IT' \\\n--data-urlencode 'paymentRequestBreakdownId=5485d7e6-60c3-753c-94d3-682eaaf9ae6e' \\\n--data-urlencode 'email=support@centralpay.eu' \\\n--data-urlencode 'receiptEmail=support@centralpay.eu' \\\n--data-urlencode 'capture=true' \\\n--data-urlencode 'customerId=aae4d8c0-a555-4c2f-bfdf-18d5636b78a4' \\\n--data-urlencode 'cardId=44d0691b-b117-4799-ba07-31e0b02c5b08' \\\n--data-urlencode 'order[cardholderEmail]=support@centralpay.eu' \\\n--data-urlencode 'order[firstName]=John' \\\n--data-urlencode 'order[lastName]=Doe' \\\n--data-urlencode 'source=EC' \\\n--data-urlencode '3ds[xid]=35876533346561303461' \\\n--data-urlencode '3ds[eci]=02' \\\n--data-urlencode '3ds[status]=Y' \\\n--data-urlencode '3ds[threeDSServerTransID]=67dc456c-6c7a-987f-92cf-f68752525d0c'\n<\/code><\/pre>\n\n<pre class=\"wp-block-preformatted\">\u2139\ufe0f <strong>\u00ab best effort \u00bb case (3RI not completed).<\/strong> If the 3RI is not completed (<code>transStatus<\/code> other than <code>Y<\/code>\/<code>A<\/code>, and excluding <code>R<\/code>), perform the same transaction <strong>without the subject<\/strong> <code>3ds[...]<\/code> : the <code>Customer<\/code>  (<code>customerId<\/code>  +  <code>cardId<\/code>) is sufficient to link the operation to the initial CIT. In that case, the transfer of liability does not apply. <\/pre>\n\n<p class=\"wp-block-paragraph\"><strong>See also:<\/strong> <a href=\"https:\/\/docs.centralpay.com\/documentation\/documentation\/bonnes-pratiques\/merchant-initiated-transaction-mit\/\">Best Practices \u2014 Merchant-Initiated Transactions (MIT)<\/a> for the contractual framework, mandate, and Strong Customer Authentication (SCA) exemptions.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The 3RI (3DS Requestor Initiated) flow applies to merchant-initiated transactions (MIT): the merchant initiates the debit without the cardholder\u2019s involvement, under a pre-existing authorization, based on a previously authenticated CIT transaction. It covers all MIT scenarios: recurring billing, variable amounts, usage-based templates, one-time fees, and deferred debits (no-shows, penalties), not just fixed-rate subscriptions. \ud83d\udc49 If [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":16466,"menu_order":2,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"doc_badge":[],"class_list":["post-16477","docs","type-docs","status-publish","hentry","no-post-thumbnail"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Merchant-initiated transaction (MIT \u2013 3RI) - CentralPay Documentation<\/title>\n<meta name=\"description\" content=\"3-D Secure 2.2 3RI workflow for merchant-initiated transactions (MIT): recurring payments, variable amounts, one-time fees...\" \/>\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\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Merchant-initiated transaction (MIT \u2013 3RI) - CentralPay Documentation\" \/>\n<meta property=\"og:description\" content=\"3-D Secure 2.2 3RI workflow for merchant-initiated transactions (MIT): recurring payments, variable amounts, one-time fees...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/\" \/>\n<meta property=\"og:site_name\" content=\"CentralPay Documentation\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-20T15:09:08+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=\"7 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\\\/3ds-2-2-authentication\\\/merchant-initiated-transaction-mit-3ri\\\/\",\"url\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/3ds-2-2-authentication\\\/merchant-initiated-transaction-mit-3ri\\\/\",\"name\":\"Merchant-initiated transaction (MIT \u2013 3RI) - CentralPay Documentation\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/#website\"},\"datePublished\":\"2024-06-27T13:08:54+00:00\",\"dateModified\":\"2026-08-20T15:09:08+00:00\",\"description\":\"3-D Secure 2.2 3RI workflow for merchant-initiated transactions (MIT): recurring payments, variable amounts, one-time fees...\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/3ds-2-2-authentication\\\/merchant-initiated-transaction-mit-3ri\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/3ds-2-2-authentication\\\/merchant-initiated-transaction-mit-3ri\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/3ds-2-2-authentication\\\/merchant-initiated-transaction-mit-3ri\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"3DS 2.2 authentication\",\"item\":\"https:\\\/\\\/docs.centralpay.com\\\/en\\\/documentation\\\/3ds-2-2-authentication\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Merchant-initiated transaction (MIT \u2013 3RI)\"}]},{\"@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":"Merchant-initiated transaction (MIT \u2013 3RI) - CentralPay Documentation","description":"3-D Secure 2.2 3RI workflow for merchant-initiated transactions (MIT): recurring payments, variable amounts, one-time fees...","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\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/","og_locale":"en_US","og_type":"article","og_title":"Merchant-initiated transaction (MIT \u2013 3RI) - CentralPay Documentation","og_description":"3-D Secure 2.2 3RI workflow for merchant-initiated transactions (MIT): recurring payments, variable amounts, one-time fees...","og_url":"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/","og_site_name":"CentralPay Documentation","article_modified_time":"2026-08-20T15:09:08+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/","url":"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/","name":"Merchant-initiated transaction (MIT \u2013 3RI) - CentralPay Documentation","isPartOf":{"@id":"https:\/\/docs.centralpay.com\/en\/#website"},"datePublished":"2024-06-27T13:08:54+00:00","dateModified":"2026-08-20T15:09:08+00:00","description":"3-D Secure 2.2 3RI workflow for merchant-initiated transactions (MIT): recurring payments, variable amounts, one-time fees...","breadcrumb":{"@id":"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/merchant-initiated-transaction-mit-3ri\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/docs.centralpay.com\/en\/"},{"@type":"ListItem","position":2,"name":"3DS 2.2 authentication","item":"https:\/\/docs.centralpay.com\/en\/documentation\/3ds-2-2-authentication\/"},{"@type":"ListItem","position":3,"name":"Merchant-initiated transaction (MIT \u2013 3RI)"}]},{"@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\/16477","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=16477"}],"version-history":[{"count":2,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/docs\/16477\/revisions"}],"predecessor-version":[{"id":16479,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/docs\/16477\/revisions\/16479"}],"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=16477"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/doc_tag?post=16477"},{"taxonomy":"doc_badge","embeddable":true,"href":"https:\/\/docs.centralpay.com\/en\/wp-json\/wp\/v2\/doc_badge?post=16477"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}