Prompt for the SubscriptionApp

Please create a React-JS application for the SubscriptionModule. The application  has to offer the following views for the user interface: 
    1. PaymentMethodView 
    2. SubscriptionView 
    3. SubscriptionPaymentView 
    4. SubscriptionPlanView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The PaymentMethodView must contain the following fields: 
    - name: FundingSource   type: FundingSource 
    - name: IsDefault   type: BOOL 
    - name: Label   type: STRING 
    - name: MethodType   type: STRING 
    - name: Priority   type: INT 
    - name: UserAccount   type: UserAccount 
The data source for the [FundingSource] select control should be loaded from the relative URL: 
    "/FundingSourceService/fundingsource"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing PaymentMethod entity should be loaded from the relative URL: 
    "/SubscriptionService/paymentmethod/{id}"   (HTTP-GET) 
If a new PaymentMethod entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionService/paymentmethod"   (HTTP-POST) 
If an existing PaymentMethod entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionService/paymentmethod/{id}"   (HTTP-PUT) 
If an existing PaymentMethod entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionService/paymentmethod/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Subscription columns: 
    - column: UserAccount 
    - column: CancelledAt 
    - column: EndDate 
    - column: StartDate 
    - column: Status 
    - column: PaymentMethod 
    - column: SubscriptionPlan 
The table should have the title "Subscriptions" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionService/subscription/paymentmethod/{id}"

2. The SubscriptionView must contain the following fields: 
    - name: CancelledAt   type: DATE 
    - name: EndDate   type: DATE 
    - name: PaymentMethod   type: PaymentMethod 
    - name: StartDate   type: DATE 
    - name: Status   type: STRING 
    - name: SubscriptionPlan   type: SubscriptionPlan 
    - name: UserAccount   type: UserAccount 
The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: 
    "/SubscriptionService/subscriptionplan"   (HTTP-GET) 
The data source for the [PaymentMethod] select control should be loaded from the relative URL: 
    "/SubscriptionService/paymentmethod"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Subscription entity should be loaded from the relative URL: 
    "/SubscriptionService/subscription/{id}"   (HTTP-GET) 
If a new Subscription entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionService/subscription"   (HTTP-POST) 
If an existing Subscription entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionService/subscription/{id}"   (HTTP-PUT) 
If an existing Subscription entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionService/subscription/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following SubscriptionPayment columns: 
    - column: Transaction 
    - column: Subscription 
    - column: ChargeDate 
    - column: Amount 
    - column: Status 
    - column: Currency 
The table should have the title "SubscriptionPayments" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionService/subscriptionpayment/subscription/{id}"

3. The SubscriptionPaymentView must contain the following fields: 
    - name: Amount   type: DOUBLE 
    - name: ChargeDate   type: DATE 
    - name: Currency   type: Currency 
    - name: Status   type: STRING 
    - name: Subscription   type: Subscription 
    - name: Transaction   type: Transaction 
The data source for the [Transaction] select control should be loaded from the relative URL: 
    "/TransactionService/transaction"   (HTTP-GET) 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [Subscription] select control should be loaded from the relative URL: 
    "/SubscriptionService/subscription"   (HTTP-GET) 
An existing SubscriptionPayment entity should be loaded from the relative URL: 
    "/SubscriptionService/subscriptionpayment/{id}"   (HTTP-GET) 
If a new SubscriptionPayment entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionService/subscriptionpayment"   (HTTP-POST) 
If an existing SubscriptionPayment entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionService/subscriptionpayment/{id}"   (HTTP-PUT) 
If an existing SubscriptionPayment entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionService/subscriptionpayment/{id}"   (HTTP-DELETE)

4. The SubscriptionPlanView must contain the following fields: 
    - name: Amount   type: DOUBLE 
    - name: BillingFrequency   type: INT 
    - name: BillingInterval   type: STRING 
    - name: Currency   type: Currency 
    - name: Description   type: STRING 
    - name: Merchant   type: Merchant 
    - name: Name   type: STRING 
    - name: Status   type: STRING 
    - name: TrialDays   type: INT 
The data source for the [Merchant] select control should be loaded from the relative URL: 
    "/MerchantService/merchant"   (HTTP-GET) 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
An existing SubscriptionPlan entity should be loaded from the relative URL: 
    "/SubscriptionService/subscriptionplan/{id}"   (HTTP-GET) 
If a new SubscriptionPlan entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionService/subscriptionplan"   (HTTP-POST) 
If an existing SubscriptionPlan entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionService/subscriptionplan/{id}"   (HTTP-PUT) 
If an existing SubscriptionPlan entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionService/subscriptionplan/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Subscription columns: 
    - column: UserAccount 
    - column: CancelledAt 
    - column: EndDate 
    - column: StartDate 
    - column: Status 
    - column: PaymentMethod 
    - column: SubscriptionPlan 
The table should have the title "Subscriptions" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionService/subscription/subscriptionplan/{id}"