Live data from Hacker News

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

iso20022js.com

81–90 of 139 posts

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

#81

>> 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?

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

#82
post #72
post #68

Earlier quoted context omitted.

What XML has to do with bank-specific messages that have to be parsed and processed? It’s just a markup format.

It's the extensible nature of XML that gives it an advantage. You can add custom elements and attributes whilst conforming to the base schema. Granted, XML isn't the only format where this is possible. You can sort of achieve it with JSON, though XML's namespace system helps deal with name collisions. Adding bank-specific messages wouldn't be possible (or would be difficult) with fixed-column formats, for example, un…

Iso200022 are tagged as well.

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

#85
post #71

Earlier quoted context omitted.

Banks add their own features to the spec - imagine they want to add a new "Bank only" attribute that makes their XML schema differentiated and better in some way. ISO20022 / XML allows this to be possible without breaking anything. In the past payment formats used to be fixed width text files - impossible to change or improve functionality for

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 work without adhering to the defined schema of the provider? Right?

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

#87
post #71
post #68

Earlier quoted context omitted.

What XML has to do with bank-specific messages that have to be parsed and processed? It’s just a markup format.

Banks add their own features to the spec - imagine they want to add a new "Bank only" attribute that makes their XML schema differentiated and better in some way. ISO20022 / XML allows this to be possible without breaking anything. In the past payment formats used to be fixed width text files - impossible to change or improve functionality for

> impossible to change or improve functionality for

You have to think inside the box!

What if, say, instead of lastname "SMITH" we used "SMITH,FEE: 5.65"

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

#88
Hey this seems really interesting. But I have questions about this statement “.

In order to transmit bank payments programatically, you must have direct transmission enabled with your banking partner. If you have any questions about this, don’t hesitate to reach out to us.

So do we need to get this enabled on a per bank basis or a per account basis?

Post reply on HN