API Documentation
All API
Service
Cancellation of ChargeSync
Version: v1
Version: v1
/api/v1/recharges/by-bank-accounts/no-hce/cancel
Request Headers
Request Parameters
Response Headers
X-KM-Correlation-Id
string
Required
Length : 20
Transaction number for tracking trasncription
- Form : yyMMddHHmiSS-xxxxxxx
- xxxxxxx : 7digit, Hex String
X-KM-Crypto-Key-Id
string
Optional
Length : 32
Data encryption/decryption key ID
- Given ID from creating the service provider's project
- If it is passed as a callback, the first key issued among the keys issued to the service provider is used.
Response Parameters
isPending
boolean
Required
Waiting for charging transaction
(Cancellation of charge) If a normal response is not received from the PG due to network instability, etc. during the transaction, the value is returned as "true".
Such transaction may take some time depending on the network conditions of the bank or PG, and the PG continuously checks success of withdrawal transfer.
If it succeeds, the card charge cancellation transaction is completed, and if it fails, it is processed as a charge cancellation failure.
On the day of the request, charge cancellation transaction will be checked continuously every 5 minutes.
Response Code
Detailed classification and addition of error for unseccessful withfrawal
200
Error code
000_000
Message
Success.
Description
Success
400
Error code
000_002
Message
Invalid input parameter. userId
Description
Invalid input parameter
400
Error code
007_001
Message
Bank account not found.
Description
No account registered
400
Error code
007_030
Message
Cancellation not possible for this transaction.
Description
์ถฉ์ ์ทจ์๊ฐ ๋ถ๊ฐ๋ฅํ ๊ฑฐ๋.
400
Error code
007_040
Message
Cancel request for another method.
Description
์ถฉ์ ์ทจ์ํ ์ถฉ์ ๊ฑด์ ์ถฉ์ ๊ธ์ก ์ง๋ถ ๋ฐฉ์์ด ๋ค๋ฅธ ๊ฒฝ์ฐ.
400
Error code
007_043
Message
Cancellation request denied due to name mismatch.
Description
์์คํ ์ ๋ฑ๋ก๋ ํ์ ์ด๋ฆ๊ณผ ์ํ๊ณ์ข ์์ ์๋ช ์ด ๋ค๋ฅธ ์ํ์์ ์ทจ์ ์์ฒญ์ด ๋ค์ด์จ ๊ฒฝ์ฐ ๋ฐ์ํ ์๋ฌ.
Test Data
Request
Response
Click Try It!
to start a Request and see the Response here!