A cover payment is a bank-to-bank transfer that provides, or "covers", the funds for a customer payment whose instruction has been sent separately. In the cover method, the sending bank sends the customer credit transfer message straight to the beneficiary's bank, so the beneficiary's bank knows a payment is coming, and at the same time sends a second message instructing its own correspondent to move the money through the correspondent chain to the beneficiary's bank's account. When the cover arrives, the beneficiary's bank can credit its customer.
The method is an alternative to the serial method, in which a single customer message travels through each bank along with the funds. Both are used in correspondent payments, and the choice affects speed, cost and the information that intermediaries see. Cover payments are governed by message standards set by SWIFT and by international rules on payment transparency, including the FATF requirements known as the travel rule.
How the cover method works
Consider a bank in Singapore sending US dollars for a customer to a supplier whose account is at a bank in Brazil. The two banks do not hold accounts with each other, but each has a US dollar nostro account with a correspondent in New York.
- The Singapore bank sends the customer credit transfer, historically a SWIFT MT103 and now an ISO 20022 pacs.008, directly to the Brazilian bank, naming the New York correspondents in the settlement details.
- It sends a separate financial institution transfer to its own New York correspondent, asking it to pay the Brazilian bank's correspondent.
- The New York banks settle between themselves, typically through CHIPS or Fedwire.
- The Brazilian bank's correspondent credits its account and notifies it, and the Brazilian bank matches the funds with the instruction it already holds and credits the supplier.
Because the instruction and the funds travel separately, the beneficiary's bank must reconcile them, and it may wait for the cover to arrive before crediting the customer.
MT202 COV and pacs.009 COV
Before 2009, cover transfers were sent as ordinary bank-to-bank messages, the MT202, which carried only the names of the banks. Intermediary correspondents could not see who was paying whom, which made it impossible for them to screen the underlying customers for sanctions and money laundering risk. Investigations into banks that removed or hid customer details in payments, a practice sometimes called stripping, showed how this gap could be exploited.
In response, SWIFT introduced the MT202 COV message in November 2009. It contains the bank-to-bank details and, in a separate sequence, the originator and beneficiary information copied from the underlying customer payment. Correspondents became required in practice to screen this information. The Basel Committee published guidance on due diligence and transparency for cover payments in the same year. In ISO 20022, the equivalent is the pacs.009 message in its cover variant, often called pacs.009 COV, which carries the underlying customer credit transfer details in structured form.
Serial versus cover
| Feature | Serial method | Cover method |
|---|---|---|
| Messages | One customer message passed along the chain | Customer message direct to beneficiary bank plus a separate cover message |
| Information at intermediaries | Full customer details | Customer details only in the COV sequence |
| Speed of notice to beneficiary bank | On arrival of funds | Early, before funds arrive |
| Reconciliation | Simple | Instruction and funds must be matched |
Risks and compliance points
Cover payments raise several risks. The beneficiary's bank may credit its customer before the cover arrives, taking a credit risk if the funds never come. Mismatches between the customer message and the cover can lead to delays and investigations. Intermediaries depend on the sending bank to copy the customer information accurately, so incomplete or inconsistent data must be followed up. Banks apply sanctions screening and transaction monitoring to the COV information as they would to a serial payment, and supervisors check that banks do not use cover payments to avoid transparency obligations.
Role in modern cross-border payments
The cover method remains common for high-value and treasury flows and for banks with many direct relationships, because it gives the beneficiary's bank early notice of incoming funds. Tracking services such as SWIFT gpi link the customer message and the cover through a shared end-to-end reference, which makes matching and tracing easier. Charges deducted along the cover route, such as an intermediary bank fee, are handled according to the charge option chosen by the sender. Richer data in ISO 20022 messages is expected to reduce manual repairs and investigations, which have long been a source of delay in cover payments.