diff --git a/docs/images/ilp-flow.png b/docs/images/ilp-flow.png
new file mode 100644
index 0000000..7226997
Binary files /dev/null and b/docs/images/ilp-flow.png differ
diff --git a/docs/markdown/ilp-flow.md b/docs/markdown/ilp-flow.md
new file mode 100644
index 0000000..d9f3d44
--- /dev/null
+++ b/docs/markdown/ilp-flow.md
@@ -0,0 +1,41 @@
+# Basic Interledger Payment Flow
+ 
+This section helps you become more familiar with Interledger by outlining the parts of an Interledger payment system and explaining the steps involved in an Interledger payment.
+ 
+## Interledger payment
+ 
+The Interledger payment system consists of four main components:
+- Sender - Initiates a value transfer.
+- Router - Applies currency exchange and forwards packets of value.
+- Receiver - Receives the value.
+- ILP Packet - A binary data packet, which contains necessary information required for an ILP payment. ILPv4 has three packet types: Prepare, Fulfill, and Reject, which roughly correspond to request, response, and error messages.
+
+In the following scenario, the sender sends a Prepare packet to the connecting router. The routers forward the packet until it reaches the receiver. The receiver then accepts or rejects the packet by sending a Fulfill packet or a Reject packet.
+ 
+ ![ILP-packets](../images/ilp-packets.png)
+
+## Interledger payment flow
+ 
+### Prerequisites
+
+To understand the Interledger payment flow, let's assume the following:
+1. The sender and receiver have accounts with at least one router on the Interledger network.
+2. The sender knows the receiver's payment pointer, which is required for exchanging necessary payment information.
+ 
+### Payment flow
+
+1. The sender initiates a payment by connecting with the receiver over an out-of-band authenticated channel and obtaining the receiver's ILP address and a secret hash condition.
+0. The sender constructs a Prepare packet with the destination ILP address, the secret hash condition, amount, and expiry.
+0. The sender sends the Prepare packet to the router it is connected to.
+0. The router checks the expiry of the Prepare packet. If the router receives the packet after the expiry, the router sends a Reject packet to the sender. If the router receives the packet before the expiry, the following steps take place.
+0. The router uses its local routing tables and the destination address from the Prepare packet to determine which next hop to forward the packet to. The next hop can be another router or the receiver.
+0. The router determines the outgoing asset type based on the next hop it will forward the packet to and applies its exchange rate and fees to the Prepare amount.
+0. The router forwards the Prepare packet to the next hop, which may be another router. All subsequent routers go through steps 4-6 (treating the previous router as the sender) until the packet reaches the receiver.
+0. The receiver receives the packet and checks the packet contents, for example, if the amount to be received is acceptable.
+0. If the receiver accepts the Prepare packet, the receiver returns a Fulfill packet. If the receiver does not want the Prepare packet or it does not pass one of the checks, the receiver returns a Reject packet instead.
+0. The router checks if the receiver returned a Fulfill before the expiry in the Prepare packet. If so, the router returns the same Fulfill packet to the previous router. If the receiver returned a Reject packet or the Prepare expired before the Fulfill was returned, the router returns the Reject packet to the preceding router. Each router repeats this step until the Fulfill or Reject packet reaches the sender.
+0. Sender repeats the process, starting from step 2, as many times as is necessary to transfer the desired total amount of value.
+
+The following diagram shows the sequence of events that occur during an Interledger payment:
+
+![ILP-flow](../images/ilp-flow.png)