Working with payment systems, I kept running into the same frustrations with existing ISO 8583 libraries:
Everything comes back as String (then you convert it yourself)
Nested subfields (TLV, private fields, etc.) are painful or unsupported
Configuration is usually locked in annotations or static XML
Fixed-length and ISO 8583 messages often need completely different code paths
I got tired of fighting the tools, so I built alatka-messages .
What is alatka-messages?
It’s a Java library focused on parsing and building both fixed-length and ISO 8583 messages.
Not a full payment switch (like jPOS). Just a clean, modern message definition + pack/unpack layer.
What makes it different?
1. Proper nested subdomain support
Supports TLV, ULV, bitmap subfields, and deep nesting. This is especially useful for UnionPay and other schemes with complex private fields.
2.…