Return-Path: Delivered-To: admin@ggclinknetworks.com Received: from nuna.solusitotal.com by nuna.solusitotal.com with LMTP id hTlhAl4b5Wd8NDkA3iUGDQ (envelope-from ) for ; Thu, 27 Mar 2025 16:33:18 +0700 Return-path: Envelope-to: admin@ggclinknetworks.com Delivery-date: Thu, 27 Mar 2025 16:33:18 +0700 Received: from rs236.mailgun.us ([209.61.151.236]:46109) by nuna.solusitotal.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1txjbw-00FjFH-OO for admin@ggclinknetworks.com; Thu, 27 Mar 2025 16:33:17 +0700 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=marketing.midtrans.com; q=dns/txt; s=pic; t=1743067930; x=1743075130; h=Content-Transfer-Encoding: Content-Type: Message-Id: To: To: From: From: Subject: Subject: Mime-Version: Date: Sender: Sender; bh=qu4xs2SddwE1AWFXLxVQy5e1Si+J7hREmDJMwqJVOpI=; b=MzN3nKC9B7VBD+q/AEZLlSsi5Ng/6+YCV96wsWSMQhCz+Ck4g8yXZCRRxisiKsbI0j6o7E58BoFA+XV3vzvI2NKTVCgmx7gm4HdkLjXjoAZ2xJos3okcXIO6limyf79uruW+Q08HMKifM9PevCaNM90LIhG560YHqK764UA6kzQ= X-Mailgun-Sending-Ip: 209.61.151.236 X-Mailgun-Sending-Ip-Pool-Name: X-Mailgun-Sending-Ip-Pool: X-Mailgun-Sid: WyJiMTQ1NyIsImFkbWluQGdnY2xpbmtuZXR3b3Jrcy5jb20iLCI2MzZlMmEiXQ== Received: by 46a365323a10 with HTTP id 67e51b1ab745373e7c6943b0; Thu, 27 Mar 2025 09:32:10 GMT Sender: hello@marketing.midtrans.com Date: Thu, 27 Mar 2025 09:32:10 +0000 Mime-Version: 1.0 Subject: =?UTF-8?q?=F0=9F=94=94Important:_Update_Your_Allowlist_for_3DS_Secure_Pay?= =?UTF-8?q?ments!?= From: Midtrans To: admin@ggclinknetworks.com X-Mailgun-Variables: {"client_id":"campaign-manager","tracking_id":"f47b7c5d-4b3c-4977-8e45-af791be12196"} X-Mailgun-Variables: {"campaign_id": "6196d4c5-404b-4f89-836c-9ab8d5d6cb37", "campaign_name": "ID_2025_MIDTRANS_INFO_0006_PRD_3DSRedirectDomainChange", "persona": "MERCHANT", "user_id": "513881990"} X-Mailgun-Template-Name: midtrans_3ds_redirect_domain_change Message-Id: <20250327093210.52718358f3b55ebd@marketing.midtrans.com> Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=1.1 X-Spam-Score: 11 X-Spam-Bar: + X-Ham-Report: Spam detection software, running on the system "nuna.solusitotal.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root\@localhost for details. Content preview: Hi Merchant Midtrans, We are writing to inform you of an upcoming improvement to our 3DS (3D Secure) payment flow. As part of ongoing enhancements to ensure secure and seamless transactions, we will gradually migrate the 3 [...] Content analysis details: (1.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: midtrans.com] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 RCVD_IN_VALIDITY_RPBL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. [209.61.151.236 listed in bl.score.senderscore.com] 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts 0.0 HTML_MESSAGE BODY: HTML included in message 1.1 KAM_REALLYHUGEIMGSRC RAW: Spam with image tags with ridiculously huge http urls -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.0 RCVD_IN_VALIDITY_SAFE_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. [209.61.151.236 listed in sa-accredit.habeas.com] 0.0 T_REMOTE_IMAGE Message contains an external image X-Spam-Flag: NO =20 =20 =20 =20 =20
=20 =20 =20 =20
=20
=20
=20 =20 =20
=20
=20 3D"" =20
=20
=20
=20
=20
=20 =20 =20 =20
=20
=20
=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20
=20

