...
6.1 Staging a Service Initiation Consent
6.1.1 Single Instant Payment
To manage the creation and execution of a Single Instant payment;
...
MUST provide a
ConsentId
in the Consent object within theauthorization_details
of a Rich Authorization Request.MAY use
PATCH
to manage any Webhook configurations for the entire duration of a payment consentMAY use a
GET
to the/payments/{PaymentId}
resource to poll for Payment Statuses.
...
MUST reject the Service Initiation consent if a globally unique UUID v4
ConsentId
does not exist in the RAR object.MUST validate the Consent parameters and create a Consent resource (
ConsentId
) that isAwaitingAuthorization
when a valid RAR object is staged at the PAR endpoint.MUST immediately stage the payment with the LFI once a valid Service Initiation resource is created by the TPP.
MUST send payment status events to the TPP if an active Webhook Subscription is registered within the Consent object.
The LFI:
MUST immediately stage the payment with the Payment Rails once a valid payment is staged by the OFP.
MUST emit payment status events to the OFP.
6.1.2 Single Future Dated, Multi-Payment
For Single Future Dated and Multi-Payment Consents:
The TPP:
MUST provide an
ConsentId
in the Consent object within theauthorization_details
of a Rich Authorization Request.MAY use
PATCH
to manage any Webhook configurations for the entire duration of a payment consent
...
MUST validate the Consent parameters and create a Consent resource (
ConsentId
) that isAwaitingAuthorization
when a valid RAR object is staged at the PAR endpoint.MUST immediately stage the payment with the LFI once a valid Service Initiation resource is created by the TPP.
MUST send payment status events to the TPP if an active Webhook Subscription is registered within the Consent object.
...