List payment instruments in e-commerce integration
These release notes describe functionality that may not have been released yet. To see when this functionality is planned to release, please review What’s new and planned for Dynamics 365 for Retail. Delivery timelines and projected functionality may change or may not ship (see Microsoft policy).
It is common in e-commerce scenarios to support a customer’s ability to save a payment instrument for subsequent transactions and to later use that payment instrument when creating orders. This feature adds the ability for the merchant to include customer context in authorization requests that can be used to map that customer to payment instruments previously used with the same payment processor.
The payment experience for e-commerce scenarios in Dynamics 365 for Retail or Finance and Operations is driven by the "Payment Accept Page" (which is a URL to an external payment flow) or "Payment Accept Content" (which is HTML content for an external payment flow). The URL or HTML content is generated by the payment gateway/processor on the fly based on a new payment session and set of parameters that are sent to the payment connector.
When this feature is turned on within Retail Shared Parameters, authenticated customers who are creating an order in an e-commerce storefront will be given the option to save their card for the next visit. When a customer opts to save a card during the checkout process, that card will be presented as a payment option the next time the customer visits that web storefront. Customers must opt in to save cards. Customers using guest checkout will not be able to save cards.
With this feature turned on, the customer context is passed to the payment gateway along with the request for the card payments page. If the processor has the ability to return saved customer cards, and is able to map the customer to previously saved payments, those payments will be selectable as part of checkout.