Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Iso20022.js – Create payments in 3 lines of code

iso20022js.com

Post reply on HN
Print view View original

131–139 of 139 posts

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#131

Post by svapnil »

boursbenjamin wrote: post #108

It seems very clear and easy to use, well done! I am wondering if there is any test environment like with Stripe in order to validate the flow in development?

Thanks for the feedback boursbenjamin.

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 @ svapnil@woodside.sh

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#132

Post by datavirtue »

A4ET8a8uTh0 wrote: post #121
dawidloubser wrote: post #115

Based on my experience of building several payment gateways, it is my opinion that it's pretty much always "3 lines of code" (which isn't true about this library - more like "3 steps") to post a payment, even to the nastiest acquiring or banking API. The remaining 675,000 lines of code are to: - Perform Risk / Fraud scoring to decide whether you want to, indeed, process this payment. - Deal with the myriad of failure…

I completely agree. When I first saw some of the issues ( in US ), my first reaction was that of disbelief. I simply could not believe this is the way it is set up. If US has any defense, it is that it is not alone in this craziness as almost every bigger power center carefully manages its domain to ensure it remains a relevant player. To put it simply, there is too much money in managing different pipes. At this poi…

The government has typically abdicated payments to various proprietary networks and big banks in the US. Try getting your hands on the NACHA spec for our glacial "direct" deposit standard.

We also have no standard way of letting users authenticate to their bank to download transactions. Once you get logged in there is usually a way to get OFX (QFX) files but the process is manual. I happened on the European open banking documentation the other day...jealous.

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#133

Post by 0x457 »

actionfromafar wrote: post #76
pseudocomposer wrote: post #74

Earlier quoted context omitted.

You can have extensible structure and fields with JSON Schema, gRPC, Cap’n Proto, etc. There’s nothing XML-specific about that. The only thing XML gives you over any of those formats is unstructured mixing of text and data, which is more a foot-gun than anything. Oh, and of course, being significantly more verbose.

A niche thing maybe, but XML has comments, which I appreciate.

Why do you need comments in machine generated files meant for other machines?

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#134

Post by actionfromafar »

0x457 wrote: post #133
actionfromafar wrote: post #76

Earlier quoted context omitted.

A niche thing maybe, but XML has comments, which I appreciate.

Why do you need comments in machine generated files meant for other machines?

It can be very helpful when trying to figure out why one machine won't understand another, for instance.

You can put meta-data in for debugging without compromising anything, schema wise.

Or in the case of config files, there can be detailed instructions on what fields are what they should contain.

The thing about XML is that it strikes a sweet-spot between machine readable files and human readable files. (I can't believe I'm coming out as an XML apologist!)

If it were only "by machines for machines", we wouldn't consider JSON, YaML or XML as much, we'd all go for Protocol Buffers or Parquet or something.

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#135

Post by cyanydeez »

bilekas wrote: post #85
cyanydeez wrote: post #75

Earlier quoted context omitted.

Custom schema means nothing against improper implementation

This has me a little dumbfounded as either really profound or slightly misguided. How do you mean? As I am reading this you think a custom schema wont effect an implementation, but how do you expect to implement an external service (API for example) without the required defined schema. That's kind of the definition of a schema in this scenario. Extending the schema might be another thing. But implementation can't wor…

First name is defined as a string. Great.

What's the first name?https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#136

Post by pixelbyaj »

logicalmind wrote: post #96
svapnil wrote: post #60

Earlier quoted context omitted.

Thanks for your comment mkuznets. I appreciate your input regarding XSD to class conversion - I agree that this is a super useful concept for sending ISO20022 files. I think there's always some ergonomic gap between these XML Schema generated classes and SDKs that developers are comfortable using. My intention for this library is for a non-payment developer to be able to interact with the ISO20022 schemas, while bein…

I am currently implementing an ISO20022 integration at a large financial institution. The way these generally work is that whatever network you're connecting with will require a certain standard number of an ISO20022 message. When you send the generated messages, they must be valid as per the specific schema in question. If not, they will be rejected. I'm speaking specifically about payment networks, not consumer lev…

Hi Svapnil, Sorry to bother in between but yeah logicalmind is right in this regards. @logicalmind you can use my solution which do all which is required for ISO20022 to create and validate. https://pixelbyaj.com/iso20022/#iso20022_about and for DEMO https://pixelbyaj.com/iso20022/demo/#/. I have all the required tools in the for the same.

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#137

Post by svapnil »

TheeWheel wrote: post #86

Do you have any plans to support ACH/NACHA payments?

Yes, ACH/NACHA payments work through ISO20022 aswell and are next up on the roadmap. I'd love to let you know when it's shipped - please shoot me an email at svapnil@woodside.sh so we can stay in touch!

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#138

Post by svapnil »

101008 wrote: post #25

Super stupid question, but this must have some kind of authentication, right? Where is that part?

The most straightforward way this is done is by SFTP'ing into banks. Check out step 4 here!

https://docs.iso20022js.com/quickstart#step-4-send-the-payme...

Re: Show HN: Iso20022.js – Create payments in 3 lines of code

#139

Post by katzinsky »

root_axis wrote: post #81
phkahler wrote: post #44

>> I'd love to know what you think and importantly know about any improvements you'd like us to make! I think it's scary to do any finance related stuff using NPM dependencies. How large is your dependency tree?

Why NPM in particular? Is there any package manager where you don't have to audit your dependencies?

NPM is particularly nasty because they've solved the issue of transitive dependencies having mismatched versions. This removes one of the biggest immediate pain points caused by having very large dependency graphs so you only feel the pain later on. Because of that you get this emergent behavior of unusually large dependency graphs in a lot of NPM packages.
Post reply on HN