TL;DR
What Is the Ultimate Remitter
To understand the global payment landscape in 2026, we need to start with the terminology of the ISO 20022 standard. There is a common misconception that the person who holds the bank account is always the remitter. In modern fintech structures, this is rarely the case. We need to distinguish between three distinct roles: the debtor, the debtor agent, and the ultimate debtor or remitter.
The debtor is the account holder who sends the payment instruction to their bank. The debtor agent is the bank itself. The ultimate debtor or remitter is the person or business whose money it actually is.
Consider a simple example. A fintech company sends a payout from its own corporate bank account on behalf of a marketplace seller. In this scenario, the fintech is the debtor. The marketplace seller is the ultimate remitter.
The SWIFT CBPR+ market practice documents emphasize that these distinctions are vital for automated processing. When a payment message moves through the correspondent banking network, every bank in the chain needs to know who is really behind the money to perform accurate risk assessments.
Why It Matters Now
Three major forces are making the identification of the ultimate remitter an urgent priority in 2026.
First, the migration to ISO 20022 has reached its final stages. This migration makes payment data richer and more structured, which means banks can now see and expect specific ultimate party fields. The BIS report on ISO 20022 harmonisation notes that structured data is the foundation of faster cross-border settlement.
Second, the FSB G20 Roadmap for Enhancing Cross-Border Payments has set strict targets for transparency and speed. Regulators are pushing for a system where no payment is a black box. The FSB progress report makes clear that transparency improvements are a priority area where the industry can deliver near-term progress. The McKinsey Global Payments Report highlights that payment transparency is no longer a luxury but a regulatory mandate.
Third, correspondent banks have lost their patience with poor data quality. Banks are increasingly rejecting or flagging payments where ultimate party information is missing or inconsistent. The practical consequences are severe: payment delays, returned funds, and frozen accounts. In some cases, a single missing address field for an ultimate remitter can cause a payment to be held for weeks of manual review.
How It Affects Fintechs, Platforms, and Marketplaces
If you are a fintech, marketplace, or platform making payments on behalf of your customers, you are operating in an on-behalf-of model. This means your corporate bank account is the source of funds, but the underlying party is your customer (a seller, merchant, freelancer, or supplier).
Regulators and correspondent banks want to see both. They want to know who holds the account (the debtor) and who the money is actually from (the ultimate remitter). This is not optional anymore. The SWIFT market practice guidelines explicitly state that on-behalf-of structures are a valid scenario for populating ultimate party fields, with the company being captured as the debtor and the underlying customer being populated as the ultimate debtor.
The practical consequence is clear. If you run an on-behalf-of structure and do not correctly populate ultimate remitter fields, your payments are more likely to be delayed, returned, or rejected. Correspondent banks may also ask your banking partner questions about the nature of the relationship, which can lead to account reviews or restrictions if the data is not clean.
How to Get It Right
There are four things every business operating in an on-behalf-of model should do.
1. Confirm your payment provider supports ISO 20022 ultimate party fields. Not all providers populate these fields, even if they support ISO 20022 message formats. Ask specifically whether your provider transmits ultimate debtor and ultimate creditor information to the correspondent banking chain.
2. Map your internal data to payment message fields. For every outbound payment, you should be able to pass the ultimate remitter's name, address, and an account or transaction reference to your payment provider. This requires your internal systems to link each payout to the underlying customer record.
3. Align ultimate remitter identification with your KYC records. The information you provide as the ultimate remitter should match the KYC data you have on file for that customer. Inconsistencies between payment message data and KYC records create compliance risk.
4. Test with your banking partners. Some banks in the correspondent chain truncate or drop optional fields during message processing. Run test payments and verify that the ultimate party information reaches the beneficiary bank intact. If it does not, work with your provider to find an alternative routing.
How Tazapay Handles This
Tazapay operates as a licensed payment infrastructure provider with on-behalf-of capabilities across 170+ markets. When fintechs and platforms use Tazapay for payouts, ultimate party information is captured during onboarding and passed through in payment messages that meet ISO 20022 and CBPR+ standards.
This means the fintech does not need to manage the complexities of payment message formatting, ultimate party field population, or correspondent bank requirements internally. Tazapay's infrastructure handles it as part of the payout flow.
For a deeper look at how on-behalf-of payment structures work, see our guide on on-behalf-of payment infrastructure.
Sources: SWIFT CBPR+ Market Practice Guidelines | BIS: Enhancing Cross-Border Payments | FSB G20 Roadmap Progress Report | McKinsey Global Payments Report
