action openbankingproject_initiate_payment {
  label: "Payment initiation request"
  description: "This method is used to initiate a payment at the ASPSP.\n\n## Variants of payment initiation requests\n\nThis method to initiate a payment initiation at the ASPSP can be sent with either a JSON body or an pain.001 body depending on the payment product in the path.\n\nThere are the following **payment products**:\n\n  - Payment products with payment information in *JSON* format:\n    - ***domestic-swiss-credit-transfers-isr***\n    - ***domestic-swiss-credit-transfers***\n    - ***domestic-swiss-credit-transfers-qr***\n    - ***domestic-swiss-foreign-credit-transfers***\n    - ***swiss-sepa-credit-transfers***\n    - ***swiss-cross-border-credit-transfers***\n  - Payment products with payment information in *SIX pain.001* XML format:\n    - ***pain.001-sepa-credit-transfers***\n    - ***pain.001-cross-border-credit-transfers***\n    - ***pain.001-swiss-six-credit-transfers***\n\nFurthermore the request body depends on the **payment-service**:\n  * ***payments***: A single payment initiation request.\n  * ***bulk-payments***: A collection of several payment initiation requests.\n  \n    In case of a *pain.001* message there are more than one payments contained in the *pain.001 message.\n\n    In case of a *JSON* there are several JSON payment blocks contained in a joining list.\n  * ***periodic-payments***:\n    Create a standing order initiation resource for recurrent i.e. periodic payments addressable under {paymentId}\n     with all data relevant for the corresponding payment product and the execution of the standing order contained in a JSON body.\n\nThis is the first step in the API to initiate the related recurring/periodic payment.\n\n## Single and mulitilevel SCA Processes\n\nThe payment initiation requests are independent from the need of one or multilevel \nSCA processing, i.e. independent from the number of authorisations needed for the execution of payments. \n\nBut the response messages are specific to either one SCA processing or multilevel SCA processing. \n\nFor payment initiation with multilevel SCA, this specification requires an explicit start of the authorisation, \ni.e. links directly associated with SCA processing like 'scaRedirect' or 'scaOAuth' cannot be contained in the \nresponse message of a Payment Initation Request for a payment, where multiple authorisations are needed. \nAlso if any data is needed for the next action, like selecting an SCA method is not supported in the response, \nsince all starts of the multiple authorisations are fully equal. \nIn these cases, first an authorisation sub-resource has to be generated following the 'startAuthorisation' link.\n"
  provider: openbankingproject
  method: POST
  path: "/v1/{payment-service}/{payment-product}"
  encoding: json
  output: {
    type: "object"
    additionalProperties: true
  }
}