Hi Colleagues

I would just like to wether it is possible to link a Database to a website.

my website would be one whereby members have to create accounts and put money in their accounts by transfering the funds to our Business Bank Account and then we use that reference to put credits in their Online Accounts.

they would then use those credits to buy our products & services online.

So my difficulty lies in this...

I want my business database to be connected to the websiteand memebers online account, so that:

1. when a member transfers money into my businesses bank account, i can quickly and
with ease, update that members account on my database with the amount of money
they paid. fort e.g.

(**if their account balance is $70 and they paid $20 in my bank
account i want to be able to make his new balance $90 and then it
should reflect on his account on the website)

2. If the member buys on of our products online, then i want that his online account
balance to be deducted accordingly and that transaction to be reflected in his
online account and on our business database.


is this possible?, how and is there any product out there already, should i visit a programmer, software developer? any ideas, references,information and advise on this one would be greatly welcome.

i am new to web desig, i have the ideas but really dont know much, therefor all help is welcome? is there a software to manage ewallets?

Dani AI

Generated

A compact, practical checklist for turning this into a safe e-wallet. is right that a developer will build it, but when you interview one (or plan it yourself) look for these concrete items and ask for them by name: an immutable transaction ledger, atomic credit/debit operations, idempotent deposit processing, an admin reconciliation UI, and full audit logs.

Design patterns to ask for

  • Ledger-first: every credit/debit is an immutable row in transactions. Balance is the sum of transactions (easy to audit).
  • Cached-balance: keep a balance column for speed but always write a transactions row inside the same DB transaction and use checks/locking to avoid race conditions.

Example patterns (pseudo-SQL)

-- credit (use unique reference to avoid double-credit)
BEGIN;
INSERT INTO transactions (user_id, amount, type, reference, created_at) VALUES (?, ?, 'credit', ?, NOW());
UPDATE users SET balance = balance + ? WHERE id = ?;
COMMIT;
-- debit with atomic check
BEGIN;
UPDATE users SET balance = balance - ? WHERE id = ? AND balance >= ?;
-- if rows_affected = 1 then insert transactions row and COMMIT, else ROLLBACK (insufficient funds)

Operational and reliability tips

  • For manual bank deposits require a unique deposit reference and mark deposits as PENDING until an admin clears them after reconciliation. Store raw bank statement lines and match by reference or amount/date to avoid manual mistakes. Use idempotency keys for webhook-driven flows.

Security and compliance

  • Use TLS, parameterized queries, input validation, strong admin access controls and immutable audit logs (see OWASP guidance). Use DB transactions (ACID) to prevent inconsistencies. Check local rules about holding customer funds; some jurisdictions require registration. If unsure, hire a developer experienced with payments or consider a payment provider that offers wallet/store-credit features.

References: ACID (Wikipedia) · OWASP Top Ten ·

yes it can be possible but you have to ask a programmer to do that.. any good programmer will solve this... not a big issue...
have you solved the problem?

yes it can be possible but you have to ask a programmer to do that.. any good programmer will solve this... not a big issue...
have you solved the problem?

not yet finding the ryte programmer still...but it feels good to know its possible thanks!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.