I built a fintech application however am having issues with unsupported domains FE UI updates and database table server updates?

Question

https://drive.google.com/drive/folders/1BKIsYPohxYjU9ucQbcfhcEdAKwYTtC92?usp=drive_link - bank error bug not updating database tables and front end user interface

https://drive.google.com/drive/folders/1I3PoEmPZJMSGSh6YCl0bEmAY1sfB79Ex?usp=drive_link - crypto error bug insert not showing on the blockchain explorer, issue crwated and unassigned https://github.com/blockchain/blockchain-wallet-v4-frontend/issues/6538

https://drive.google.com/drive/folders/1DPyX-AxO6o_s-RgpI55hozSAEF5CmhlC?usp=sharing - fintech application screen captures and mixed unupdated screens mock data.

https://drive.google.com/drive/folders/101e9NnxtAZDSVL-FETTIF_W85rZFYKpk?usp=sharing - research paper introduction

Answer 1

Hi John,

My name is jason and I an an independent advisor and windows user,

Unfortunatly the files are not loading my end but if the main issues are:

1. Bank error bug: Database tables and frontend UI not updating
2. Crypto error bug: Insert not showing on blockchain explorer
3. Mixed/unupdated screens: UI not reflecting backend state
4. Unsupported domains: Possibly CORS, routing, or domain validation issues

Suggested Debugging Steps

1. Bank Error Bug – DB + UI Not Updating

• Backend: Check if the API endpoint handling the bank transaction is returning a success response (200 OK) but failing silently (e.g., DB transaction rollback). Add logging around the DB insert/update logic — especially if using an ORM like Sequelize or Eloquent. Confirm DB schema matches the expected payload (e.g., no missing NOT NULL fields or constraint violations).
• Frontend: Ensure the UI is listening for the correct response and updating state (e.g., React useEffect, Vue watch, etc.) Check if the UI is caching stale data (e.g., Redux store, Apollo cache)

2. Crypto Insert Not Showing on Blockchain Explorer

Confirm the transaction is being broadcast to the network (e.g., via Web3.js, ethers.js)

Use a tool like Etherscan or BlockCypher to manually push and verify the raw transaction

• Check for: Nonce mismatch Gas limit too low Transaction dropped from mempool

If the insert is local-only (e.g., mock chain), it won’t show on public explorers.

3. Mixed/Unupdated Screens

• This often happens when: State is not refreshed after mutation Backend returns stale data due to caching (e.g., Redis, Cloudflare) UI is not re-rendering due to shallow prop comparison

Try:

// Force re-fetch after mutation
await mutate('/api/transactions') // if using SWR
queryClient.invalidateQueries('transactions') // if using React Query

4. Unsupported Domains

• If this is a CORS issue, check: Server response headers: Access-Control-Allow-Origin Preflight OPTIONS request handling
• If it’s a routing issue, verify: DNS records and SSL certs Reverse proxy (e.g., NGINX) forwarding rules Allowed hosts in backend config (e.g., Django ALLOWED_HOSTS, Express cors())

Next Steps

If you can share:

The specific error messages (console logs, HTTP responses)

Snippets of the failing API call or DB logic

Frameworks/libraries in use (e.g., Laravel, React, Node.js, Solidity)

Answer 2

Thank you for your detailed response. I am not sure why the links are not visible? Maybe because they just over size limit? I had to use hyperlinks because the file sizes were too big. However the links are set to share with anyone in the google drive so should technically be viewable. Could just be the web domain you opened them in

Just focusing on the banking issue for now.

When trying to send the transaction, my ai development tool is asking for the relevant banks secret api key and I have to email and ask the bank for it I have only emailed and asked two of the respective banks. They haven't responded with the secret key. I have the email I sent the one bank and am waiting for a response.

I don't know why I can't just pull this information off their website or through my banking profile.

Maybe you have a work around or an alternative bank with accessible database access keys?

"Database Change Request

Change Request Details

Request Type: API Access Credentials Request

Current Naming/Structure: Standard Bank API Integration

Proposed Changes: Database Secret Keys for SBSA API

Justification:

We are requesting access to the Standard Bank API integration credentials for our banking application.

Our application requires the following credentials to establish a secure connection with the Standard

Bank API: 1. Client ID 2. Client Secret 3. API Access Token generation endpoint details 4. OAuth2

authentication configuration parameters These credentials are essential for implementing secure

banking operations including account information retrieval, transaction processing, and payment

initiation through the Standard Bank API gateway. The integration will be used for: - Real-time account

balance inquiries - Transaction history retrieval - Payment processing and validation - Compliance

reporting All credentials will be stored securely using encrypted environment variables and will only be

accessible to authorized backend services.

Dependency Information:

This integration request is dependent on: 1. Standard Bank API Developer Portal access 2. Application

registration approval from Standard Bank 3. KYC verification completion for our organization 4. OAuth2

flow configuration for token management 5. Webhook endpoint configuration for real-time notifications

Technical Requirements: - Secure storage of Client ID and Client Secret in encrypted environment

variables - Implementation of OAuth2 token refresh mechanism - Compliance with Standard Bank API

10/11/25, 10:29 PM Gmail - DB Change Request: API Access Credentials Request - Standard Bank API Integration

rate limits and usage policies - PCI DSS compliance for handling financial data - Multi-factor

authentication for administrative access Expected Timeline: - Application review: 3-5 business days -

Credential provisioning: 1-2 business days after approval - Integration testing: 5-7 business days -

Production deployment: Upon successful testing Please provide the credentials via secure channel

(encrypted email or secure portal download).

Action Required

Please review this change request and provide feedback on:

Naming convention compliance

Impact on existing integrations

Required migration steps

Timeline for implementation"