Comment on page
A service that passes the control of the payment request to the merchant server.
A merchant must use this service:
- When there is a small quantity of the product in stock
- When payment is processed first-come-first-served
- When there is business logic that the merchant wants to execute just before making the payment request
If a merchant's product is a luxury or very popular item and there are concurrent requests competing to submit a payment, the merchant server can process the payment request after doing a final check on the inventory. If the confirm process is not configured, the purchased order may not ship as scheduled due to lack of inventory or may be cancelled leading to poor customer satisfaction and experience.
If a merchant uses a payment method that launches at a scheduled time, such as application for marathon, ticketing for popular concerts, and special discount events such as OO Day, there will be a rush of concurrent payment requests at the scheduled time. In such a case, the merchant needs to perform a final inventory check on the server just before making the payment request.
The service can also be used when the merchant needs to process some business logic just before payment for reasons, such as checking the health of the merchant server.
Checking your Merchant ID
To use Confirm Process, you must define the confirm_url parameter and set it to the merchant endpoint URL when calling the request_pay() function.
confirm_url : ‘Merchant EndPoint URL’,
If the confirm URL is set, the final confirm page before payment request is loaded via HTTP with the same webhook data in the HTTP body.
imp_uid: payment ID
merchant_uid: order ID
status: payment result
The payment request is processed when the merchant responds to the above request with HTTP Status 200.
Payment is not processed for a non-200 response. (