# SEPA_SCHEDULED_TRANSACTION

A standing order was either executed or declined. Use this webhook to stay informed about the progression of standing orders and to connect each step in the process with its corresponding booking (or absence thereof).

Endpoint: POST sepa_scheduled_transaction
Version: 1.0

## Request fields (application/json):

  - `id` (string)
    The ID of the relevant standing order.
    Example: "c14ed45ced80f17a1ecc62214db2738ccsto"

  - `account_id` (string)
    The account ID associated with the standing order.
    Example: "008cad63f317721e582ba99eefff219fcacc"

  - `processed_at` (string)
    UTC timestamp from when the transaction was processed.
    Example: "2017-10-21T00:50:00.438Z"

  - `reference` (string)
    Optional reference for the transaction. Will act as an idempotency key.
    Example: "Reference-56eb879fae8faa2f6d14f87161cst"

  - `source` (string)
    Transaction source.
    Example: "standing_order"

  - `source_id` (string)
    ID of the transaction's source.
    Example: "c14ed45ced80f17a1ecc62214db2738ccsto"

  - `status` (string)
    Status of the standing order.
    Example: "EXECUTED"

  - `decline_reason` (array)
    An array containing the reasons why the standing order was declined.

  - `transaction_id` (string)
    ID of the transaction.
    Example: "49a57d88276df2e440cdd2e7eec291ctrx"