OFS Message Parser

Why you need to parse OFS messages

When something goes wrong with a T24 integration — a payment is stuck, an account was not created, or a transaction failed — the first place to look is the OFS log. But raw OFS messages are hard to read. They look like a single line of comma-separated text with no obvious structure.

This parser takes that raw string and breaks it into its five parts: the application being called, the processing options, the user credentials, the record ID, and every data field with its multi-value position. It is designed for incident investigation, interface debugging, and learning how OFS messages work.

OFS message parsing example

Paste this OFS message into the parser to see how it decomposes:

FUNDS.TRANSFER,OFS/I/PROCESS,INPUTTER/COB/GB0010001,,,
DEBIT.ACCT.NO=100234,DEBIT.CURRENCY=GBP,
DEBIT.AMOUNT=5000,CREDIT.ACCT.NO=200567,
CREDIT.CURRENCY=GBP,CREDIT.AMOUNT=5000,
ORDERING.CUST=100100,
BENEFICIARY.CUST=100200,
PAYMENT.DETAILS=Test payment

The parser will show you the application (FUNDS.TRANSFER), the options (OFS/I/PROCESS), the user context, and each field individually — making it much easier to spot mistakes like a wrong field name or a missing comma.

Frequently asked questions

How do I read an OFS message in T24?

An OFS message is a comma-separated string with five parts: application, options, user credentials, record ID, and data fields. The parser above breaks each part into its own section so you can read it without counting commas. For a detailed explanation of the structure, see the OFS in T24 article.

Where do I find OFS messages in T24?

OFS messages appear in several places: the OFS.LOG file on the application server, the OFS.QUEUE enquiry in T24, integration log files from middleware, and the OFS.SOURCE configuration. When an integration fails, the log files contain the exact OFS message that was sent and the error response.

What does an OFS error look like?

An OFS error usually returns a message like OFS_CONN_ERR or a field-level error such as FIELD.NAME.UNKNOWN. The parser can help you identify which field caused the issue by showing the full structure of the sent message.