Overview

Initiating a Checkout session sends a webhook notification to the merchant that includes the checkoutId. The initial status is created.

📘
See the webhooks section for descriptions of the checkout statuses.

Get the status of a checkout request using the checkoutId or the merchantTransactionId.

🚧

Using the merchantTransactionId returns the latest Checkout associated with that value. If you are not maintaining unique merchantTransactionId values, multiple associations between this parameter and Checkout sessions could exist.

Use unique merchantTransactionId values for each checkout request that you execute.

Flow

To learn more about the required and optional parameters, see the API reference section.

The Checkout status flow works as follows:

The merchant queries the checkout status by making a request to the Status endpoint.
The Checkout API responds with the status of the checkout. If the merchant used merchantTransactionId and is not using unique transaction IDs, the Checkout API returns the latest Checkout associated with the merchantTransactionId.

📘
All GET status requests require a signature using the secret token as the key and the API signs all responses with a signature using the secret token as the key.

curl -G https://testsecure.peachpayments.com/status \
   -d authentication.entityId=8ac7a4ca86c2c24d0168c2caab2e0025 \
   -d merchantTransactionId=Test1234\
   -d signature=79b450ed255e306332f6325c99732cc84fca8cc2cf3fdc2bfd1f3e2465f55

Example requests and responses

For sample requests and responses, see the interactive API playground or use the Peach Payments Postman collection: