Electronic Money and Payment System (IMONEEZ): Design & Implementation

3. Design & Implementation

The design of imoneez is described below. Therms:

Peer
Recipient
Coin
Cheque

Imoneez consists of three sides, really of five sides and three layers. Layered design is shown on figure 1. Let see at the figure and will understand what happense on the first (server) layer. The communication process is based on MIME messages exchanging. The complete detailed format of messages are in the attachment. So let's look at the usuall situation, when the peer wants to make payment, and must do request to server first. This request called TRANSFER-request and must be the following format


Request-Type: TRANSFER          ; Request type field
Currency-Name: RU               ; Currency Code field 
Cache-Value: 32.1200            ; Value to be transferred
Content-Type: Multipart/Mixed   ; Specifies that there are the attachments in the message
<CLCR>
<CLCR>
attachments
.
.
.

Brief description of reductions in figure.

TR - TRANSFER Request
CQr,CQs - recipient's and sender's cheques
GR - GET request
CNr,CNs - recipient's and sender's coins
TH - Transaction Hash as a guarantee of transaction for possible disagreements

3.1 Client side transaction composition

Client side transaction composition is similar to email composition, really it is the email composition itself, but with additional fields included (see fig.2). In the example we used mozilla mail agent as a transaction source, but with some header fields preferences added. So, the sender to make the transaction must define additional fields in message, Invoice-Type, Invoice-Value and Invoice-Currency. Optional fields are From-Address, From-Name, From-Phones, To-Address, To-Name, To-Phones, which may be usefull for organizations.

Next Previous Contents