Prompt for the PlatformUserApp

Please create a React-JS application for the PlatformUserModule. The application  has to offer the following views for the user interface: 
    1. PaymentMethodView 
    2. PlatformUserView 
    3. RiderAccountView 
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 PaymentMethodView must contain the following fields: 
    - name: BillingCountry   type: STRING 
    - name: BillingZip   type: STRING 
    - name: ExpiryMonth   type: INT 
    - name: ExpiryYear   type: INT 
    - name: MaskedAccountNumber   type: STRING 
    - name: MethodType   type: STRING 
    - name: PlatformUser   type: PlatformUser 
    - name: Provider   type: STRING 
    - name: Status   type: STRING 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing PaymentMethod entity should be loaded from the relative URL: 
    "/PlatformUserService/paymentmethod/{id}"   (HTTP-GET) 
If a new PaymentMethod entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/paymentmethod"   (HTTP-POST) 
If an existing PaymentMethod entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/paymentmethod/{id}"   (HTTP-PUT) 
If an existing PaymentMethod entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/paymentmethod/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following TripPayment columns: 
    - column: Amount 
    - column: RefundAmount 
    - column: RefundCurrency 
    - column: Currency 
    - column: CapturedAt 
    - column: Trip 
    - column: PaymentMethod 
The table should have the title "TripPayments" und the data must be loaded from the server with the following relative URL: 
    "/VehicleService/trippayment/paymentmethod/{id}"

2. The PlatformUserView must contain the following fields: 
    - name: CreatedAt   type: STRING 
    - name: Email   type: STRING 
    - name: ExternalUserKey   type: STRING 
    - name: PhoneNumber   type: STRING 
    - name: Status   type: STRING 
    - name: UserType   type: STRING 
An existing PlatformUser entity should be loaded from the relative URL: 
    "/PlatformUserService/platformuser/{id}"   (HTTP-GET) 
If a new PlatformUser entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-POST) 
If an existing PlatformUser entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/platformuser/{id}"   (HTTP-PUT) 
If an existing PlatformUser entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/platformuser/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following RiderAccount columns: 
    - column: DefaultPaymentMethod 
    - column: Notes 
    - column: PlatformUser 
    - column: Rating 
The table should have the title "RiderAccounts" und the data must be loaded from the server with the following relative URL: 
    "/PlatformUserService/rideraccount/platformuser/{id}" 
Add a HTML table to the view with the following PaymentMethod columns: 
    - column: ExpiryMonth 
    - column: Status 
    - column: ExpiryYear 
    - column: MethodType 
    - column: BillingZip 
    - column: Provider 
    - column: MaskedAccountNumber 
    - column: BillingCountry 
    - column: PlatformUser 
The table should have the title "PaymentMethods" und the data must be loaded from the server with the following relative URL: 
    "/PlatformUserService/paymentmethod/platformuser/{id}" 
Add a HTML table to the view with the following DriverAccount columns: 
    - column: LicenseCountry 
    - column: LicenseNumber 
    - column: DeactivationDate 
    - column: VehicleRegistrationCountry 
    - column: PlatformUser 
    - column: OnboardingDate 
    - column: Rating 
    - column: BackgroundCheckStatus 
The table should have the title "DriverAccounts" und the data must be loaded from the server with the following relative URL: 
    "/VehicleService/driveraccount/platformuser/{id}"

3. The RiderAccountView must contain the following fields: 
    - name: DefaultPaymentMethod   type: LONG 
    - name: Notes   type: STRING 
    - name: PlatformUser   type: PlatformUser 
    - name: Rating   type: DOUBLE 
The data source for the [PlatformUser] select control should be loaded from the relative URL: 
    "/PlatformUserService/platformuser"   (HTTP-GET) 
An existing RiderAccount entity should be loaded from the relative URL: 
    "/PlatformUserService/rideraccount/{id}"   (HTTP-GET) 
If a new RiderAccount entity has been created, the new entity should be posted to the relative URL: 
    "/PlatformUserService/rideraccount"   (HTTP-POST) 
If an existing RiderAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/PlatformUserService/rideraccount/{id}"   (HTTP-PUT) 
If an existing RiderAccount entity has to be deleted, the following relative URL should be called: 
    "/PlatformUserService/rideraccount/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Trip columns: 
    - column: CompletedAt 
    - column: RequestedAt 
    - column: PriceCurrency 
    - column: Service 
    - column: StartedAt 
    - column: AcceptedAt 
    - column: DurationMinutes 
    - column: DriverAccount 
    - column: Status 
    - column: DistanceKm 
    - column: PriceAmount 
    - column: RiderAccount 
    - column: OriginCity 
    - column: Vehicle 
    - column: CanceledAt 
    - column: DestinationCity 
The table should have the title "Trips" und the data must be loaded from the server with the following relative URL: 
    "/VehicleService/trip/rideraccount/{id}"