Prompt for the UserApp

Please create a React-JS application for the UserModule. The application  has to offer the following views for the user interface: 
    1. PaymentView 
    2. PaymentMethodView 
    3. UserView 
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 PaymentView must contain the following fields: 
    - name: Amount   type: STRING 
    - name: Currency   type: STRING 
    - name: Description   type: STRING 
    - name: PaidAt   type: STRING 
    - name: PaymentMethod   type: PaymentMethod 
    - name: Status   type: STRING 
    - name: Subscription   type: Subscription 
    - name: User   type: User 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
The data source for the [PaymentMethod] select control should be loaded from the relative URL: 
    "/UserService/paymentmethod"   (HTTP-GET) 
The data source for the [Subscription] select control should be loaded from the relative URL: 
    "/SeasonService/subscription"   (HTTP-GET) 
An existing Payment entity should be loaded from the relative URL: 
    "/UserService/payment/{id}"   (HTTP-GET) 
If a new Payment entity has been created, the new entity should be posted to the relative URL: 
    "/UserService/payment"   (HTTP-POST) 
If an existing Payment entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserService/payment/{id}"   (HTTP-PUT) 
If an existing Payment entity has to be deleted, the following relative URL should be called: 
    "/UserService/payment/{id}"   (HTTP-DELETE)

2. The PaymentMethodView must contain the following fields: 
    - name: BillingCountry   type: Country 
    - name: CreatedAt   type: STRING 
    - name: ExpiryMonth   type: LONG 
    - name: ExpiryYear   type: LONG 
    - name: IsDefault   type: BOOL 
    - name: LastFour   type: STRING 
    - name: Provider   type: STRING 
    - name: Type   type: STRING 
    - name: User   type: User 
The data source for the [BillingCountry] select control should be loaded from the relative URL: 
    "/TitleService/country"   (HTTP-GET) 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
An existing PaymentMethod entity should be loaded from the relative URL: 
    "/UserService/paymentmethod/{id}"   (HTTP-GET) 
If a new PaymentMethod entity has been created, the new entity should be posted to the relative URL: 
    "/UserService/paymentmethod"   (HTTP-POST) 
If an existing PaymentMethod entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserService/paymentmethod/{id}"   (HTTP-PUT) 
If an existing PaymentMethod entity has to be deleted, the following relative URL should be called: 
    "/UserService/paymentmethod/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Payment columns: 
    - column: Status 
    - column: Amount 
    - column: PaidAt 
    - column: Currency 
    - column: User 
    - column: Subscription 
    - column: Description 
    - column: PaymentMethod 
The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: 
    "/UserService/payment/paymentmethod/{id}"

3. The UserView must contain the following fields: 
    - name: Country   type: Country 
    - name: CreatedAt   type: STRING 
    - name: DisplayName   type: STRING 
    - name: Email   type: STRING 
    - name: PasswordHash   type: STRING 
    - name: Status   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/TitleService/country"   (HTTP-GET) 
An existing User entity should be loaded from the relative URL: 
    "/UserService/user/{id}"   (HTTP-GET) 
If a new User entity has been created, the new entity should be posted to the relative URL: 
    "/UserService/user"   (HTTP-POST) 
If an existing User entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserService/user/{id}"   (HTTP-PUT) 
If an existing User entity has to be deleted, the following relative URL should be called: 
    "/UserService/user/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following PaymentMethod columns: 
    - column: User 
    - column: ExpiryMonth 
    - column: IsDefault 
    - column: Provider 
    - column: BillingCountry 
    - column: ExpiryYear 
    - column: LastFour 
    - column: Type 
    - column: CreatedAt 
The table should have the title "PaymentMethods" und the data must be loaded from the server with the following relative URL: 
    "/UserService/paymentmethod/user/{id}" 
Add a HTML table to the view with the following Device columns: 
    - column: OsName 
    - column: AppVersion 
    - column: LastActiveAt 
    - column: DeviceType 
    - column: OsVersion 
    - column: Model 
    - column: User 
    - column: Manufacturer 
    - column: RegisteredAt 
The table should have the title "Devices" und the data must be loaded from the server with the following relative URL: 
    "/EpisodeService/device/user/{id}" 
Add a HTML table to the view with the following ChannelSubscription columns: 
    - column: StartDate 
    - column: Channel 
    - column: User 
    - column: EndDate 
    - column: AutoRenew 
    - column: Status 
The table should have the title "ChannelSubscriptions" und the data must be loaded from the server with the following relative URL: 
    "/DrmSchemeService/channelsubscription/user/{id}" 
Add a HTML table to the view with the following Profile columns: 
    - column: Name 
    - column: IsKidsProfile 
    - column: User 
    - column: AvatarUrl 
    - column: CreatedAt 
The table should have the title "Profiles" und the data must be loaded from the server with the following relative URL: 
    "/ProfileService/profile/user/{id}" 
Add a HTML table to the view with the following Subscription columns: 
    - column: EndDate 
    - column: StartDate 
    - column: AutoRenew 
    - column: User 
    - column: Status 
    - column: SubscriptionPlan 
The table should have the title "Subscriptions" und the data must be loaded from the server with the following relative URL: 
    "/SeasonService/subscription/user/{id}" 
Add a HTML table to the view with the following Payment columns: 
    - column: Status 
    - column: Amount 
    - column: PaidAt 
    - column: Currency 
    - column: User 
    - column: Subscription 
    - column: Description 
    - column: PaymentMethod 
The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: 
    "/UserService/payment/user/{id}"