MTD-STD-04 · Transfers of Funds and Crypto-Assets Standard (v3.2)
The registry entry for this document — where it came from, what it says, and which
assessments its passages are filed to.
Active
Internal
v1
mtd-std-04-transfers-standard.md
5585 bytes · owner Head of Financial Crimeas at 2026-03-19 (approval date)
Identity, integrity & provenance
bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65Allocated to assessments
Where this document's content was filed at triage — 6 sections. A section can be allocated to more than one assessment. Change it with Triage and allocate, in the actions at the top of this page.
1.1 This Standard applies to every transfer of funds and every transfer of crypto-assets that Mittenda executes or receives, and to every transfer in which it acts as an intermediary payment service provider or an intermediary crypto-asset service provider.
1.2 It gives effect to Chapters II and III of Regulation (EU) 2023/1113 and has regard to the travel rule guidelines, EBA/GL/2024/11.
Sets the scope of Mittenda Limited's own standard for the transfers it executes, receives or intermediates under Regulation (EU) 2023/1113; Mittenda Limited owns and operates it as PSP/IPSP/CASP/ICASP.
2.1 Mittenda's role in the chain is determined for each transfer, and the duties of that role are applied.
2.2 For transfers of funds, the roles are those of Chapter II of Regulation (EU) 2023/1113: payment service provider of the payer, payment service provider of the payee, and intermediary payment service provider. For transfers of crypto-assets, the roles are those of Chapter III: crypto-asset service provider of the originator, of the beneficiary, and intermediary crypto-asset service provider.
2.3 In this Standard, for transfers of funds, 'originator' and 'beneficiary' mean the payer and the payee.
Describes how Mittenda Limited determines its own role per transfer and applies that role's duties; the activity is performed by Mittenda Limited, the only assessed unit.
3.1 Every transfer of funds is accompanied by information on the originator: the name; the payment account number; the address, including the name of the country, official personal document number and customer identification number or, alternatively, the date and place of birth; and, where the message format allows, the current legal entity identifier or an equivalent official identifier. The transfer is also accompanied by the beneficiary's name, payment account number and, where the format allows, legal entity identifier.
3.2 Where every payment service provider in the chain is established in the Union, the transfer is accompanied by at least the payment account numbers of the originator and the beneficiary. The full information in §3.1 is made available to the payment service provider of the payee or an intermediary payment service provider within three working days of a request.
3.3 A batch file of transfers from a single originator may carry the information in §3.1 on the batch file rather than on each transfer, provided the batch file carries it in full and each individual transfer carries the originator's payment account number.
3.4 Where a payment service provider in the chain is established outside the Union, a transfer of funds not exceeding EUR 1,000 that does not appear linked to other transfers together exceeding that amount may be accompanied by only the names and payment account numbers of the originator and the beneficiary.
Sets the originator and beneficiary information Mittenda Limited attaches to transfers of funds, including intra-Union, batch and low-value third-country variants; Mittenda Limited performs these duties as PSP of the payer.
3.5 Where the identity of the originator has been verified in accordance with the AML/CTF Policy §6 and the Customer Due Diligence Standard §4, the accuracy of the information required by this Standard is deemed to have been verified, in accordance with Article 4(5) and Article 14(7) of Regulation (EU) 2023/1113.
States how Mittenda Limited treats verification of originator information accuracy for its own transfers, relying on its CDD; Mittenda Limited owns this verification approach.
4.1 Incoming transfers are monitored for missing or incomplete information in accordance with risk-based procedures, and transfers from counterparties that repeatedly fail to provide required information are escalated to the Head of Financial Crime.
4.2 Detection procedures identify incoming transfers whose required fields are missing, incomplete, or completed with characters or inputs that do not conform to the conventions of the relevant messaging scheme.
Describes Mittenda Limited's own monitoring and detection of missing or incomplete information on incoming transfers and escalation of repeatedly failing counterparties; Mittenda Limited performs this as PSP/CASP of the payee/beneficiary and as intermediary.
6.1 Every transfer of crypto-assets is accompanied by information on the originator: the name; the distributed ledger address or crypto-asset account number; the address, including the name of the country, official personal document number and customer identification number or, alternatively, the date and place of birth; and, where the message format allows, the current legal entity identifier or an equivalent official identifier. The transfer is also accompanied by the beneficiary's name and distributed ledger address or crypto-asset account number.
6.2 These requirements apply to every transfer of crypto-assets regardless of value: no de-minimis threshold applies.
6.3 For a transfer of more than EUR 1,000 to or from a self-hosted address, whether the address is owned or controlled by Mittenda's customer is verified.
Sets the information Mittenda Limited attaches to crypto-asset transfers and its self-hosted address verification; Mittenda Limited performs these duties in its CASP role.
Not allocated
Text no triage section covers — 8 passages. Often this is the title, document-control metadata or sign-off; if any of it belongs to an assessment, file it with Triage and allocate, in the actions at the top of this page.
# Mittenda Limited · Transfers of Funds and Crypto-Assets Standard (v
) · specimen excerpt > **Synthetic specimen.** Mittenda Limited is a fictional firm. This document is invented, > derived from scenarios seen in practice, and contains deliberate deficiencies for > demonstration. It is not a template and must not be adopted. **Document control:**
. | Version | Date | Change | |---|---|---| |
| March 2026 | Guidance references updated | | 3.1 | April 2025 | Crypto-asset transfer requirements (§6) added | | 3.0 | December 2024 | Reissued for the application of Regulation (EU) 2023/1113; renamed from the Financial Crime Standard; monitoring and screening moved to dedicated Standards | *[Earlier versions omitted]* **Contents** 1. **Purpose and scope** 2. **Role determination** 3. **Information requirements** 4. **Incoming transfers and counterparty management** 5. Intermediary duties 6. **Crypto-asset transfer requirements** Appendix A: Required information by role and rail *Sections in bold are excerpted below.* ## 1. Purpose and scope
## 2. Role determination
## 3. Information requirements
## 4. Incoming transfers and counterparty management
*[Section 5 omitted]* ## 6. Crypto-asset transfer requirements
Document text
Mittenda Limited · Transfers of Funds and Crypto-Assets Standard (v3.2) · specimen excerpt
Synthetic specimen. Mittenda Limited is a fictional firm. This document is invented, derived from scenarios seen in practice, and contains deliberate deficiencies for demonstration. It is not a template and must not be adopted.
Document control: MTD-STD-04 · owner: Head of Financial Crime · approved: Risk and Compliance Committee, 19 March 2026 · classification: Internal · next review due: March 2027.
| Version | Date | Change |
|---|---|---|
| 3.2 | March 2026 | Guidance references updated |
| 3.1 | April 2025 | Crypto-asset transfer requirements (§6) added |
| 3.0 | December 2024 | Reissued for the application of Regulation (EU) 2023/1113; renamed from the Financial Crime Standard; monitoring and screening moved to dedicated Standards |
[Earlier versions omitted]
Contents
- Purpose and scope
- Role determination
- Information requirements
- Incoming transfers and counterparty management
- Intermediary duties
- Crypto-asset transfer requirements
Appendix A: Required information by role and rail
Sections in bold are excerpted below.
1. Purpose and scope
1.1 This Standard applies to every transfer of funds and every transfer of crypto-assets that Mittenda executes or receives, and to every transfer in which it acts as an intermediary payment service provider or an intermediary crypto-asset service provider.
1.2 It gives effect to Chapters II and III of Regulation (EU) 2023/1113 and has regard to the travel rule guidelines, EBA/GL/2024/11.
2. Role determination
2.1 Mittenda's role in the chain is determined for each transfer, and the duties of that role are applied.
2.2 For transfers of funds, the roles are those of Chapter II of Regulation (EU) 2023/1113: payment service provider of the payer, payment service provider of the payee, and intermediary payment service provider. For transfers of crypto-assets, the roles are those of Chapter III: crypto-asset service provider of the originator, of the beneficiary, and intermediary crypto-asset service provider.
2.3 In this Standard, for transfers of funds, 'originator' and 'beneficiary' mean the payer and the payee.
3. Information requirements
3.1 Every transfer of funds is accompanied by information on the originator: the name; the payment account number; the address, including the name of the country, official personal document number and customer identification number or, alternatively, the date and place of birth; and, where the message format allows, the current legal entity identifier or an equivalent official identifier. The transfer is also accompanied by the beneficiary's name, payment account number and, where the format allows, legal entity identifier.
3.2 Where every payment service provider in the chain is established in the Union, the transfer is accompanied by at least the payment account numbers of the originator and the beneficiary. The full information in §3.1 is made available to the payment service provider of the payee or an intermediary payment service provider within three working days of a request.
3.3 A batch file of transfers from a single originator may carry the information in §3.1 on the batch file rather than on each transfer, provided the batch file carries it in full and each individual transfer carries the originator's payment account number.
3.4 Where a payment service provider in the chain is established outside the Union, a transfer of funds not exceeding EUR 1,000 that does not appear linked to other transfers together exceeding that amount may be accompanied by only the names and payment account numbers of the originator and the beneficiary.
3.5 Where the identity of the originator has been verified in accordance with the AML/CTF Policy §6 and the Customer Due Diligence Standard §4, the accuracy of the information required by this Standard is deemed to have been verified, in accordance with Article 4(5) and Article 14(7) of Regulation (EU) 2023/1113.
4. Incoming transfers and counterparty management
4.1 Incoming transfers are monitored for missing or incomplete information in accordance with risk-based procedures, and transfers from counterparties that repeatedly fail to provide required information are escalated to the Head of Financial Crime.
4.2 Detection procedures identify incoming transfers whose required fields are missing, incomplete, or completed with characters or inputs that do not conform to the conventions of the relevant messaging scheme.
[Section 5 omitted]
6. Crypto-asset transfer requirements
6.1 Every transfer of crypto-assets is accompanied by information on the originator: the name; the distributed ledger address or crypto-asset account number; the address, including the name of the country, official personal document number and customer identification number or, alternatively, the date and place of birth; and, where the message format allows, the current legal entity identifier or an equivalent official identifier. The transfer is also accompanied by the beneficiary's name and distributed ledger address or crypto-asset account number.
6.2 These requirements apply to every transfer of crypto-assets regardless of value: no de-minimis threshold applies.
6.3 For a transfer of more than EUR 1,000 to or from a self-hosted address, whether the address is owned or controlled by Mittenda's customer is verified.
[Appendix A omitted]
What it evidences
| Cited by | Suggestion | Version | When |
|---|---|---|---|
| Mittenda Limited | Risk examination Documented, not evidenced — Originator information verification not validly performed before transfer sg-0392 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 21:50 |
| Mittenda Limited | Coverage Not evidenced — Failed verification outcome blocks dispatch sg-0390 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
| Mittenda Limited | Coverage Not evidenced — Joint-holder beneficiary name-set coverage pre-check sg-0391 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
| Mittenda Limited | Coverage Not evidenced — On-demand retrieval index for originator KYC information sg-0386 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
| Mittenda Limited | Coverage Not evidenced — Routing of information-on-request to response team sg-0385 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
| Mittenda Limited | Coverage Not evidenced — Information-on-request intake recognition classifier sg-0384 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
| Mittenda Limited | Coverage Not evidenced — Pre-crediting beneficiary-verification gate sg-0381 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
| Mittenda Limited | Coverage Not evidenced — Accompaniment incident and metrics monitoring sg-0379 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
| Mittenda Limited | Coverage Not evidenced — Dedicated intake channel for information-on-request sg-0380 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
| Mittenda Limited | Coverage Not evidenced — Outsourced incoming-processing detection clauses sg-0378 | current — v1sha256 bd118bf9f7b0f1b3323af24e10448ac3ad3ac5efd08d0a9acc1952d6c84b3a65 |
2026-10-04 20:13 |
Assistant findings
267 grounded in this documentWhat the assistant surfaced from this document — accept or reject them on the findings and coverage page.
| Finding | Value | Confidence | Status |
|---|---|---|---|
| Originator information accompanying transfers of funds sg-0001 | Partial | Medium | Accepted |
| Beneficiary information accompanying transfers of funds sg-0002 | Partial | Medium | Accepted |
| Head of Financial Crime (MLRO) sg-0004 | Head of Financial Crime (MLRO) | High | Accepted |
| Risk and Compliance Committee sg-0006 | Risk and Compliance Committee (group) | High | Accepted |
| Account numbers only for fully intra-Union transfers sg-0007 | Partial | Medium | Accepted |
| Omitted originator information supplied within three working days on request sg-0012 | Partial | Medium | Accepted |
| Single-originator batch derogation for transfers outside the Union sg-0029 | Partial | Medium | Accepted |
| Minimum information for low-value transfers outside the Union sg-0044 | Partial | Medium | Accepted |
| Verification of originator information against a reliable source before transfer sg-0058 | Not evidenced | Medium | Accepted |
| When originator information verification is deemed to have occurred sg-0075 | Not evidenced | Medium | Accepted |
Audit timeline
Every event on this document (283)
| When (UTC) | Actor | What | Change |
|---|---|---|---|
| 2026-10-06 13:38:08 | Demo User | Document viewed | "MTD-STD-04 · Transfers of Funds and Crypto-Assets Standard (v3.2)" opened on the register detail. |
| 2026-10-06 13:38:08 | Demo User | Document content_accessed | Content read by a Restricted clearance (document Internal). |
| 2026-10-06 10:10:59 | Demo User | Document viewed | "MTD-STD-04 · Transfers of Funds and Crypto-Assets Standard (v3.2)" opened on the register detail. |
| 2026-10-06 10:10:59 | Demo User | Document content_accessed | Content read by a Restricted clearance (document Internal). |
| 2026-10-06 10:05:31 | Demo User | Document viewed | "MTD-STD-04 · Transfers of Funds and Crypto-Assets Standard (v3.2)" opened on the register detail. |
| 2026-10-06 10:05:31 | Demo User | Document content_accessed | Content read by a Restricted clearance (document Internal). |
| 2026-10-06 08:53:40 | Demo User | Document viewed | "MTD-STD-04 · Transfers of Funds and Crypto-Assets Standard (v3.2)" opened on the register detail. |
| 2026-10-06 08:53:40 | Demo User | Document content_accessed | Content read by a Restricted clearance (document Internal). |
| 2026-10-05 10:22:14 | Demo User | Document viewed | "MTD-STD-04 · Transfers of Funds and Crypto-Assets Standard (v3.2)" opened on the register detail. |
| 2026-10-05 10:22:14 | Demo User | Document content_accessed | Content read by a Restricted clearance (document Internal). |
| 2026-10-04 21:50:24 | Demo User | Document cited | Cited by an accepted suggestion. |
| 2026-10-04 20:13:07 | Demo User | Document cited | Cited by an accepted suggestion. |
| 2026-10-04 20:13:07 | Demo User | Document cited | Cited by an accepted suggestion. |
| 2026-10-04 20:13:07 | Demo User | Document cited | Cited by an accepted suggestion. |
| 2026-10-04 20:13:07 | Demo User | Document cited | Cited by an accepted suggestion. |
15 of 283 shown
| |||