Open ashgansh opened 2 months ago
The most important fields should be:
DE3
=> processing code
DE4
=> transaction amount (in lowest possible denomination, cents for example)DE6
=> billing amount (in lowest possible denomination, cents for example)DE22
=> POS entry mode (chip, contactless, ... + pin capability)DE25
=> POS condition code (normal transaction, ecom payment, mail/telephone order, verification check, ...)DE43
=> acquirer name and location
DE49
=> transaction currency code (ISO4217)DE51
=> billing currency code (ISO4217)I would only focus on the 1987 version of the ISO8583 standard. The newer versions are not used by the biggest payment schemes.
The wikipedia article on the ISO8583 standard shouldn't be underestimated. It has a great summary of all the important data elements from the 1987 version.
@lrnt any sample we could put here?
@lrnt any sample we could put here?
Created a PR to add some samples: #2
did a first iteration #3
A lot of the tooling for payments is written in golang.
To get this project started we'd actually need to start to parse iso8583 messages.
basically going from left to right:![image](https://github.com/ashgansh/iso8583-posthog/assets/11430621/c8db0169-6517-40d8-917e-adb62ff0fd38)
Here's some inspiration of an existing project that does did.
https://github.com/moov-io/iso8583
There's also this resource: https://iso8583.info/
happy to pay for an account if it helps anyone move on this