Corda transactions

After the Buyer has decided what they would like to buy, they need to initiate a Propose Corda Transaction. The Corda transactions are shown as a set of duplicated actions in the swim lane of each participant involved in the Corda transaction, with the Corda logo in the corner.

The actions are joined with a two way dashed line. In BPMN dashed lines denote messages and are normally unidirectional. However, in the CorDapp BPMN a two way arrow is used to reflect that there is a series of back and forth messages which result in a finalised transaction on the ledger.

The party that initiated the transaction is marked, and the message line is annotated on the Initiator end with a blue box giving more details about how the transaction was formed. This is typically what Flow is invoked and what the Command in the transaction should be.

In this example you can see that the Buyer will initiate the ProposeFlow to create a Propose transaction.

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.