Cardholder authentication
Duoza supports 3-D Secure (3DS) for online cardholder authentication, including Direct Pay API integrations. The issuer assesses the authentication request and may ask the cardholder to complete an additional step.
Authentication sits within the payment journey alongside authorization and the final payment outcome.
Design for a smooth customer experience
Keep the customer informed when authentication is required and allow the authentication journey to complete. Handle completion, failure, and abandonment using your channel’s integration guidance.
Provide a clear route back to the order and avoid treating an unfinished authentication step as a completed payment.
Follow your channel’s authentication flow
Your Duoza integration manager provides the supported 3DS version, initiation flow, customer-interface requirements, and outcome handling in the full integration reference.
Test the applicable authentication journeys together with successful, declined, and interrupted payment attempts before launch.
Keep authentication and payment outcomes distinct
Successful authentication is not payment authorization or settlement. Use the final payment outcome to update the order and the settlement records to reconcile merchant funds.
Applicable scheme and acquiring rules govern dispute and liability treatment. Include the relevant operating guidance in your support procedures.