For my case they are all new cardsIf it is particular card and it is not a new card just registered, you need check whether it was registered with a different account before. I have quite a few old cards registered not appearing in SimplyGo any more.
Have you been charged by SimplyGo previously? For virtual card, it takes time for SimplyGo to resolve the virtual card to an actual card and notify as the actual card. Apple Pay/Google Pay such will be later to get real time notification than the card itselfFor my case they are all new cards
It's been almost a month since adding the card and have crossed a month end cycle. I've had no issue with virtual cards so far to get instant notification. Also if I go into the app, the trip is shown almost instantly, just no push notification.Have you been charged by SimplyGo previously? For virtual card, it takes time for SimplyGo to resolve the virtual card to an actual card and notify as the actual card. Apple Pay/Google Pay such will be later to get real time notification than the card itself
It's been almost a month since adding the card and have crossed a month end cycle. I've had no issue with virtual cards so far to get instant notification. Also if I go into the app, the trip is shown almost instantly, just no push notification.
Nope only a single phone. Have not received notification for the new card I have from UOB, but works OK with new cards from other banks (such as DBS and HSBC).do you have another phone with SimplyGo app? SimplyGo seems can only push to 1 phone whether logging out or not.
have you ever received push notification for this card? any other card with SimplyGo on this phone?
may be worth trying to remove the card and add it again if other cards can receive push notification
Nope only a single phone. Have not received notification for the new card I have from UOB, but works OK with new cards from other banks (such as DBS and HSBC).
Have also tried removing the adding the card in Simply Go, and my phone too (so as to get a new virtual card number) but nothing works. Tried relogging in to SimplyGo, disable and enable again the trip notification, reset password and relogin in too.
but isn't it a bit strange that it will appear on the simplygo app the transaction, just not the push notification?in this case, it is likely some internal issue with this card on SimplyGo side, which will require some reset on SimplyGo side instead.
but isn't it a bit strange that it will appear on the simplygo app the transaction, just not the push notification?
Would agree on this design if they were using old technology available. In my view, it would have been designed broadly along the lines of:in this case, it is likely some internal issue with this card on SimplyGo side, which will require some reset on SimplyGo side instead.
If I were to design the notification system, it will be something like this:
1. the terminal(bus entry/exit, train gate entry/exit) captures the transaction details (e.g. the card details, virtual or actual, chip transaction id, code, etc) and sends the information in addition to the terminal info(the bus stop, which train station, entry or exit) to the SimplyGo system
2. The SimplyGo system processes the transaction after receiving it, determine whether it is considered as a charge (e.g. entry alone will not be charged til exit), calculate the fare based on information it has(whether it is a continuation from previous trip, etc), also obtain the actual card(I assume) if it is a virtual card such as Apple Pay
3. SimplyGo system will try to find the notification information registered with the actual card and send it to the providers(such as Apple, Google etc)
As you can receive fare charges normally, 1 & 2 seems working properly. you have other cards without notification issue, means your App notification is on and registered with the provider and SimplyGo can deliver notification. The only gap I see is that SimplyGo can't link the card with your App instance for notification.
I doubt SimplyGo gets virtual card to actual card mapping from the banks, they will have to integrate with all banks in the world. It is more likely from Visa/MasterCard instead. Nonetheless, it should be done per transaction. Otherwise, it is a loop hole for a merchant to get the mapping without any transaction.Would agree on this design if they were using old technology available. In my view, it would have been designed broadly along the lines of:
1) All tap in and tap out would trigger an event, and an entry would be logged on where the tap occurred, for which card, along with a time stamp
2) On tap out on an exit terminal event, look back to see in the last 2 hours how many trips could be linked together via directed graph to capture eligible transfers.
3) For cases where there are multiple taps on entry terminals, an end of day batch mode would validate and reclasify them as exit which largely applies to busses where the terminal could allow both entry/exit.
The notification system would only stop at 2), and an event based / messaging based system would be the right tool which then triggers a push notification to the client device (on all devices the user is logged in on).
The virtual card to physical card look up, perhaps it may be onerous to look up each of the bank's database on a live basis. It would be easier to do a daily sync, store them in an optimised key value pair database to determine how to roll up the transactions to the physical card billing number.
Not sure why you'll say that because event driven design has been around since the days of mainframe, and it's been used to process transactions for many decades (eg. card transactions).I doubt SimplyGo gets virtual card to actual card mapping from the banks, they will have to integrate with all banks in the world. It is more likely from Visa/MasterCard instead. Nonetheless, it should be done per transaction. Otherwise, it is a loop hole for a merchant to get the mapping without any transaction.
In my line of work, event/message based are overrated. It just makes some architects look good on paper only. In actual implementation, a lot of issues without trace of event/message loss. Anyway, it is just delivery mechanism, the actual logic is not in the delivery of data.
Sidetrack a bit. I see someone with real implementation experience good. Solution architect architect the whole entire IT architecture. Their job does not or need not delve into the implementation details as that will derail from the overall big picture.In my line of work, event/message based are overrated. It just makes some architects look good on paper only. In actual implementation, a lot of issues without trace of event/message loss. Anyway, it is just delivery mechanism, the actual logic is not in the delivery of data.
He is most likely referring to the more modern messaging system not the mainframe kind. E.g I use JMS and packet loss do occur under intense load.Not sure why you'll say that because event driven design has been around since the days of mainframe, and it's been used to process transactions for many decades (eg. card transactions).
I mean the modern ones, like Kafka based, not mentioning the extra infra/system need maintainNot sure why you'll say that because event driven design has been around since the days of mainframe, and it's been used to process transactions for many decades (eg. card transactions).
This one would be the recipe for disaster - cost over runs, cannot meet deliverable, no choice but pump more money in. The cross border development thing does not work if something is not in maintenence mode in my viewSidetrack a bit. I see someone with real implementation experience good. Solution architect architect the whole entire IT architecture. Their job does not or need not delve into the implementation details as that will derail from the overall big picture.
I test water this role previously for a while and then give up. It does not suit me and you need to liaise with developers from all over the world on different timezone!
Actually cross border the young developers don't like to do maintenance. They want create from scratch instead. Reason to do maintenance required knowledge of existing codebase and that by itself is a skillset by its own becuz it could be on legacy technology for which the cross border youngsters never do before and if you force they will screw it up even existing working features some more. That is why I am also employed specifically for maintenance aka clean up brown colour stain the original developers left behind.This one would be the recipe for disaster - cost over runs, cannot meet deliverable, no choice but pump more money in. The cross border development thing does not work if something is not in maintenence mode in my view