Salesforce Disabling TLS 1.0

Salesforce will be disabling TLS 1.0 in production organizations in the near future (they are already disabled in sandboxes). More information can be found here. This change has a direct effect on Payment Center because Payment Center does call-outs to the payment processors we support.

Call-outs are integrations where Salesforce refers to an outside source to either verify login credentials, push data, or pull data. Examples of call-outs include: Delegated Authentication Single-Sign-On (SSO), Outbound Messaging, and Apex call-outs. If you use call-out integrations, please ensure that TLS 1.1 and/or TLS 1.2 are enabled in those integrations.

The good news is we tested our integrations and they all support TLS 1.1 and above.

Processor	URL	Supports TLS 1.1 and Above?
PayPal Payments Pro	https://api-3t.paypal.com/nvp	Yes
PayPal Payflow Pro	https://payflowpro.paypal.com	Yes
Authorize.Net	https://secure2.authorize.net/gateway/transact.dll	Yes
Authorize.Net	https://api2.authorize.net/xml/v1/request.api	Yes
CyberSource	https://ics2ws.ic3.com/commerce/1.x/transactionProcessor	Yes
Stripe	https://api.stripe.com/v1/charges	Yes
Recurly	https://api.recurly.com/v2/transactions	Yes
PayLeap	https://secure1.payleap.com/TransactServices.svc/ProcessCreditCard	Yes

So with the above we do not expect disruptions in Payment Center when Salesforce disables TLS 1.0.