svapnil
Show HN: Groupchat, Open Source Slack for Developers
Hey Hacker News,My name's Svapnil Ankolkar and I missed talking to human being when I used AI to code. I built this app since I wanted to spend more with people instead of talking to LLMs. Developers can run their Claude Code / Codex within the app to pair program or work on projects together.The client is open source and I'm hoping to work with other developers to make this program even...
Source: former Erlang engineer
Better Fiat Banking Rails will matter more than Stablecoins
iso20022.js allows any developer to programatically move bank transfers with a business bank account by making ISO20022, the underlying messaging standard for money movement easier to use.
It's amazing how any developer can now move payments instantly using bank rails. I'd love for you all to take a look and let me know what you think.
Send a SEPA Payment Using JavaScript
Trade Memecoins on Discord
Building Multiplayer Voice-Based AI Apps
Would love to hear your thoughts or suggestions on where we take the project from here. Thanks!
The Bank Payment System Is Async
For financial calculations I recommend using Dinero.js
As far as I know, this is an international phenomenon. Keep in mind this is corporate banking, not consumer banking.
I'd happy answer any other questions you have @ https://cal.com/woodside/iso20022js
ISO20022 has a huge namespace and can do all kinds of things. My current focus on making transaction banking namespaces more accessible (think pain.001 002 and 008) aswell as CAMT files
See the https://dinerojs.com/ package to see how money is handled (tldr it's a combination of currency and amount which helps us get to the root #)
I published iso20022js.com a few weeks ago, and I was incredibly surprised by the overwhelming traction it received. I wanted to share more about some payments fundamentals that engineers might need in order to run this package - specifically, how sending these types of bank payments actually works.
How to Send a Swift Wire for Developers
It's true that REST APIs operate under the assumption of processing at request time, while not the case with files. That's what makes Bank REST APIs so tricky - processing doesn't ever actually occur at request time.
There are so many crazy formats that are supported. Simpler is better imo
I agree that simplicity and open standards will win. SFTP is straightforward and has worked well in the past. In banking and finance, SFTP is what powers most programmatic corporate banking. Eventually, I think we'll see SFTP and message queues (like SQS) used more often as processing speeds up. I believe message queues are what powers much of real time payment processing already (https://news.ycombinator.com/item?id=36805571)
Where Banking APIs Fall Short
Iso20022.js: Why Every Bank's APIs Suck
https://docs.iso20022js.com/quickstart#step-4-send-the-payme...
The test cases for this library validate against the XSD for the ISO files, which could be extended to handle more test cases.
Banks sometimes offer a test SFTP endpoint they use. Engineers have had to do this from scratch at the companies they worked at in the past. If this is something you're interested in, we should talk more @ [email protected]
If you have more questions, I'd love to help you out - please shoot me an email @ [email protected]