Piano has prepared and updated the following functionality to be compliant with the SCA restrictions for clients using Braintree as their payment provider. More information about this topic is available here.
Checkout
For subscriptions, fixed-time access and gift purchases, users whose bank requires a 3DS authentication of the payment will be shown an additional screen during checkout after they enter their credit card payment details and confirm the purchase. Here the user will be prompted to enter an authorization code, token or follow the instructions on how to verify the payment in the bank’s mobile application.
The layout of this screen is defined by the individual bank, but you can edit certain parts via the template 3d Bank secure components.
Please note, that the template changes outlined here and here are required for 3DS checkout to function properly. In addition, you will need to switch your integration version of Braintree selected in Piano’s Edit Business settings to: V3. Supports 3DS 2.0 (Version 3).
Trials/Promotions
In case of trials and promo codes we will be initiating the transaction with the whole amount (of the full subscription price), receiving 3DS authorization for the whole amount, and then settling the actual lower amount by making a partial capture.
End users are informed about this through the following copy shown in checkout:
"While you will only be charged {0} for your promotional period, your bank now requires 3D Secure Authentication for all internet payments. That is why we need your authorization to charge the full price for future renewals."
Renewals
For the flow of failed subscription renewals due to 3DS issues please see the following link.
Manual renewals
In order to support 3DS authorizations for manual renewals via Braintree, you need to update the My Account Wallet Components template.
Find: <script type="text/ng-template" id="/widget/myaccount/partials/wallet/wallet_bank_secure.shtml">
And replace it with the following:
<script type="text/ng-template" id="/widget/myaccount/partials/wallet/wallet_bank_secure.shtml">
<div ng-click="close()" class="tp-close">x</div>
<div class="modal-content modal-content-bank-secure-modal">
<div id="secure-container-wrapper" class="secure-container-wrapper">
<div id="secure-container" class="secure-container">
</div>
</div>
</div>
</script>
My Account
When adding a new credit card via My Account, users will be prompted to authenticate the card by confirming it via the 3DS flow in the additional screen shown after adding the payment method via the My Account’s Library or Wallet tab. Please note, that the template updates described here and here are required for this functionality to work.
Piano dashboard
Subscribe user
Utilizing the flow under Manage > All Users > Subscribe user, you are able to subscribe a user to any payment term available in your application. As an additional step, we’ve now introduced a 3DS confirmation screen after confirming the subscription purchase on the user’s behalf, where you would need to enter a code or token provided by the user in order for the subscription to be billed.
Action Manager
The Action manager flow is not compatible with a 3DS authentication step and we don’t recommend using this functionality, as users with unauthenticated payment methods will potentially face issues for their auto-renewals of subscriptions with updated prices.
Upgrades
The impact of 3DS on the upgrade flow is described here.
Please note, that while enrolling in 3D Secure does allow for more flexibility to accept Maestro cards, you can't use recurring billing with Maestro cards when enrolled in 3D Secure.
For clients using Stripe, we have compiled a list of updates to templates here in order to support 3DS during checkout.
Any clients that are not using Braintree should consider updating the Email Manager template Subscription renewal failure (more information available here) with additional guidance for 3DS, i.e. explain what it is why a payment failure may occur. And then link clients back to a landing page or checkout where users can complete a new purchase incl. the necessary 3DS authentication if required. Potentially you should also consider adding additional instructions and a FAQ page available to your users about this topic and how to mitigate any 3DS impact on their subscription access.