-
Notifications
You must be signed in to change notification settings - Fork 13
/
Copy pathSCT-instant.pml
62 lines (40 loc) · 1.59 KB
/
SCT-instant.pml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
@startuml
!includeurl https://raw.githubusercontent.com/w3c/webpayments-flows/gh-pages/PaymentFlows/skin.ipml
participant "Payee's Bank" as MPSP
Participant "Payee" as Payee
Actor "Payer" as Payer
participant "Payment App" as PSPUI
participant "Payer's Bank" as CPSP
note over Payee, PSPUI: HTTPS
title Payer Initiated SEPA Credit Transfer Instant
== Negotiation of Payment Terms & Selection of Payment Instrument ==
Payee<->Payer: Offer Negotiation
== Payment Initiation ==
Payee->PSPUI: PaymentRequest with CreditTransferRequest
PSPUI->CPSP: Submit Payment Initiation Request
note over PSPUI
API to receive credit transfer initiation including all data set from CreditTransferRequest
(e.g. PSD2 / OpenBanking API if Payment App from 3rd Party)
end note
PSPUI->CPSP: Authenticate
...
== Payment Processing ==
CPSP->MPSP: Transfer Funds
note over PSPUI
if payeePaymentIdentificationUserReadable and payeePaymentIdentificationMachineReadable
available in CreditTransferRequest then payeePaymentIdentificationMachineReadable should
be privileged into the SEPA Credit Transfer
end note
== Notification ==
CPSP-[#black]>Payer: [Optional] Payment Completion Status
MPSP->Payee: Payment Completion Status
Payee-[#black]>Payer: [Optional] Payment Completion Status
== Delivery of Product ==
Payee->Payer: Meet any service obligation established in Step 1
== Bank legacy Notification ==
CPSP->Payer: Statement or Credit transfer advice
note over PSPUI
both payeePaymentIdentificationUserReadable and payeePaymentIdentificationMachineReadable
could be provided in CAMT-053 and CAMT-054 formats
end note
@enduml