Skip to main content
For delivery method, firewall settings, and logs, see Webhook Events.

Event Types

Cash receipt issuance and cancellation are asynchronous. The API sends the final result in one of the following events.

Payload

Issuance Success

Issuance Failure

Cancellation Success

Cancellation Failure

The following codes are returned only with CASH_RECEIPT_CANCEL_FAILED.
  • ORIGINAL_ISSUANCE_FAILED: Bolta accepted the cancellation request while the original issuance was in progress, but the original issuance later failed
  • CANCELLATION_TARGET_NOT_FOUND: The cancellation target could not be found, was already canceled, or already had a cancellation request

Canceled Outside Bolta

Bolta sends this event when an issued cash receipt is canceled outside Bolta (for example, on Hometax).

Webhook Delivery Time

Delivery timing depends on the key and processing result. For live keys, Bolta starts result-webhook delivery after the final status changes. A test key (test_) records the final status after the request is processed. The automatic webhook is sent no sooner than 10 seconds after the API accepts the request. You can receive the same event more than once. Process webhooks idempotently with eventType and issuanceKey. The final status transition and HTTP receipt do not necessarily occur at the same time.
202 Accepted only means Bolta accepted the request. Treat a cash receipt as unconfirmed until the status API returns ISSUED or you receive CASH_RECEIPT_ISSUED.

When a Webhook Does Not Arrive

Check with Retrieve Cash Receipt Status. PENDING means the API accepted the request and has not started processing it. REQUEST_SUCCESS only means request delivery completed; it does not confirm the final result. For a live request that remains in progress or awaits issuance-result confirmation, check again after 17:00 KST on the following day.