# Timed Orders

A timed order is a type of [SEPA Credit Transfer (SCT)](/guides/digital-banking/sepa-transfers/sepa-credit-transfer) that allows customers
to schedule and authorize a one-off transaction to be executed automatically at
specific date.

See the [overview](/guides/digital-banking/sepa-transfers/) page to
learn more about SEPA and the different types of SEPA payment schemes.

## How does it work?

A timed order works exactly like a standard SEPA Credit Transfer (SCT). Offer a
frontend for your customer to log in and set up a timed order, which triggers
the [change request](/guides/authentication/strong-customer-authentication#change-request)
process. The customer must authorize the transaction either via an SMS OTP or a
device signing challenge.

The process looks like this:

1. The customer logs in to their account to create a timed order. They must
provide the necessary transaction details, such as the amount, recipient
IBAN, and execution date.
2. The customer authorizes the transaction using two-factor authentication (2FA)
via an SMS OTP or a device signing challenge.
3. Before executing the timed order, Solaris checks the account's
`available_balance` to ensure that there are sufficient funds.
4. Solaris executes the timed order, which creates a booking on the
customer's account with the booking type `SEPA_CREDIT_TRANSFER`.


- Timed orders have the same transaction type and booking type as a standard
SCT, which is `SEPA_CREDIT_TRANSFER`.
- In case a timed order fails due to insufficient funds, no booking will be
placed on the account. Instead, the status of the transaction will be set to
`declined`.


### Execution rules

- Timed orders execute according to the same rules as regular SEPA Credit
Transfers, i.e., every banking day on every hour between 07:00 - 20:00.
- If an execution date falls on a bank holiday or a weekend, the beneficiary
will receive the transfer on the next banking day.


## Prerequisites

You must implement the following features in order to use timed orders in
your solution:

- [Device binding](/guides/authentication/device-binding/)
- [Strong Customer Authentication](/guides/authentication/strong-customer-authentication/)
- [SEPA Credit Transfers](/guides/digital-banking/sepa-transfers/sepa-credit-transfer)


## Related webhooks

- [SEPA_TIMED_ORDER](/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/sepa_timed_order/post): A timed order was executed.


## API reference documentation

To implement timed orders, integrate the following endpoints in your solution:

- [POST Create a timed order](/api-reference/digital-banking/sepa-transfers/#tag/(Legacy)-Timed-orders/paths/~1v1~1persons~1%7Bperson_id%7D~1accounts~1%7Baccount_id%7D~1timed_orders/post)
- [GET Retrieve a timed order](/api-reference/digital-banking/sepa-transfers/#tag/(Legacy)-Timed-orders/paths/~1v1~1persons~1%7Bperson_id%7D~1accounts~1%7Baccount_id%7D~1timed_orders/get)
- [GET Retrieve all timed orders](/api-reference/digital-banking/sepa-transfers/#tag/(Legacy)-Timed-orders/paths/~1v1~1persons~1%7Bperson_id%7D~1accounts~1%7Baccount_id%7D~1timed_orders~1%7Bid%7D/get)
- [PATCH Cancel a timed order](/api-reference/digital-banking/sepa-transfers/#tag/(Legacy)-Timed-orders/paths/~1v1~1persons~1%7Bperson_id%7D~1accounts~1%7Baccount_id%7D~1timed_orders~1%7Bid%7D~1cancel/patch)