Retrieve a checkout
Retrieves an identified checkout resource. Use this request after processing a checkout to confirm its status and inform the end user respectively.
- 200
- 401
- 404
OK
- application/json
- Schema
- Example (from schema)
Schema
- checkout_reference string
Possible values:
<= 90 characters
Unique ID of the payment checkout specified by the client application when creating 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.
- 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.
- return_url uri
URL to which the SumUp platform sends the processing status of the payment checkout.
- id string
Unique ID of the checkout resource.
- status string
Possible values: [
PENDING
,FAILED
,PAID
]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.
- customer_id string
Unique identification of a customer. If specified, the checkout session and payment instrument are associated with the referrenced customer.
mandate object
Created mandate
type stringIndicates the mandate type
status stringMandate status
merchant_code stringMerchant code which has the mandate
transactions object[]
List of transactions related to the payment.
id stringUnique ID of the transaction.
transaction_code stringTransaction code returned by the acquirer/processing entity after processing the transaction.
amount floatTotal amount of the transaction.
currency stringPossible 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.
timestamp date-timeDate and time of the creation of the transaction. Response format expressed according to ISO8601 code.
status stringPossible values: [
SUCCESSFUL
,CANCELLED
,FAILED
,PENDING
]Current status of the transaction.
payment_type stringPossible values: [
ECOM
,RECURRING
]Payment type used for the transaction.
installments_count integerPossible values:
>= 1
Current number of the installment for deferred payments.
merchant_code stringUnique code of the registered merchant to whom the payment is made.
vat_amount floatAmount of the applicable VAT (out of the total transaction amount).
tip_amount floatAmount of the tip (out of the total transaction amount).
entry_mode stringPossible values: [
CUSTOMER_ENTRY
]Entry mode of the payment details.
auth_code stringAuthorization code for the transaction sent by the payment card issuer or bank. Applicable only to card payments.
internal_id integerInternal unique ID of the transaction on the SumUp platform.
- transaction_code string
Transaction code of the successful transaction with which the payment for the checkout is completed.
- transaction_id string
Transaction ID of the successful transaction with which the payment for the checkout is completed.
- merchant_name string
Name of the merchant
- redirect_url string
Refers to a url where the end user is redirected once the payment processing completes.
payment_instrument object
Object containing token information for the specified payment instrument
token stringToken value
{
"checkout_reference": "string",
"amount": 0,
"currency": "BGN",
"pay_to_email": "[email protected]",
"merchant_code": "string",
"description": "string",
"return_url": "string",
"id": "string",
"status": "PENDING",
"date": "2023-06-02",
"valid_until": "2023-06-02",
"customer_id": "string",
"mandate": {
"type": "string",
"status": "string",
"merchant_code": "string"
},
"transactions": [
{
"id": "string",
"transaction_code": "string",
"amount": 0,
"currency": "BGN",
"timestamp": "2023-06-02",
"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
}
],
"transaction_code": "string",
"transaction_id": "string",
"merchant_name": "string",
"redirect_url": "string",
"payment_instrument": {
"token": "string"
}
}
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"
}