|
|
| (15 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| 2.1.1 “paymentInitiationRequest”
| |
|
| |
|
| This API creates a payment resource with all data relevant for the corresponding payment product; each
| |
| payment product is managed by a dedicated endpoint. PSD2-Orchestrator publishes the payment-product
| |
| endpoint if at least one ASPSP support it.
| |
|
| |
|
| '''Input parameters'''
| | *[[4.1.1 "paymentInitiationRequest" interface]] |
| | *[[4.1.2 "getPaymentStatusRequest" interface]] |
| | *[[4.1.3 "updatePaymentResource" interface]] |
| | *[[4.1.4 "getPaymentRequest" interface]] |
| | |
| | ---- |
|
| |
|
| {|class="wikitable"
| | <div class="prevpage"> |
| ! style="text-align:left;width:30%" | Attribute
| | [[4. Payments flow|<< 4. Payments flow]] |
| ! style="text-align:left;" | Description
| | </div><div class="nextpage"> |
| |-
| | [[4.1.1 "paymentInitiationRequest" interface|4.1.1 "paymentInitiationRequest" interface >>]] |
| |'''psu-id'''
| | </div> |
| |The ID of the PSU in the ASPSP client interface. Mandatory if “psu-corporate-id” is valorized
| |
| |-
| |
| |'''psu-id-type'''
| |
| |Type of the PSU-ID, needed in scenarios where PSUs have several PSU-IDs as access possibility.
| |
| |-
| |
| |'''psu-corporate-id''' | |
| |Identification of a Corporate, only used in a corporate context.
| |
| |-
| |
| |'''consent-id'''
| |
| |This data element may be contained, if the payment initiation transaction is part of a session, i.e. combined AIS/PIS service. This then contains the “consentId” of the related AIS consent, which was performed prior to this payment initiation.
| |
| |-
| |
| |'''tpp-redirect-preferred'''
| |
| |Only “true” or “false” values are accepted.
| |
| If it equals “true”, the TPP prefers a redirect over an embedded SCA approach.
| |
| If it equals “false”, the TPP prefers not to be redirected for SCA.
| |
| The ASPSP will then choose between the Embedded or the Decoupled SCA approach, depending on the choice of the SCA procedure by the TPP/PSU.
| |
| If the parameter is not used, the ASPSP will choose the SCA approach to be applied depending on the SCA method chosen by the TPP/PSU.
| |
| |-
| |