Hi Merchant Midtrans,

=20
=20

We are writing to inform you of an upcoming improvement t= o our 3DS (3D Secure) payment flow. As part of ongoing enhancements to ensu= re secure and seamless transactions, we will gradually migrate the 3DS r= edirect domain from https://api= =2Emidtrans.com to https://car= d.midtrans.com.

=20
=20

Key Details:

=20
=20
=20
=20

If your system employs domain allowl= isting, ensure that the new domain is added to your allowlist before Apr= il 24, 2025 to prevent disruptions. Failure to update the allowlist (if= applicable) may result in transaction failures where customers cannot comp= lete 3DS authentication and leading to declined payments.

=20
=20

Specifically, check all parts of you= r system that interact with 3DS Redirect URL, including:

<= /div> =20
=20
  • Web integrations: When performing = a 3DS URL Redirect or embedding the URL in an iframe.
  • Mobile apps: When handling the 3DS Webview.
=20
=20

=20 =20 =20
=20

What's Changed?

=20
=20

The API paths will remain unchanged,= only 3DS Redirect domain will be updated. Below are the revised URL= s for reference:

=20
=20
=20 =20 =20 =20
=20
=20

3DS Flow Overview:

=
=20
=20
  1. Redirect URL: Returned in the char= ge response, which (on Frontend side) you will have to redirect your custom= er to open 3DS URL, for them to complete 3DS process.
  2. Callback URL: Automatically triggered after the Redire= ct URL is opened (to gather browser information data).
  3. Result Completion URL: Automatically triggered or disp= layed after the customer completes the 3DS authentication, whether by submi= tting an OTP or allowing the transaction (including frictionless flows and = in-app 3DS authentication).
=20
=20

For full details on the 3DS flow, re= fer to our documentation.

=20
=20

=20 =20 =20
=20

Frequently Asked Questions (FAQ)

=20
=20

= Q1: When will this change take effect?

A: The migration will begin on April 24, 20= 25 and be fully completed by End of June 2025. We will notify you of any ti= meline adjustments.

 

Q2= : Do merchants need to change their integration to use the new domain?<= /span>

A: No, merc= hants should continue using the existing domain for Charge, Create Token, e= tc. This change only affects 3DS URL (which is used to redirect customers t= o the 3DS web page, on the Frontend side). No action is required unless you= use domain allowlisting. If so, add ht= tps://card.midtrans.com to your allowlist.

 

Q3: Will this affect existing transactions?

A: No. The AP= I paths remain identical, and the change will not disrupt current implement= ations.

 

Q4: Is there a= deadline to update our allowlist?

A: Yes. Ensure the new domain is allowed before= April 24, 2025 to avoid service interruptions.

 

Q5: Why is the Result Completion Page UR= L unchanged?

A: Only 3DS Redirect and Callback URLs are migra= ting. The Result Completion URL will remain on api.midtrans.com. However, i= n the future, we will also migrate this to https://card.midtrans.com for 3D= S URL consistency. This change will be announced separately and will take p= lace after the migration of the 3DS Redirect and Callback URLs.

<= /div> =20
=20

For any questions, feel free to reach out to our support = team at support@midtrans.com or visi= t our Help Center.

Thank you for your cooperation i= n ensuring a smooth transition.

=20
=20

Best regards,

Midtrans

=
=20
=20 =20 =20 =20 =20
=20 =20 =20
=20 =20 =20
=20 =20 =20
=20 =20
=20

Midtrans, Pasaraya= Blok M, B Building, 4th Floor 

Jl. Iskandarsyah II No. 2 Melawai, Kebayoran Baru, Ja= karta Selatan, 

Jakarta 12160, Indonesia

=20
=20
=20
=20
=20 =20 =20 =20
=20 3D"" =20