๐จUrgent Support
We are experiencing
"responseBody":{"code":"FORBIDDEN_CONSECUTIVE_REQUEST","message":"๋ฐ๋ณต์ ์ธ ์์ฒญ์ ํ์ฉ๋์ง ์์ต๋๋ค. ์ ์ ํ ๋ค์ ์๋ํด์ฃผ์ธ์."},"responseCode":403
The two requests are not consecutive as we sent after a few hours. Does anyone know why this is happening?
We need to send this within an hour by the end of today KR time.
16 Replies
โณ ์ ์๋ง ๊ธฐ๋ค๋ ค์ฃผ์ธ์! ๊ณง ๋ต๋ณ๋๋ฆฌ๊ฒ ์ต๋๋ค
์ค๋ฅ ๋ฌธ์์ผ ๊ฒฝ์ฐ ์๋ ์ ๋ณด๋ฅผ ๋ฏธ๋ฆฌ ์ ๋ฌํด์ฃผ์๋ฉด, ๋น ๋ฅธ ๋ต๋ณ์ ๋์์ด ๋ฉ๋๋ค.
- ์ฃผ๋ฌธ๋ฒํธ(orderId) :
- ๋ฌธ์ ๋ด์ฉ :
(img๋ฅผ ํจ๊ป ์ฒจ๋ถํด์ฃผ์๋ฉด ๋์์ด๋ฉ๋๋ค)
* ๊ณ์ฝ๊ด๋ จ ๋ด์ฉ์ 1544-7772๋ก ๋ฌธ์์ฃผ์ธ์.
* ์ฃผ๋ง/๊ณตํด์ผ์๋ ๋ต๋ณ์ด ๋ฆ์ ์ ์์ด์.
TP01020241212110849jgzb5
You are sending two consecutive requests when sending a cancellation. It may take some time to process, so try sending them one by one
Actually, if you check the cancellation request that came to us, it looks like this
Dec 12, 2024 @ 16:25:33.279859000
{"cancelReason":"Refund for payment TP01020241212110849jgzb5","cancelAmount":19624,"currency":"KRW","taxFreeAmount":19624}
Dec 12, 2024 @ 16:25:33.281296049
{"cancelReason":"Refund for payment TP01020241212110849jgzb5","cancelAmount":19624,"currency":"KRW","taxFreeAmount":19624}
If sending them one by one doesn't work, adjust the partial cancellation amount. For example, to KRW 1,000.
Then our team will check again.
Thank you! We have also sent on a few hours later and seems it has 403 error. Would you mind having a look?
The next request was also requested in two.
Dec 12, 2024 @ 21:36:52.085570000
{"cancelReason":"Refund for payment TP01020241212110849jgzb5","cancelAmount":19624,"currency":"KRW","taxFreeAmount":19624}
Dec 12, 2024 @ 21:36:52.087078967
{"cancelReason":"Refund for payment TP01020241212110849jgzb5","cancelAmount":19624,"currency":"KRW","taxFreeAmount":19624}
Send just one and let me know again
Try this
{"cancelReason":"Refund for payment TP01020241212110849jgzb5","cancelAmount":1000,"currency":"KRW","taxFreeAmount":1000}
Thank you, let me try one more time.
Sorry, I have to get off work now
I'll continue tomorrow, so leave the test log or results here.
Thank you so much! Will do.
Thank you!
Also, when you request the API, send Accept-Language header as en-US
it makes the response body is translated to english so you can understand the exception more easily
โค๏ธ ๊ธฐ์ ๋ฌธ์ ๊ฒฝํ์ด ์ด๋ ์
จ๋์?!
๊ฐ๋จํ ์ฝ๋ฉํธ ๋จ๊ฒจ์ฃผ์ธ์! ์ ํ ๋ฐ์ ์ ํฐ ํ์ด ๋ฉ๋๋ค.
Thanks all. We retried again last night but still got 403 error. I will check if we are sending it twice or not. However, this wonders me. Can we not just process the first request? I understand second request may have 403 but the first one should be process.
The API request is a heavy transaction because it calls the card company API using VAN, processes the payment(pay it or cancel it), and changes the DB.... So if 2 consecutive requests come in, both transactions might be rejected to avoid potential problems.
Understood, thanks
Thanks. Just think about it - If the confirm API or cancel API is called twice, without rejecting both,
and database is not locked yet(still requesting the card companys' API). It will pay twice or cancel twice - causes the huge problem as it directly links the cash flow.
I see, understood. I am normally not in the payment world so good to know.