# Low code checkout pages

> Learn about our low code checkout solution which could reduce your integration workload.

Checkout Pages is a low code checkout solution(also known as Payment links) offered by Continental Payment for customers who do not want to build their checkout and deal with complexities of data collection which can vary from one payment method to another.

With the help of Checkout solution, our customers can simply send a single API request to [Create a checkout](https://continental-payment.typemark.dev/payments/post-rest-checkouts) endpoint to generate a payment link such as: [https://testapi.continentalpay.com/rest/checkouts/f04359f5-0609-46eb-9c90-9c3d18787294](https://testapi.continentalpay.com/rest/checkouts/f04359f5-0609-46eb-9c90-9c3d18787294).

Once generated, end payer should be redirected to the given link where they can finalize the transaction.

## Integration steps

1. Send an API request to [Create a checkout](https://continental-payment.typemark.dev/payments/post-rest-checkouts) API endpoint. See API reference for full list of parameters you can pass to the endpoint.
2. If you have provided **success\_url**, **error\_url** or **webhook\_url**, the end payer will be redirected to your provided URLs, or, if not given, to our own return urls.

**We strongly suggest to provide the webhook\_url in order to receive notifications about transactions happening on this checkout**.

## Listening to transaction notifications on created checkout

Once the checkout is created, save the **checkout\_id** in your systems, so when receiving notifications to your given **webhook\_url**, you can match the transaction ID inside the webhook notification to a given checkout.

For instance, let's consider a case where you have created a checkout and received a response:

```Text json
{
  "checkout_id": "f04359f5-0609-46eb-9c90-9c3d18787294",
  "error_code": 0,
  "status": "open",
  "client_action": "redirect",
  "action_data": {
    "url": "http://testapi.continentalpay.com/rest/checkouts/f04359f5-0609-46eb-9c90-9c3d18787294"
  }
}

```

You should save the returned **checkout\_id** so that when you receive a notification such as:

```Text json
{
  "transaction_id": "5e02903b-0fbf-4266-affd-dc58f2749cd1",
  "checkout_id": "f04359f5-0609-46eb-9c90-9c3d18787294"
  "order_id": "123000",
  "status_code": 1,
  "status": "completed"
}
```

With this, now you can match in your systems that your created checkout with ID **f04359f5-0609-46eb-9c90-9c3d18787294** has a completed transaction with ID **5e02903b-0fbf-4266-affd-dc58f2749cd1**.

**We strongly suggest to only provide services when you have a completed transaction belonging to the checkout**.

Some payment methods are asynchronous, and may take a few minutes/hours/days to reach completed status, such as SEPA Direct Debit, Boleto, PIX. In this case, you may receive multiple webhook notifications for each status change. A fully cleared transaction will always have completed status while anything else is either a pending or a faulty state.

**We strongly suggest to also double check / poll the transaction's status using our[Get a payment](https://continental-payment.typemark.dev/continental-payment-v-2/get-v2-payouts-id) API, where you can fetch information about a transaction**.

## Ability to prefill information

Checkout solution also supports prefilling of the input fields in the checkout, if you already have access to the data. This may reduce the friction that your customer may face in the checkout flow.

Read more about the parameter options passable to our checkout API in our [API Reference](https://docs.c-payment.de/reference)
