Refactored payment processing in storefront checkout
This content is archived and is not being updated. For the latest documentation, go to What's new or changed in Dynamics 365 Commerce. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
|Enabled for||Public preview||General availability|
|Users by admins, makers, or analysts||May 28, 2021||Jul 16, 2021|
This feature reduces the number of authorization requests to the payments processor, resulting in lower payment processing fees. It also adds better support for Strong Customer Authentication (SCA) in the European Union by combining the customer authentication by their bank with the authorization request for the amount due on the order.
In Europe, SCA requires that if a customer is paying for an online transaction using a card, the website must support redirecting the customer for authentication as the cardholder directly with their bank. If the customer can be authenticated by their bank prior to the authorization request, the transaction is considered more secure and the liability shifts away from the merchant. Today, that customer authentication is done when the card token is obtained. That card token is then used in a subsequent authorization request. From the merchant's standpoint, that subsequent authorization request does not have a liability shift because it was made using a card token, or card on file. This can cause confusion for merchants using the storefront.
When this feature is enabled, a single request will be made to obtain the card token and authorization. The request will also include SCA redirect. The result is that merchants will see one authorization request that includes the liability shift where SCA is applicable. For merchants subject to SCA requirements and those who are not, this feature will result in fewer authorization requests, which translates into lower processing fees.