Top Up

General Steps to Connect and Top Up

Open the eWallet App: Log in to your eWallet account.
Locate 'Add Money' or 'Reload': Look for the balance section and click "Add Money," "Reload," or "Top Up."
Select Payment Method: Choose "Bank Account," "Debit Card," or "Direct Debit".
Link the Account:
- Card: Enter your debit/credit card details (card number, CVV, expiry).
- Bank App: Select your bank, and the app will redirect you to your bank's portal to authorize the link (e.g., using FPX in Malaysia or Osko/PayID in Australia).
Verify and Top Up: Follow the security prompts (OTP) to finalize the link, then select the amount to transfer.

Facebook

user selects the add money or reload button.
Then he can select which type of reload, whether its the credit card or through the bank account.
- if its credit card, enter the details for the credit card in a credit card object, and store details in the database user_bank_details / user_card_details, or add a new record type in user_auth, for the auth_type TOP_UP, and the credentialHash will be the payment token. which is generated by the provider like stripe, or user enters directly,
- Another way is we can use tokenization, such as credential on file or COF, and gateway tokenization, is one way, where the user enters the card details one time to the platform, then we will generate a token and it can be reused for future transactions so that the user does not need to enter the token each time he wants to make a new purchase.
- another way is Network Tokenization, which is storing the user PAN (primary account numbers) the 16 digit number on the card with a token generated by the card provider. so we dont have to retrieve the user card details, as the card provider will provide us the tokenized token.
One the result from the API is confirmed success, future

for each column, such as the card placeholder and expiry, check whether the information is correct, if its an invalid number, or date, show actively, if its invalid.
- for this feature we need to check what this architecture looks like. because actively query is definitely not from database, it could be cache, but to check the entire industry database to see if the card number exist ? im not sure how it is done.
There is no need to concern for multiple accounts because currently there is only one user equals one touch n go account. but the logic remains the same. no issue.
- just that when we queryUserCardDetails. we can connect using userId instead of accountId. since its a 1-1 relationship. because if we connect account, there may be multiple different accounts.