Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/tochemey/netcore8583
NetCore8583 is a library that helps parse/read and generate ISO 8583 messages for .NET Core
https://github.com/tochemey/netcore8583
banking csharp dotnet-core financial-data iso8583 netcore
Last synced: 3 days ago
JSON representation
NetCore8583 is a library that helps parse/read and generate ISO 8583 messages for .NET Core
- Host: GitHub
- URL: https://github.com/tochemey/netcore8583
- Owner: Tochemey
- License: mit
- Created: 2018-06-20T11:56:31.000Z (over 6 years ago)
- Default Branch: main
- Last Pushed: 2024-12-01T20:52:36.000Z (21 days ago)
- Last Synced: 2024-12-10T07:51:52.930Z (12 days ago)
- Topics: banking, csharp, dotnet-core, financial-data, iso8583, netcore
- Language: C#
- Homepage:
- Size: 200 KB
- Stars: 35
- Watchers: 6
- Forks: 22
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
- Contributing: contributing.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Code of conduct: code_of_conduct.md
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# NetCore8583
_NetCore8583 is considered feature complete and mature.
No future feature development is planned, though bugs and security issues are fixed._
[](https://github.com/Tochemey/NetCore8583/blob/main/.github/workflows/ci.yml)
[](https://opensource.org/licenses/MIT)
[](https://www.nuget.org/packages/NetCore8583/)
[](https://www.nuget.org/packages/NetCore8583/)
[](https://masterminds.github.io/stability/maintenance.html)
## Introduction
NetCore8583 is a dotnet core implementation of the ISO 8583 protocol.
NetCore8583 is a library that helps parse/read and generate ISO 8583 messages. It does not handle sending or reading them over a network connection, but it does parse the data you have read and can generate the data you need to write over a network connection.
## ISO 8583 overview
ISO8583 is a message format used for credit card transactions, banking and other commercial interaction between different systems. It has an ASCII variant and a binary one, and it is somewhat convoluted and difficult to implement.
The main format of the ISO8583 is something like this:
|ISO header (optional)|Message Type|primary bitmap|secondary bitmap (optional)|data fields|
|---------------------|------------|--------------|---------------------------|-----------|
The ISO header is a string containing some code that can vary according to the message type.
The message type is a number expressed as 4 hex digits (or 2 bytes when using binary format).
The bitmap is 64 bits long and it is encoded as 16 hex characters or as 8 bytes when using binary format. Every bit that is set in the bitmap indicates that the corresponding field is present. If the first bit is set, then field 1 is present, and so on.
The fields in the message are numbered from 1 to 64. Field 1 is the secondary bitmap, if present. The secondary bitmap allows for the message to have fields from 65 to 128.
Wikipedia has [a very good article](http://en.wikipedia.org/wiki/ISO_8583) on the whole specification.
## Usage
The library is available on nuget package. You can get it via:
```bash
dotnet add package NetCore8583
```
## Support
One can use the following channel to report a bug or discuss a feature or an enhancement:
- [Issue Tracker](https://github.com/Tochemey/NetCore8583/issues)
- [Discussions](https://github.com/Tochemey/NetCore8583/discussions)
If you find this library very useful in your day job, kindly show some love by starring it.
## How does NetCore8583 work?
NetCore8583 offers a [`MessageFactory`](./NetCore8583/MessageFactory.cs), which once properly configured, can create different message types with some values predefined, and can also parse a byte array to create an ISO message. Messages are represented by [`IsoMessage`](./NetCore8583/IsoMessage.cs) objects, which store [`IsoValue`](./NetCore8583/IsoValue.cs) instances for their data fields. You can work with the [`IsoValue`](./NetCore8583/IsoValue.cs) or use the convenience methods of [`IsoMessage`](./NetCore8583/IsoMessage.cs) to work directly with the stored values.
### MessageFactory and IsoMessage classes
These are the two main classes you need to use to work with ISO8583 messages. An [`IsoMessage`](./NetCore8583/IsoMessage.cs) can be encoded into a signed byte array. You can set and get the values for each field in an [`IsoMessage`](./NetCore8583/IsoMessage.cs), and it will adjust itself to use a secondary bitmap if necessary. An [`IsoMessage`](./NetCore8583/IsoMessage.cs) has settings to encode itself in binary or ASCII, to use a secondary bitmap even if it's not necessary, and it can have its own ISO header.
However, it can be cumbersome to programmatically create [`IsoMessage`](./NetCore8583/IsoMessage.cs) all the time. The MessageFactory is a big aid in creating [`IsoMessage`](./NetCore8583/IsoMessage.cs) with predefined values; also, it can set the date and the trace number in each new message.
* There is an extension method that helps switch between signed byte array and unsigned byte array.
#### How to configure the MessageFactory
There are five main things you need to configure in a [`MessageFactory`](./NetCore8583/MessageFactory.cs): ISO headers, message templates, parsing templates, TraceNumberGenerator, and custom field encoders.
* **Iso headers**: ISO headers are strings that are associated with a message type. Whenever you ask the message factory to create an [`IsoMessage`](./NetCore8583/IsoMessage.cs), it will pass the corresponding ISO header (if present) to the new message.
* **Message Templates**: A message template is an [`IsoMessage`](./NetCore8583/IsoMessage.cs) itself; the [`MessageFactory`](./NetCore8583/MessageFactory.cs) can have a template for each message type it needs to create. When it creates a message and it has a template for that message type, it copies the fields from the template to the new message before returning it.
* **Parsing Templates**: A parsing template is a map containing [`FieldParseInfo`](./NetCore8583/Parse/FieldParseInfo.cs) objects as values and the field numbers as the keys. A [`FieldParseInfo`](./NetCore8583/Parse/FieldParseInfo.cs) object contains an [`IsoType`](./NetCore8583/IsoType.cs) and an optional length; with this information and the field number, the [`MessageFactory`](./NetCore8583/MessageFactory.cs) can parse incoming messages, first analyzing the message type and then using the parsing template for that type; when parsing a message, the [`MessageFactory`](./NetCore8583/MessageFactory.cs) only parses the fields that are specified in the message's bitmap. For example if the bitmap specifies field 4, the factory will get the [`FieldParseInfo`](./NetCore8583/Parse/FieldParseInfo.cs) stored in the map under key 4, and will attempt to parse the field according to the type and length specified by the [`FieldParseInfo`](./NetCore8583/Parse/FieldParseInfo.cs).
A message does not need to contain all the fields specified in a parsing template, but a parsing template must contain all the fields specified in the bitmap of a message, or the MessageFactory won't be able to parse it because it has no way of knowing how it should parse that field (and also all subsequent fields).
* **ITraceNumberGenerator**: When creating new messages, they usually need to have a unique trace number, contained in field 11. Also, they usually need to have the date they were created (or the date the transaction was originated) in field 7. The [`MessageFactory`](./NetCore8583/MessageFactory.cs) can automatically set the current date on all new messages, you just need to set the assignDate property to true. And it can also assign a new trace number to each message it creates, but for this it needs a TraceNumberGenerator.
The [`ITraceNumberGenerator`](./NetCore8583/ITraceNumberGenerator.cs) interface defines a `nextTrace()` method, which must return a new trace number between 1 and 999999. It needs to be cyclic, so it returns 1 again after returning 999999. And usually, it needs to be thread-safe.
NetCore8583 only defines the interface; in production environments you will usually need to implement your own TraceNumberGenerator, getting the new trace number from a sequence in a database or some similar mechanism. As an example, the library includes the [`SimpleTraceGenerator`](./NetCore8583/Tracer/SimpleTraceGenerator.cs), which simply increments an in-memory value.
* **Custom fields encoders**: Certain implementations of ISO8583 specify fields which contain many subfields. If you only handle strings in those fields, you'll have to encode all those values before storing them in an [`IsoMessage`](./NetCore8583/IsoMessage.cs), and decode them when you get them from an IsoMessage.
In these cases you can implement a [`CustomField`](./NetCore8583/ICustomField.cs), which is an interface that defines two methods, one for encoding an object into a String and another for decoding an object from a String. You can pass the [`MessageFactory`](./NetCore8583/MessageFactory.cs) a [`CustomField`](./NetCore8583/ICustomField.cs) for every field where you want to store custom values, so that parsed messages will return the objects decoded by the [`CustomField`](./NetCore8583/ICustomField.cs) instead of just strings; and when you set a value in an [`IsoMessage`](./NetCore8583/IsoMessage.cs), you can specify the CustomField to be used to encode the value as a String
#### Custom Field encoders
Sometimes there are fields that contain several sub-fields or separate pieces of data. NetCore8583 will only parse the field for you, but you still have to parse those pieces of data from the field when you parse a message, and/or encode several pieces of data into a field when creating a message.
NetCore8583 can help with this process, by means of the custom field encoders. To use this feature, first you need to implement the ICustomField interface. You can see how it is done in the following test classes **_TestParsing.cs_** and **_TestIsoMessage.cs_** using the **_CustomField48.cs_** class.
### Easy way to configure ISO 8583 messages templates
The easiest way to configure the message templates and parsing templates is by using a XML config file and pass it to the [`MessageFactory`](./NetCore8583/MessageFactory.cs).
### XML configuration
The [`MessageFactory`](./NetCore8583/MessageFactory.cs) can read a XML file to setup message templates, ISO headers by type and parsing templates, which are the most cumbersome parts to configure programmatically.
There are three types of main elements that you need to specify in the config file: header, template, and parse. All these must be contained in a single `n8583-config` element.
#### Header
Specify a header element for every type of message that needs an ISO header. Only one per message type:
```xml
ISO015000050
ISO015000050
```
You can define a header as a reference to another header:
```xml
```
The header for 0800 messages will be the same as the header for 0200 messages.
#### Template Element
Each template element defines a message template, with the message type and the fields that the template should include. Every new message of that type that the [`MessageFactory`](./NetCore8583/MessageFactory.cs) creates will contain those same values, so this is very useful for defining fixed values, which will be the same in every message. Only one template per type.
```xml
650000
456
4591700012340000=
Fixed-width data
Life, the Universe, and Everything|42
840
B456PRO1+000
This field can have a value up to 999 characters long.
999
ABCD
```
You can define a template as extending another template, so that it includes all the fields from the referenced template as well as any new fields defined in it, as well as excluding fields from the referenced template:
```xml
Bla bla
```
In the above example, the template for message type 0400 will include all fields defined in the template for message type 0200 except field 102, and will additionally include field 90.
#### Parse Element
Each parse element defines a parsing template for a message type. It must include all the fields that an incoming message can contain, each field with its type and length (if needed). Only `ALPHA` and `NUMERIC` types need to have a length specified. The other types either have a fixed length, or have their length specified as part of the field (`LLVAR` and `LLLVAR`).
```xml
```
As with message templates, you can define parsing guides that extend other parsing guides:
```xml
```
#### Composite Fields
Another feature is the [`CompositeField`](./NetCore8583/Codecs/CompositeField.cs). This is a [`CustomField`](./NetCore8583/ICustomField.cs) that acts as a container for several [`IsoValue`](./NetCore8583/IsoValue.cs), and it can be configured in the parsing guide of a message type:
```xml
```
In the above example, when a message with type 0410 is parsed, the value for field 125 will be a [`CompositeField`](./NetCore8583/Codecs/CompositeField.cs) and you can obtain the subfields via **_GetField()_** or **_GetObjectValue()_**. The num attribute of the subfields is ignored.
This means that you can do this via code:
```c#
//Assuming original data for field 125 is "018one 03two123456OK"
CompositeField f = message.GetObjectValue(125);
string sub1 = (string)f.GetObjectValue(0); //"one "
string sub2 = (string)f.GetObjectValue(1); //"two"
string sub3 = (string)f.GetObjectValue(2); //"123456"
string sub4 = (string)f.GetObjectValue(3); //"OK"
```
You can also create a [`CompositeField`](./NetCore8583/Codecs/CompositeField.cs), store several subfields inside it, and store it in any field inside an [`IsoMessage`](./NetCore8583/IsoMessage.cs), specifying the same instance as the [`CustomField`](./NetCore8583/ICustomField.cs):
```c#
CompositeField f = new CompositeField().AddValue(new IsoValue(IsoType.ALPHA, "one", 5))
.AddValue(new IsoValue(IsoType.LLVAR, "two"))
.AddValue(new IsoValue(IsoType.NUMERIC, 123l, 6))
.AddValue(new IsoValue(IsoType.ALPHA, "OK", 2));
message.SetValue(125, f, f, IsoType.LLLVAR, 0);
```
When the message is encoded, field 125 will be "018one 03two000123OK".
## Resources
* [ISO 8583](http://en.wikipedia.org/wiki/ISO_8583)