Payment Initiations

The initiation family: MT101 requests for transfer to and from pain.001 customer credit transfer initiations, the pain.001 version bridge, and spreadsheet payment files.

Formats

Format	What it is	Versions accepted	Emitted by default
`mt101`	Request for transfer	n/a	n/a
`pain.001`	Customer credit transfer initiation	`.001.03`, `.001.09` – `.001.12`	`.001.09` (`.001.03` on request)
`csv-payments` / `xlsx-payments`	Payment file as a CSV or Excel sheet (source only)	n/a	n/a

Pairs

From	To
`mt101`	`pain.001`
`pain.001`	`mt101`, `pain.001`
`csv-payments`, `xlsx-payments`	`mt101`, `pain.001`
`canonical`	`mt101`, `pain.001`

pain.001 → pain.001 is the version bridge: send a .001.03 file with targetVersion=pain.001.001.09 to upgrade it, or the reverse to downgrade. Spreadsheet files are never auto-detected, so from is required for them; their column options are covered in Formats.

Direct debits (MT104, pain.008) are a separate family: see Direct debits.

How fields map

The canonical model is an initiation with one or more batches (a debtor, its account and agent, an execution date) each holding instructions (one per creditor payment).

MT101 to pain.001.

:20: becomes the message id; :21R: the payment information id of every batch; :30: the requested execution date.
The ordering customer (:50F:, :50G:, :50H:) becomes the batch debtor and debtor account; :52A:/:52C: the debtor agent. :50C:/:50L: (the instructing party) becomes the initiating party.
Each transaction's :21: becomes both the instruction id and the end-to-end id; :32B: the instructed amount; :33B: and :36: the original amount and exchange rate; :21F: the FX deal reference.
:56a:/:57a: become the intermediary and creditor agent; :59a: the creditor and creditor account; :70: unstructured remittance; :77B: regulatory reporting; :25A: the charges account; :23E: instruction codes.
:71A: becomes the charge bearer: on the batch when every transaction agrees, otherwise per instruction.
A message with ordering customers in sequence B is split into one batch per distinct customer, account servicer and charge bearer.

pain.001 to MT101. One MT101 is written per distinct execution date, because :30: applies to the whole message. Within a message, the debtor and its agent go in sequence A when every batch shares them and into each transaction otherwise; :71A: is always written per transaction.

Where information is lost

Situation	Warning
pain.001 needs a creation time, an initiating party (the first debtor's name is used), a payment method (`TRF`) and a payment information id (`<MsgId>-<n>`) that MT101 does not carry	`MISSING_REQUIRED_DEFAULTED`
Several batches merged into one MT101 lose their own execution date, account, agent or id	`DROP_FIELD`
UETR, purpose code, creation time, batch booking flag: no MT101 field	`DROP_FIELD`
A debtor agent known only by name and address (MT101 has no option D there)	`DROP_AGENT`
References over 16 characters, names and addresses over four lines of 35	`TRUNC_REFERENCE`, `TRUNC_NAME`, `TRUNC_ADDRESS`
Remittance over four lines of 35	`TRUNC_REMITTANCE`
A charge bearer `SLEV` (no MT code); `:71A:SHA` is written	`CODE_UNMAPPED_PROPRIETARY`
`.001.03` target: UETR, a second service level, an execution time, or a BIC the older pattern rejects	`DROP_FIELD`
A spreadsheet column that matches no known header or `columnMap` entry	`COLUMN_UNMAPPED`

Conventions

No reference. :21: takes the end-to-end id, else the instruction id. A NOTPROVIDED id, or no id at all, is written as NONREF.
Errors, not guesses. A debtor without an account, an instruction without a creditor, or an execution date outside the MT date window is refused rather than invented.
Multi-message MT101. MT101 chains split with :28D: (1/3, 2/3, …) are joined into one initiation before conversion.
Standards Release. Under srVersion=SR2026, debtor, creditor and agent addresses are converted to the structured or hybrid form that release requires.

Example

curl -sS -X POST "https://api.transmute.403fin.io/v1/convert?to=pain.001" \
  -H "Authorization: Bearer $TRANSMUTE_KEY" \
  -H "Content-Type: text/plain" \
  --data-binary @- <<'MT'
:20:REQ-2026-0001
:28D:1/1
:50H:/DE89370400440532013000
JANE EXAMPLE
EXAMPLE STREET 1
60311 FRANKFURT
:30:260615
:21:TXN-0001
:32B:EUR1250,00
:59:/GB29NWBK60161331926819
ACME TOOLS LTD
1 TEST WAY
LONDON
:71A:SHA
MT

The result document, formatted:

<GrpHdr>
  <MsgId>REQ-2026-0001</MsgId>
  <NbOfTxs>1</NbOfTxs>
  <InitgPty><Nm>JANE EXAMPLE</Nm></InitgPty>
</GrpHdr>
<PmtInf>
  <PmtInfId>REQ-2026-0001-1</PmtInfId>
  <PmtMtd>TRF</PmtMtd>
  <ReqdExctnDt><Dt>2026-06-15</Dt></ReqdExctnDt>
  <Dbtr><Nm>JANE EXAMPLE</Nm>...</Dbtr>
  <DbtrAcct><Id><IBAN>DE89370400440532013000</IBAN></Id></DbtrAcct>
  <ChrgBr>SHAR</ChrgBr>
  <CdtTrfTxInf>
    <PmtId><InstrId>TXN-0001</InstrId><EndToEndId>TXN-0001</EndToEndId></PmtId>
    <Amt><InstdAmt Ccy="EUR">1250.00</InstdAmt></Amt>
    <Cdtr><Nm>ACME TOOLS LTD</Nm>...</Cdtr>
    <CdtrAcct><Id><IBAN>GB29NWBK60161331926819</IBAN></Id></CdtrAcct>
  </CdtTrfTxInf>
</PmtInf>

The response carries four MISSING_REQUIRED_DEFAULTED (info) warnings, for GrpHdr/CreDtTm, GrpHdr/InitgPty, PmtInf/PmtMtd and PmtInf/PmtInfId, and meta.targetType is pain.001.001.09.

Was this page helpful?