Simplify 3DS implementation in payment orchestration

The ask

Users find it challenging to implement complex payment flows, especially 3DS, with existing payment orchestration platforms. Current solutions require extensive manual configuration and custom code for each gateway's 3DS requirements. They often need to contact individual gateways for specific details, create merchant profiles, and write significant JavaScript to manage various 3DS flows. This process is time-consuming and prone to errors. A simpler approach is desired. The user wants a system where they can send a single request from their backend, receive a URL, and redirect the customer to a hosted, PCI compliant page. This page should then handle all card input, 3DS challenges, purchase blocking based on the issuing bank, and automatic retry attempts across multiple payment gateways until a successful capture. Such a solution would significantly reduce development effort and operational overhead associated with managing diverse payment gateway integrations and compliance requirements.

Flamas collected this from a public request on Ask HN, on Nov 5, 2026. Read the original. Nobody has been emailed about it, and the count above is only the people who have said they want it here.