Overview
Summary
Contact
Donate
Imprint
Prompt for the
UserAccountApp
Please create a React-JS application for the UserAccountModule. The application has to offer the following views for the user interface: 1. ComplianceCheckView 2. PayoutView 3. RefundView 4. SupportCaseView 5. UserAccountView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below. 1. The ComplianceCheckView must contain the following fields: - name: CheckType type: STRING - name: Details type: STRING - name: PerformedAt type: DATE - name: Result type: STRING - name: SanctionListEntry type: SanctionListEntry - name: Status type: STRING - name: Transaction type: Transaction - name: UserAccount type: UserAccount The data source for the [Transaction] select control should be loaded from the relative URL: "/TransactionService/transaction" (HTTP-GET) The data source for the [UserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) The data source for the [SanctionListEntry] select control should be loaded from the relative URL: "/CountryService/sanctionlistentry" (HTTP-GET) An existing ComplianceCheck entity should be loaded from the relative URL: "/UserAccountService/compliancecheck/{id}" (HTTP-GET) If a new ComplianceCheck entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/compliancecheck" (HTTP-POST) If an existing ComplianceCheck entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/compliancecheck/{id}" (HTTP-PUT) If an existing ComplianceCheck entity has to be deleted, the following relative URL should be called: "/UserAccountService/compliancecheck/{id}" (HTTP-DELETE) 2. The PayoutView must contain the following fields: - name: CompletedAt type: DATE - name: CreatedAt type: DATE - name: Currency type: Currency - name: FundingSource type: FundingSource - name: Status type: STRING - name: TotalAmount type: DOUBLE - name: UserAccount type: UserAccount The data source for the [Currency] select control should be loaded from the relative URL: "/CurrencyService/currency" (HTTP-GET) 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 Payout entity should be loaded from the relative URL: "/UserAccountService/payout/{id}" (HTTP-GET) If a new Payout entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/payout" (HTTP-POST) If an existing Payout entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/payout/{id}" (HTTP-PUT) If an existing Payout entity has to be deleted, the following relative URL should be called: "/UserAccountService/payout/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PayoutItem columns: - column: Transaction - column: Payout - column: Amount - column: Reference - column: Status The table should have the title "PayoutItems" und the data must be loaded from the server with the following relative URL: "/TransactionService/payoutitem/payout/{id}" 3. The RefundView must contain the following fields: - name: Amount type: DOUBLE - name: CompletedAt type: DATE - name: CreatedAt type: DATE - name: Currency type: Currency - name: Reason type: STRING - name: Status type: STRING - name: Transaction type: Transaction - name: UserAccount type: UserAccount 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 [UserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing Refund entity should be loaded from the relative URL: "/UserAccountService/refund/{id}" (HTTP-GET) If a new Refund entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/refund" (HTTP-POST) If an existing Refund entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/refund/{id}" (HTTP-PUT) If an existing Refund entity has to be deleted, the following relative URL should be called: "/UserAccountService/refund/{id}" (HTTP-DELETE) 4. The SupportCaseView must contain the following fields: - name: Channel type: STRING - name: ClosedAt type: DATE - name: Description type: STRING - name: Dispute type: Dispute - name: OpenedAt type: DATE - name: SecurityIncident type: SecurityIncident - name: Status type: STRING - name: Subject type: STRING - name: Transaction type: Transaction - name: UserAccount type: UserAccount The data source for the [Transaction] select control should be loaded from the relative URL: "/TransactionService/transaction" (HTTP-GET) The data source for the [SecurityIncident] select control should be loaded from the relative URL: "/RegionService/securityincident" (HTTP-GET) The data source for the [Dispute] select control should be loaded from the relative URL: "/FundingSourceService/dispute" (HTTP-GET) The data source for the [UserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing SupportCase entity should be loaded from the relative URL: "/UserAccountService/supportcase/{id}" (HTTP-GET) If a new SupportCase entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/supportcase" (HTTP-POST) If an existing SupportCase entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/supportcase/{id}" (HTTP-PUT) If an existing SupportCase entity has to be deleted, the following relative URL should be called: "/UserAccountService/supportcase/{id}" (HTTP-DELETE) 5. The UserAccountView must contain the following fields: - name: AccountType type: STRING - name: ClosedAt type: DATE - name: CreatedAt type: DATE - name: PasswordHash type: STRING - name: PrimaryEmail type: STRING - name: Status type: STRING An existing UserAccount entity should be loaded from the relative URL: "/UserAccountService/useraccount/{id}" (HTTP-GET) If a new UserAccount entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/useraccount" (HTTP-POST) If an existing UserAccount entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/useraccount/{id}" (HTTP-PUT) If an existing UserAccount entity has to be deleted, the following relative URL should be called: "/UserAccountService/useraccount/{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/useraccount/{id}" Add a HTML table to the view with the following RiskAssessment columns: - column: RiskLevel - column: UserAccount - column: Transaction - column: AssessedAt - column: Score - column: Reason The table should have the title "RiskAssessments" und the data must be loaded from the server with the following relative URL: "/TransactionService/riskassessment/useraccount/{id}" Add a HTML table to the view with the following UserAddress columns: - column: Line1 - column: State - column: Line2 - column: PostalCode - column: UserAccount - column: IsPrimary - column: City - column: AddressType - column: Country The table should have the title "UserAddresss" und the data must be loaded from the server with the following relative URL: "/CountryService/useraddress/useraccount/{id}" Add a HTML table to the view with the following Refund columns: - column: Transaction - column: UserAccount - column: CreatedAt - column: Amount - column: Currency - column: Reason - column: Status - column: CompletedAt The table should have the title "Refunds" und the data must be loaded from the server with the following relative URL: "/UserAccountService/refund/useraccount/{id}" Add a HTML table to the view with the following ComplianceCheck columns: - column: Transaction - column: CheckType - column: PerformedAt - column: Details - column: UserAccount - column: Status - column: SanctionListEntry - column: Result The table should have the title "ComplianceChecks" und the data must be loaded from the server with the following relative URL: "/UserAccountService/compliancecheck/useraccount/{id}" Add a HTML table to the view with the following AccountBalance columns: - column: LastUpdatedAt - column: PendingAmount - column: UserAccount - column: Currency - column: AvailableAmount The table should have the title "AccountBalances" und the data must be loaded from the server with the following relative URL: "/UserDeviceService/accountbalance/useraccount/{id}" Add a HTML table to the view with the following Chargeback columns: - column: Currency - column: Amount - column: OpenedAt - column: ClosedAt - column: UserAccount - column: Transaction - column: Status - column: ReasonCode The table should have the title "Chargebacks" und the data must be loaded from the server with the following relative URL: "/UserDeviceService/chargeback/useraccount/{id}" Add a HTML table to the view with the following UserKycVerification columns: - column: RequestedAt - column: Notes - column: UserAccount - column: Reviewer - column: Status - column: VerificationType - column: CompletedAt - column: UserDocument The table should have the title "UserKycVerifications" und the data must be loaded from the server with the following relative URL: "/UserDocumentService/userkycverification/useraccount/{id}" Add a HTML table to the view with the following FundingSource columns: - column: UserAccount - column: CreatedAt - column: Status - column: LastUsedAt - column: Type The table should have the title "FundingSources" und the data must be loaded from the server with the following relative URL: "/FundingSourceService/fundingsource/useraccount/{id}" Add a HTML table to the view with the following UserDocument columns: - column: ExpiresAt - column: IssuedBy - column: Status - column: IssuedAt - column: DocumentType - column: DocumentNumber - column: CreatedAt - column: UserAccount The table should have the title "UserDocuments" und the data must be loaded from the server with the following relative URL: "/UserDocumentService/userdocument/useraccount/{id}" Add a HTML table to the view with the following SupportCase columns: - column: Description - column: Status - column: Subject - column: Channel - column: Dispute - column: UserAccount - column: ClosedAt - column: Transaction - column: OpenedAt - column: SecurityIncident The table should have the title "SupportCases" und the data must be loaded from the server with the following relative URL: "/UserAccountService/supportcase/useraccount/{id}" Add a HTML table to the view with the following Merchant columns: - column: DisplayName - column: LegalName - column: WebsiteUrl - column: CreatedAt - column: UserAccount - column: Category - column: Status The table should have the title "Merchants" und the data must be loaded from the server with the following relative URL: "/MerchantService/merchant/useraccount/{id}" Add a HTML table to the view with the following SecurityIncident columns: - column: Severity - column: Description - column: DetectedAt - column: Type - column: ResolvedAt - column: Merchant - column: UserAccount The table should have the title "SecurityIncidents" und the data must be loaded from the server with the following relative URL: "/RegionService/securityincident/useraccount/{id}" Add a HTML table to the view with the following UserProfile columns: - column: PhoneNumber - column: LastName - column: DateOfBirth - column: TimeZone - column: UserAccount - column: Language - column: FirstName The table should have the title "UserProfiles" und the data must be loaded from the server with the following relative URL: "/UserDocumentService/userprofile/useraccount/{id}" Add a HTML table to the view with the following UserLoginSession columns: - column: ExpiresAt - column: SessionToken - column: CreatedAt - column: UserAgent - column: UserDevice - column: Status - column: UserAccount - column: IpAddress The table should have the title "UserLoginSessions" und the data must be loaded from the server with the following relative URL: "/UserDeviceService/userloginsession/useraccount/{id}" Add a HTML table to the view with the following UserDevice columns: - column: DeviceType - column: OperatingSystem - column: DeviceFingerprint - column: LastSeenAt - column: UserAccount - column: Trusted The table should have the title "UserDevices" und the data must be loaded from the server with the following relative URL: "/UserDeviceService/userdevice/useraccount/{id}" Add a HTML table to the view with the following Payout columns: - column: Status - column: TotalAmount - column: CompletedAt - column: UserAccount - column: CreatedAt - column: Currency - column: FundingSource The table should have the title "Payouts" und the data must be loaded from the server with the following relative URL: "/UserAccountService/payout/useraccount/{id}" Add a HTML table to the view with the following PaymentMethod columns: - column: Priority - column: MethodType - column: FundingSource - column: IsDefault - column: UserAccount - column: Label The table should have the title "PaymentMethods" und the data must be loaded from the server with the following relative URL: "/SubscriptionService/paymentmethod/useraccount/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint