Important Notice

Disabling TLS 1.0 for MY2C2P SDK

In 20 June 2017, 2C2P Instances will disable TLS 1.0 and will begin using TLS 1.2 only. This change is slated to occur on the following schedule:

• Sandbox Instances : 25 May, 2017, at 00:00 UTC

• Production Instances : 20 June, 2017, at 00:00 UTC

Impacted :

1. This change will affect existing users of applications built on v3.0.6 and older of MY2C2P SDK. To avoid loss of functionality in your applications, please upgrade your existing applications with MY2C2P SDK version v3.1.0 and above as soon as possible.

2. This change will impact payment request that using Redirect Payment on affected Android version. Refer : Payment Channel

3. After TLS 1.0 is disabled on a 2C2P instance, applications that are not compliant with TLS 1.2 will not be able to connect to that 2C2P instances.

Android Versions Affected :

1. Jelly Bean 4.3 (API 18) or older :-

   • These platforms do not support TLS 1.2 and therefore are no longer supported for Redirect Payment & 3DS payment request.
   • Existing applications that target these platforms will stop working when TLS 1.0 is disabled.
   • MY2C2P SDK version v3.1.0 and above still continue support for these platform, if you're using Credit Card payment with Non-3DS payment request only.

2. Kitkat 4.4 (API 19) or later :-

   • These platforms releases use TLS 1.2 by default. Existing applications that target these platforms will continue to work without changes. But we encourage upgrade the MY2C2P SDK to v3.1.0 and above.

Note :

Please upgrade to v3.1.0 and above of MY2C2P SDK, and release a new version of your applications before the Production Instances deadline shown above.

Next :: Import SDK