Expire checkout
Checkouts
Expire checkout
POST
Expire checkout
Expires a checkout that should no longer be used.
- A successful response returns the checkout in its current state together with
expiredAt. - When the expiration is applied, the checkout status will be
EXPIRED. - After expiry, the customer can no longer make new payment attempts on that checkout.
- If the checkout does not exist, the endpoint returns
NOT_FOUND.
Authorizations
See Authentication.
Path Parameters
The id of the checkout that you are performing this operation on.
Required string length:
36Response
Request has been processed by PawaPay.
The unique ID for this payment in PawaPay as specified by you during initiation.
Required string length:
36Example:
"f4401bd2-1568-4140-bf2d-eb77d2b2b639"
Possible checkout lifecycle statuses. This is distinct from the initiation status (CheckoutCreationStatus) returned when the checkout is created.
WAITING_PAYMENT- The checkout and its hosted payment page have been created and are waiting for the customer to pay.PROCESSING- A payment attempt is in progress and the checkout is still being processed.COMPLETED- The checkout has completed successfully. This is a final status.FAILED- The checkout has failed. InspectdepositordepositsHistoryfor the latest attempt result when available. This is a final status.EXPIRED- The checkout has expired and can no longer be used. This is a final status.CANCELLED- The customer cancelled the payment on the hosted payment page. This is a final status.
Available options:
WAITING_PAYMENT, PROCESSING, COMPLETED, FAILED, EXPIRED, CANCELLED Timestamp when the checkout was expired.
Example:
"2026-03-27T10:45:00Z"
Reason reported for the expiration.
Example:
"MANUAL_EXPIRY"
Actor that expired the checkout.
Example:
"API"