Smart Payments 3DS Full Execution
Smart Payments 3DS Full Execution Overview
Forter's Smart 3DS/PSD2 full execution integration allows merchants to maximize transactions authorized by their PSP (Payment Service Provider) and minimize the friction for legitimate customers by providing recommendations for the application of 3DS while balancing risk, regulation, and customer experience needs.
The Smart Payments 3DS/PSD2 Execution Integration requires the integration of the following APIs and touch points:
- Adaptive Auth Transaction API (Pre-Auth) - The Adaptive Auth Transaction API should be called at the time of checkout and item purchase prior to authorization by the Payment Provider. Forter will provide a real-time approve/decline decision and/or execute a challenge for the customer.
- 3DS Challenge Verification API - API is used for checking the challenge results after the challenge journey was completed on the merchant site (following a callback that the merchant receives directly from the ACS about completion). The API request body only requires the order id and challenge token which was recieved in the callback from the ACS.
- Adaptive Auth Transaction API (Post-Auth) - The Adaptive Auth Transaction API may also be called after the 3DS challenge verify and authorization by the Payment Provider for an updated real-time approve/decline decision by Forter
- Order Status API - The API used to provide Forter with updates on the fulfillment status. If no post-auth Adaptive Auth Transaction API call is made, the Order Status API should also include the authorization Status and 3DS/PSD2 data for the order. Forter does NOT return an approve/decline decision for the Order Status API. Instead it is used to provide Forter's models with updated information about the order and the customer entity.
Updated 13 days ago