Oliveyoung Payment System Improvement Story Part - 1
Key point
To resolve payment mismatch issues, Oliveyoung improved its payment process by switching from the existing asynchronous (Async) method to a synchronous (Sync) method that separates authentication and approval.
Details
Oliveyoung had previously used a structure in which approval processing after payment authentication was handled asynchronously (Async). With this method, if a communication error occurred while payment results were being delivered to the backend, a payment mismatch phenomenon occurred where the payment was completed but the order failed.
In particular, during the Olyoung Sale period when large-scale traffic surged, the limitations of this asynchronous method caused payment data inconsistency issues, affecting user experience and sales. To resolve this, Oliveyoung switched its payment method to the Sync method.
The new method has a structure that separates authentication and approval, with the following characteristics.
- When the payment provider delivers the authentication result, Oliveyoung immediately performs synchronous communication to request final approval
- By breaking down information at each payment stage, precise monitoring is possible through Datadog
- Instead of complex transaction management, a sequential processing structure was adopted, improving code intuitiveness
Through these improvements, during the Olyoung Sale in March 2022, despite tremendous traffic, Oliveyoung recorded zero payment mismatch cases, securing service stability.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.