Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update figure39.plantuml to fix multiple typos in Refund example flow #135

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions fspiop-api/documents/Generic-Transaction-Patterns.md
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,7 @@ A Party is an entity such as an individual, a business, an organization that has

#### 3.1.2 Interledger

The API includes basic support for the Interledger Protocol (ILP) by defining a concrete implementation of the Interledger Payment Request protocol<sup>[1](https://interledger.org/rfcs/0011-interledger-payment-request)</sup>(ILP) in the logical API resources **Quotes** and **Transfers**. More details of the ILP protocol can be found on the Interledger project website<sup>[2](https://interledger.org)</sup>, in the Interledger Whitepaper<sup>[3](https://interledger.org/interledger.pdf)</sup>, and in the Interledger architecture specification<sup>[4](https://interledger.org/rfcs/0001-interledger-architecture)</sup>.
The API includes basic support for the Interledger Protocol (ILP) by defining a concrete implementation of the Interledger Payment Request protocol<sup>[1](https://interledger.org)</sup>(ILP) in the logical API resources **Quotes** and **Transfers**. More details of the ILP protocol can be found on the Interledger project website<sup>[2](https://interledger.org)</sup>, in the Interledger Whitepaper<sup>[3](https://interledger.org/interledger.pdf)</sup>, and in the Interledger architecture specification<sup>[4](https://interledger.org/)</sup>.

### 3.2 API Resource Participants

Expand Down Expand Up @@ -553,7 +553,7 @@ The intermediary objects used in a _Payer-Initiated Transaction_ to perform the

Figure 1 shows the UML sequence diagram for a _Payer-Initiated Transaction_.

{% uml src="assets/diagrams/sequence/figure64a.plantuml" %}
{% uml src="assets/diagrams/sequence/figure65a.plantuml" %}
{% enduml %}
**Figure 1 -- Payer-Initiated Transaction**

Expand Down Expand Up @@ -1793,10 +1793,10 @@ This section provides descriptions of and assumptions made for all steps in the

## 5. References

<sup>1</sup> [https://interledger.org/rfcs/0011-interledger-payment-request/ - Interledger Payment Request (IPR)](https://interledger.org/rfcs/0011-interledger-payment-request)
<sup>1</sup> Interledger Payment Request (IPR) (Link obsolete, article moved elsewhere)

<sup>2</sup> [https://interledger.org/ - Interledger](https://interledger.org)

<sup>3</sup> [https://interledger.org/interledger.pdf - A Protocol for Interledger Payments](https://interledger.org/interledger.pdf)

<sup>4</sup> [https://interledger.org/rfcs/0001-interledger-architecture/ - Interledger Architecture](https://interledger.org/rfcs/0001-interledger-architecture)
<sup>4</sup> Interledger Architecture (Link obsolete, article moved elsewhere)
Original file line number Diff line number Diff line change
Expand Up @@ -128,10 +128,10 @@ Switch <<-- PayeeFSP: **HTTP 202**\n(Accepted)
PayeeFSP -> PayeeFSP:Find original transaction, 1 USD\nwas received in FSP commission, \ngive back in FSP commission.\nReverse Agent commission.
PayeeFSP ->> Payee:Customer wants a refund of Cash-in,\nyou will lose 1 USD in commission\nand 100 USD will be transfered to\nyour account, please pay customer\n101 USD in cash
PayeeFSP <<- Payee: OK
Switch <<- PayeeFSP: **PUT /quote/**<i><ID></i>\n(transferAmount=99 USD,\npayeeFspCommission=1 USD)
Switch <<- PayeeFSP: **PUT /quotes/**<i><ID></i>\n(transferAmount=99 USD,\npayeeFspCommission=1 USD)
Switch -->> PayeeFSP: **HTTP 200** (OK)
deactivate PayeeFSP
PayerFSP <<- Switch: **PUT /quote/**<i><ID></i>\n(transferAmount=99 USD,\npayeeFspCommission=1 USD)
PayerFSP <<- Switch: **PUT /quotes/**<i><ID></i>\n(transferAmount=99 USD,\npayeeFspCommission=1 USD)
PayerFSP -->> Switch: **HTTP 200** (OK)
deactivate Switch
PayerFSP -> PayerFSP: Payer gets fee subsizidized by\nFSP commission.
Expand All @@ -144,16 +144,16 @@ PayerFSP ->> Switch: **POST /transfers**\n(amount=99 USD)
activate Switch
PayerFSP <<-- Switch: **HTTP 202** (Accepted)
Switch -> Switch: Reserve 99 USD from Payer FSP\naccount to Payee FSP account
Switch ->> PayeeFSP: **POST /transfer/**<i><ID></i>
Switch ->> PayeeFSP: **POST /transfers/**<i><ID></i>
activate PayeeFSP
Switch <<-- PayeeFSP: **HTTP 202** (Accepted)
PayeeFSP -> PayeeFSP: Reverse original transaction by\ntransferring 100 USD to Payee\naccount, 99 USD from Switch\naccount, 1 USD from fee account,\nand 1 USD from fee account to\ninternal commission account
PayeeFSP -> Payee: You have received 100 USD\nfrom Payer in Cash-in refund,\nplease pay customer his 101 USD
Switch <<- PayeeFSP: **POST /transfer/**<i><ID></i>
Switch <<- PayeeFSP: **PUT /transfers/**<i><ID></i>
Switch -->> PayeeFSP: **HTTP 200** (OK)
deactivate PayeeFSP
Switch -> Switch: Commit reserved transfer
PayerFSP <<- Switch: **POST /transfer/**<i><ID></i>
PayerFSP <<- Switch: **PUT /transfers/**<i><ID></i>
PayerFSP -->> Switch: **HTTP 200** (OK)
deactivate Switch
PayerFSP -> PayerFSP: Commit reserved transfer
Expand Down
Loading