3 ms·
Not sure if Starlink was set up this way, but teaching moment: Before taking a payment on a SPA, everyone please make a separate database transaction that reco
by coding123 4y ago
Not sure if Starlink was set up this way, but teaching moment:
Before taking a payment on a SPA, everyone please make a separate database transaction that records the user - come back to display the UI for CC collection AFTER. If you try to add the user, run the CC and return in one shot, while attractive from a transactional perspective, it's NOT good if your DB rolls back but the third party CC processing did not.
Then you end up with users that pay, but no record of payment in your DB. Get it right people.
Yes you can at least confirm your own transaction is committed in one shot THEN perform the CC, but separating these two out is still the best bet.
- hedora 4y agoThis is an intentional dark pattern. Starlink goes out of its way to avoid allowing non customers interact with them. For example, dishy doesn’t ship with an ethernet jack for its router or enough hardware to actually mount it in most situations. They don’t let you even view the accessories store (or prices for the mandatory extra equipment) until after they ship the dish + router.