Prompt for the PaymentAccountApp

Please create a React-JS application for the PaymentAccountModule. The application  has to offer the following views for the user interface: 
    1. PaymentAccountView 
    2. PaymentTransactionView 
    3. SessionStateView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The PaymentAccountView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: CurrencyCode   type: STRING 
    - name: IsEnabled   type: BOOL 
    - name: KycStatus   type: STRING 
    - name: UpdatedAt   type: DATE 
    - name: UserAccount   type: UserAccount 
    - name: WalletAddress   type: STRING 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing PaymentAccount entity should be loaded from the relative URL: 
    "/PaymentAccountService/paymentaccount/{id}"   (HTTP-GET) 
If a new PaymentAccount entity has been created, the new entity should be posted to the relative URL: 
    "/PaymentAccountService/paymentaccount"   (HTTP-POST) 
If an existing PaymentAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/PaymentAccountService/paymentaccount/{id}"   (HTTP-PUT) 
If an existing PaymentAccount entity has to be deleted, the following relative URL should be called: 
    "/PaymentAccountService/paymentaccount/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following PaymentTransaction columns: 
    - column: CreatedAt 
    - column: PaymentAccountFrom 
    - column: TransactionHash 
    - column: PaymentAccountTo 
    - column: Conversation 
    - column: AmountMinorUnits 
    - column: CompletedAt 
    - column: CurrencyCode 
    - column: Status 
The table should have the title "PaymentTransactions" und the data must be loaded from the server with the following relative URL: 
    "/PaymentAccountService/paymenttransaction/paymentaccountfrom/{id}" 
Add a HTML table to the view with the following PaymentTransaction columns: 
    - column: CreatedAt 
    - column: PaymentAccountFrom 
    - column: TransactionHash 
    - column: PaymentAccountTo 
    - column: Conversation 
    - column: AmountMinorUnits 
    - column: CompletedAt 
    - column: CurrencyCode 
    - column: Status 
The table should have the title "PaymentTransactions" und the data must be loaded from the server with the following relative URL: 
    "/PaymentAccountService/paymenttransaction/paymentaccountto/{id}"

2. The PaymentTransactionView must contain the following fields: 
    - name: AmountMinorUnits   type: LONG 
    - name: CompletedAt   type: DATE 
    - name: Conversation   type: Conversation 
    - name: CreatedAt   type: DATE 
    - name: CurrencyCode   type: STRING 
    - name: PaymentAccountFrom   type: PaymentAccount 
    - name: PaymentAccountTo   type: PaymentAccount 
    - name: Status   type: STRING 
    - name: TransactionHash   type: STRING 
The data source for the [PaymentAccountFrom] select control should be loaded from the relative URL: 
    "/PaymentAccountService/paymentaccount"   (HTTP-GET) 
The data source for the [PaymentAccountTo] select control should be loaded from the relative URL: 
    "/PaymentAccountService/paymentaccount"   (HTTP-GET) 
The data source for the [Conversation] select control should be loaded from the relative URL: 
    "/ConversationService/conversation"   (HTTP-GET) 
An existing PaymentTransaction entity should be loaded from the relative URL: 
    "/PaymentAccountService/paymenttransaction/{id}"   (HTTP-GET) 
If a new PaymentTransaction entity has been created, the new entity should be posted to the relative URL: 
    "/PaymentAccountService/paymenttransaction"   (HTTP-POST) 
If an existing PaymentTransaction entity has been updated, the modified entity should be sent to the relative URL: 
    "/PaymentAccountService/paymenttransaction/{id}"   (HTTP-PUT) 
If an existing PaymentTransaction entity has to be deleted, the following relative URL should be called: 
    "/PaymentAccountService/paymenttransaction/{id}"   (HTTP-DELETE)

3. The SessionStateView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: LocalDevice   type: LONG 
    - name: RemoteDevice   type: LONG 
    - name: RemoteUserAccount   type: LONG 
    - name: SerializedState   type: STRING 
    - name: SessionIdentifier   type: STRING 
    - name: UpdatedAt   type: DATE 
An existing SessionState entity should be loaded from the relative URL: 
    "/PaymentAccountService/sessionstate/{id}"   (HTTP-GET) 
If a new SessionState entity has been created, the new entity should be posted to the relative URL: 
    "/PaymentAccountService/sessionstate"   (HTTP-POST) 
If an existing SessionState entity has been updated, the modified entity should be sent to the relative URL: 
    "/PaymentAccountService/sessionstate/{id}"   (HTTP-PUT) 
If an existing SessionState entity has to be deleted, the following relative URL should be called: 
    "/PaymentAccountService/sessionstate/{id}"   (HTTP-DELETE)