Deactivate a checkout
Deactivates an identified checkout resource. If the checkout has already been processed it can not be deactivated.
- 200
- 401
- 404
- 409
OK
- application/json
- Schema
- Example (from schema)
- Deleted Checkout
Schema
- checkout_reference string
Possible values:
<= 90 characters
Unique ID of the payment checkout specified by the client application when creating the checkout resource.
- id string
Unique ID of the checkout resource.
- amount float
Amount of the payment.
- currency string
Possible values: [
BGN
,BRL
,CHF
,CLP
,CZK
,DKK
,EUR
,GBP
,HRK
,HUF
,NOK
,PLN
,RON
,SEK
,USD
]Three-letter ISO4217 code of the currency for the amount. Currently supported currency values are enumerated above.
- pay_to_email email
Email address of the registered user (merchant) to whom the payment is made. It is highly recommended to use
merchant_code
instead ofpay_to_email
. - merchant_code string
Unique identifying code of the merchant profile.
- description string
Short description of the checkout visible in the SumUp dashboard. The description can contribute to reporting, allowing easier identification of a checkout.
- purpose string
Possible values: [
SETUP_RECURRING_PAYMENT
,CHECKOUT
]Purpose of the checkout creation initially
- status string
Possible values: [
EXPIRED
]Current status of the checkout.
- date date-time
Date and time of the creation of the payment checkout. Response format expressed according to ISO8601 code.
- valid_until date-time
Date and time of the checkout expiration before which the client application needs to send a processing request. If no value is present, the checkout does not have an expiration time.
- merchant_name string
Merchant name
- transactions object[]
List of transactions related to the payment.
{
"checkout_reference": "string",
"id": "string",
"amount": 0,
"currency": "BGN",
"pay_to_email": "[email protected]",
"merchant_code": "string",
"description": "string",
"purpose": "SETUP_RECURRING_PAYMENT",
"status": "EXPIRED",
"date": "2023-05-24",
"valid_until": "2023-05-24",
"merchant_name": "string",
"transactions": [
{
"id": "string",
"transaction_code": "string",
"amount": 0,
"currency": "BGN",
"timestamp": "2023-05-24",
"status": "SUCCESSFUL",
"payment_type": "ECOM",
"installments_count": 0,
"merchant_code": "string",
"vat_amount": 0,
"tip_amount": 0,
"entry_mode": "CUSTOMER_ENTRY",
"auth_code": "string",
"internal_id": 0
}
]
}
{
"checkout_reference": "f00a8f74-b05d-4605-bd73-2a901bae5802",
"id": "817340ce-f1d9-4609-b90a-6152f8ee267j",
"amount": 2,
"currency": "EUR",
"pay_to_email": "[email protected]",
"merchant_code": "MH4H92C7",
"description": "Deletion example",
"purpose": "CHECKOUT",
"status": "EXPIRED",
"date": "2020-02-29T10:56:56+00:00",
"valid_until": "2020-02-29T10:56:56+00:00",
"merchant_name": "Sample Merchant",
"transactions": []
}
Unauthorized
- application/json
- Schema
- Example (from schema)
- Invalid_ Token
- Not_ Authorized_ Token
- Missing_ Token
Schema
- message string
Short description of the error.
- error_code string
Platform code for the error.
{
"message": "string",
"error_code": "string"
}
{
"error_message": "invalid access token",
"error_code": "NOT_AUTHORIZED"
}
{
"error_message": "NOT_AUTHORIZED",
"error_code": "NOT_AUTHORIZED"
}
{
"message": "access token required",
"error_code": "NOT_AUTHORIZED"
}
Not Found
- application/json
- Schema
- Example (from schema)
- Not_ Found
Schema
- message string
Short description of the error.
- error_code string
Platform code for the error.
{
"message": "string",
"error_code": "string"
}
{
"error_code": "NOT_FOUND",
"message": "Resource not found"
}
Conflict
- application/json
- Schema
- Example (from schema)
- Checkout_ Processed
Schema
- message string
Short description of the error.
- error_code string
Platform code for the error.
{
"message": "string",
"error_code": "string"
}
{
"error_code": "CHECKOUT_PROCESSED",
"message": "Checkout is already processed"
}