Hacker Newsnew | past | comments | ask | show | jobs | submit | Nars088's commentslogin

Maintainer here, this is the actual quiz we gave our new joinees while onboarding :)


Hyperswitch is on a mission to build payment infrastructure that serves billions of people at scale - a utility like water or electricity


True, still trying to fix that! Need to figure out how to implement 'show don't tell' with GPT


Thanks for the feedback (I'm a collaborator)

- We were thinking ideally the selection menu should take text input but parked that for later

Also the visualise buttons get enabled as soon as you hit generate button for the corresponding block!


It probably comes down to how many have actually added their cards to GPay and Apple pay, best to experiment and check if adding paypal improves your conversions


> I also like not having a single payment provider have the ability to cut off my revenue if some kind of issue arises

How are you going about this currently? Have you integrated Paypal separately or do you have any other processor along with stripe?


The payment page shows a stripe and PayPal button, and the user can decide which they prefer.


Hyperswitch is free to use for the first 10k transactions of the month. After that it costs $0.04 per transaction. It is a payment switch that comes pre integrated with major processors. So as a merchant your business relationship with processors like Stripe or Adyen remains the same (I'm affiliated with this product)


I've seen some sites use Google maps API to suggest your exact address, pretty cool


Oh good grief those are annoying though. "We've found a more exact version of the address you entered" no you haven't, you've randomly substituted my neighbour's house number and dropped the county name. It's even worse for my office address: it's a large building shared by many companies; without the correct company name the receptionist cannot contact the right recipient. The APIs though like to either replace the company name with a random unrelated one or drop it entirely.

Wonder how many misdeliveries these features cause? Both my and GP's annoyances can be solved simply by leaving the entered data unmangled. I've supplied precisely what needs to go on the packaging to get the item to me. All of the text is necessary, sufficient and in the correct order. Don't change those things. You don't know better.


When moving in, some two years ago, to an apartment located close to the very centre of Kraków - one of the biggest and well-known cities in Poland - I discovered that Google somehow got the postal code wrong for the entire street. The code they had on record actually pointed some 20-30 kilometers outside of Kraków. It took more than a year of sending corrections to Google Maps before they finally fixed the postal code... of my building alone. The rest of the street still has the wrong code.

Want to know why I bothered to try and get it fixed all this time? Because this little mistake made it nearly impossible to order food via any of the food order services. Uber Eats, Glovo, Pyszne.pl, etc., in their infinite tech startup wisdom, all integrated with Google API to fetch postal codes based on address, and use them to filter out restaurants that can deliver to the user's location. With my address mistakenly mapping to a village 20+ kilometers outside of Kraków, do you care to guess how many options I had to order from?

That, plus it also messed up ordering taxis via FreeNow and Bolt, which also integrate with Google API for stupid reasons. This also means the drivers need to use separate apps to navigate around the center, because Google doesn't have data on which roads are banned for traffic except buses and taxis, and the parent companies are too cheap to license from a provider that has this data. All while in the apps themselves, if your route starts, ends, or even crosses anywhere near the city center, the estimated time data shoots up to some ridiculous values, while the map gets entirely confused, as Google Maps integration is adamant that the route we're on is physically impossible.


Shopify does this to my address. I live at 106 and Shopify sites like to decide that I live at 106 bis, the next building over. That building only has a shared mailbox between three families, so packages that end up there are lost forever with no accountability.


I think there is a strong relationship between the average ticket size and payment experience. It is almost like it is the user's problem if the ticket size is high (hence the website need not necessarily invest in creating a good payment experience). Something like insurance websites.

The ones that really seem to think about the payment experience are the ones that have low to medium average ticket size and high transaction volumes. It is in the website's best interest to ensure each and every transaction goes through


Stripe's link has a similar experience


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: