Data Converters

Format conversion and encoding utilities — Base64, Base94, BCD, character encoding, check digits and the Track 2 codec. Each one works in both directions, on the representations payment data actually arrives in.

Introduction

The converters live under Tools → Data Converters and handle format conversion and encoding: the representations payment data arrives in — Base64 on an API, BCD in an ISO 8583 field, packed hex in EMV tag 57 — and the check digits that guard them. Every tool is a two-direction pair: one card encodes, the other decodes.

The Data Converters hub with cards for the Base64 Encoder, Base94 Encoder, BCD Converter, Character Encoder, Check Digit calculator and Track 2 Codec — utility-tools Data Converters hub

All tools

Every converter in this category — each card links to the detailed reference below.

Base64 Encoder

Encode bytes to Base64 or decode a Base64 string back to hex.

View details →

Base94 Encoder

The denser printable-ASCII variant, encoded and decoded the same way.

View details →

BCD Converter

Pack a decimal string two digits per byte, or unpack one.

View details →

Character Encoder

Convert between binary, hexadecimal, decimal and ASCII.

View details →

Check Digit Calculator

Generate or validate a Luhn (Mod 10) check digit.

View details →

Track 2 Codec

Build Track 2 from its parts, or decode any of its three shapes.

View details →

Base64 Encoder

Base64 turns arbitrary bytes into a text-safe alphabet — the form payment data usually takes when it crosses a JSON or XML boundary. Encode and decode sit side by side.

Encode to Base64 form with an ASCII input encoding drop-down and an Input Data field above the Encode button — utility-tools Encode to Base64

Decode from Base64 form with a single Base64 Data field above the Decode button — utility-tools Decode from Base64

Inputs

Input Encoding — Drop-down: ASCII or hexadecimal. It tells the encoder how to read what you paste, so a hex key and a plain string both work.
Input Data — The bytes to encode, in the format above.
Base64 Data — On the decode side; the result comes back as hexadecimal.

Base94 Encoder

Base94 packs bytes into the full printable ASCII range, so it fits more data into the same number of characters than Base64. Some key-injection and terminal-management protocols use it for exactly that reason.

Encode to Base94 form with an ASCII input encoding drop-down and an Input Data field above the Encode button — utility-tools Encode to Base94

Decode from Base94 form with a single Base94 Data field above the Decode button — utility-tools Decode from Base94

The fields mirror the Base64 tool exactly — an Input Encoding drop-down and Input Data going in, Base94 Data coming back, decoded to hexadecimal.

BCD Converter

Binary Coded Decimal stores two digits per byte, which is how numeric ISO 8583 fields and EMV amounts are carried on the wire. The converter goes both ways between a decimal string and its packed form.

Encode to BCD form with a Decimal Data field holding 1234567890 above the Encode button — utility-tools Encode to BCD

Decode from BCD form with a Hexadecimal input format drop-down and a BCD Data field holding 1234567890 above the Decode button — utility-tools Decode from BCD

Inputs

Decimal Data — Digits to pack. An odd digit count is padded to a whole byte.
Input Format — On the decode side: Hexadecimal by default.
BCD Data — The packed value to unpack.

Character Encoder

A general conversion bench for the representations that are not a payment format in their own right — binary, hexadecimal, decimal and ASCII. One drop-down picks the direction.

Encoding Converter with a Conversion Type drop-down set to Binary to Hexadecimal and an Input Data field above the Convert button — utility-tools Encoding Converter

Inputs

Conversion Type — Drop-down naming both ends of the conversion, e.g. Binary -> Hexadecimal. Pick the pair and the tool applies it in that direction.
Input Data — The value in the source format.

Button: Convert.

Check Digit Calculator

The trailing digit on a PAN is a Luhn checksum, and a wrong one is rejected before any cryptography runs. This tool computes it, or checks the one you already have.

Inputs

Input Number — The digits to check. For validation, include the check digit; to generate one, leave it off.
Algorithm — Drop-down; Luhn (Mod 10) is the default and the one card numbers use.

Buttons: Validate, Generate.

Track 2 Codec

Track 2 is the magstripe-equivalent record that also travels in EMV tag 57, and it appears in at least three shapes depending on where you captured it. The codec builds one from its parts, or takes any of those shapes apart.

Encode

Inputs

PAN — 8–19 digits.
Expiry YYMM — 4 digits.
Service Code — 3 digits.
Discretionary Data — Digits; optional.
Output Format — Drop-down; BCD/Hex (EMV Tag 57) for chip data, or the ASCII magstripe forms.

Decode

Paste the record in any of its shapes — the tool detects which one it is rather than asking you. The form lists all three:

ASCII raw — with the ; start sentinel and ? end sentinel.
ASCII, no sentinels — PAN, =, then the rest.
BCD / hex (Tag 57) — packed, with D as the field separator and a trailing F pad.

Tips

When a field will not parse, check its representation before its value — a PAN that looks wrong is often BCD read as ASCII, or the other way round.
Round-trip anything you are unsure of: encode, then decode the result. If you do not land back on the input, the format assumption is what is wrong.
The Track 2 decoder accepts all three shapes, so paste a capture straight in rather than converting it by hand first.
The activity logs in each tool persist until you clear them — useful for capturing a sequence of intermediate values to share with a vendor support ticket.