System Integrator (SI) ToolkitSystem Integrator (SI) Toolkit
Introduction
Management
Business Operations
Technical Integration Guide
Deployment
Payment Manager User Guide
Technical Reference
Scheme Designs
Introduction
Management
Business Operations
Technical Integration Guide
Deployment
Payment Manager User Guide
Technical Reference
Scheme Designs
  • Introduction

    • System Integrator (SI) Toolkit
    • DFSP Onboarding Guide and Roadmap
    • Customer Journey
  • Management
  • Business Operations
  • Technical Integration Guide

    • Technical Integration
    • Inclusive Instant Payment System (IIPS) Integration
    • Development guide for building core-connectors
    • Core Connector Testing Harness
    • Core Connector Template
    • ISO20022 and Merchant Payments.
    • Fees
  • Deployment

    • Overview
    • Docker Compose

      • Payment Manager Deployment Guide
      • Core Connector Guide
      • Deploying Payment Manager
      • Configuring the core connectors
      • Connecting to a Hub
      • Securing the Docker Daemon
      • Firewall Configuration in Ubuntu and AWS EC2 (t2.large)
      • Test Transfer Process
  • Technical Reference

    • API Service
    • Routing and API Specifications
    • Networking
    • Core Banking Solution (CBS) Client
    • Mojaloop Connector Client (SDK Client)
    • Configuration.
    • Core Connector Aggregate (Business Logic)
    • Error Handling
    • Integration Accounts
    • Request Handling Lifecycle
  • Payment Manager User Guide

    • Payment Manager OSS
    • Transfers Overview Guide
    • FX Conversions Overview Guide
    • Technical Dashboard
  • Scheme Designs

    • Foreign Exchange - Currency Conversion
    • Interscheme

Fees

This section provides a detailed description of what fees can be charged and how these fees are executed and collected.

Fee types / categories

There are four categories of fees. This documentation describes in detail the transaction based fees, but it is important to understand that there are other types of fees that are not covered in this documentation.

  1. Transaction based fees (Participant Organisation Fees)
    These are per fees that are charged per transaction, and paid by the end consumer. All participant organisation can apply this fee. I.e. Payer DFSP, FXP and Payee DFSP.
    The Payee DFSP & FXP fees are included in the clearing amount of the transaction.
    I.e. They are pre-funded and settled during settlement.
  2. Non-transaction based fees
    E.g. DRPP Connection Fees: These fees are charged by the hub operator to Participant Organisations connecting to the DRPP. They are defined by the participant scheme agreement. No special mechanism is needed to invoice and settle these fees.
  3. Interchange Fees
    This is a mechanism where more elaborate per transaction fee can be applied by the hub.
  4. Fee commissions
    This is where a participant organisation involved in a transaction can choose to subsidise fees incurred by other participant organisation involved in a transaction.

Transaction Based Fees

These are Participant Organisation Fees. I.e. all Participants in a Transaction are able to add/include their fees at the time of the transaction. In order to describe in details, this document describe how the fee is applied and collected based on the participants role in the transaction. I.e. we will discuss how transaction fees are applied as:

  1. A Payer DFSP
  2. An FXP (Foreign Exchange Provider)
  3. A Payee DFSP

Fees charged to either the creditor or debtor

In the DRPP, two cross-border payment models are supported, each defining how the transaction amount and associated fees are calculated and charged:

  1. P2P “Send Money” Transfer
    The transfer amount is specified in the source currency, representing the amount debited from the sender’s account. In this model, the creditor (recipient) bears the transaction fees. Technically, this corresponds to the FSPIOP definition amountType = SEND and the ISO 20022 ChargeBearerType1Code = CRED (CdtTrfTxInf.ChrgBr = CRED).
  2. P2B “Merchant Payments”
    The payment amount is specified in the target currency, representing the amount credited to the payee’s account. In this model, the debtor (payer) bears the transaction fees, which are calculated and applied on top of the transfer amount. This aligns with the FSPIOP definition amountType = RECEIVE and the ISO 20022 ChargeBearerType1Code = DEBT (CdtTrfTxInf.ChrgBr = DEBT).

These models define not only the direction of value transfer but also how and where transaction fees are applied within the cross-border payment process.

Payer DFSP Transaction Fee

This fee is not included in the DRPP messaging, as it is expected to be managed outside of DRPP.

  1. P2P (peer-to-peer): Send Money
    Fees are deducted before.
    DRPP Send Money Amount = Amount - Fee
  2. P2B (peer-to-business): Merchant Payment
    Fee is added before presenting terms to customer.
    You will need to pay = DRPP Source Amount + Fee.

FXP Transaction Fee

Fees are included in the conversion terms; that are then presented to Payer DFSP, and the Payer. The fees are included in the clearing amount of the transaction. I.e. They are pre-funded and settled during settlement.

  1. P2P: Send Money
    Fees are included in the terms
    Target Currency Amount = Conversion Amount - Fee
  2. P2B: Merchant Payment
    Fees are included in the terms.
    Source Currency Amount = Conversion Amount + Fee

Payee DFSP Transaction Fee

Fees are included in the transfer terms; that are then presented to Payer DFSP, and the Payer. The fees are included in the clearing amount of the transaction. I.e. They are pre-funded and settled during settlement.

  1. P2P: Send Money & P2B: Merchant Payment
    Fees are included in the transfer terms
    Transfer amount = request amount + Fee

Scheme specified maximum fee

DRPP scheme has the objective of meeting the world bank and G20 targets to reduce cross border remittance fees to < 3% transferred amount.

Restriction of fees are placed on participant organisations. Details of which are included in the participant agreement and scheme rules of the scheme.

Next we will go through examples that shows detailed sequence diagrams to illustrate how are incorporated through participant integrations.

P2P: Send Money Fees Example

The transfer amount is specified in the source currency, representing the amount debited from the sender’s account. In this model, the creditor (recipient) bears the transaction fees. Technically, this corresponds to the FSPIOP definition amountType = SEND and the ISO 20022 ChargeBearerType1Code = CRED (CdtTrfTxInf.ChrgBr = CRED). Here is an end-to-end example of how fees are calculated for all participant organisations using a P2P or Send Money scenario.

P2P_Fees_Example The Payer initiates a transfer of 500 ZMW to the Payee. The Payer DFSP charges a 1% fee (5 ZMW), leaving 495 ZMW for conversion. The FXP converts the remaining 495 ZMW to MWK at an exchange rate of 75, resulting in 37,125 MWK. The FXP then deducts their 1% fee (371 MWK), leaving 36,754 MWK for the Payee DFSP. Finally, the Payee DFSP applies their 1% fee (367 MWK), and the Payee receives 36,387 MWK.

Let's examine the message sequences that illustrate how this example impacts the messages being transmitted.

P2P: Payer DFSP - Agreement of terms phase

  • Payer Sends 500 ZMW
  • Less Payer DFSP Fee of 5 ZMW
  • Payer DFSP sends 495 ZMW

P2P: Payer DFSP agreement

P2P: FXP - Agreement of terms phase

  • FXP convers 495 ZMW to 37125 MWK
  • Less FXP fee of 371 MWK
  • FXP Proposes to Send 36754 MWK

P2P: FXP agreement

P2P: Payee DFSP - Agreement of terms phase

  • Payee DFSP proposes to deposit 36387 MWK
  • After subtracting fee of 367 MWK
  • From Send amount of 36387 MWK

P2P: Payee DFSP agreement

P2P: Payer DFSP - Transfer phase

The transfer phase executes the agreement of terms. P2P: Payer DFSP transfer

P2P: FXP - Transfer phase

The transfer phase executes the agreement of terms. P2P: FXP transfer

P2P: Payee DFSP - Transfer phase

The transfer phase executes the agreement of terms. P2P: Payee DFSP transfer

P2B: Merchant Payment Fees Example

The payment amount is specified in the target currency, representing the amount credited to the payee’s account. In this model, the debtor (payer) bears the transaction fees, which are calculated and applied on top of the transfer amount. This aligns with the FSPIOP definition amountType = RECEIVE and the ISO 20022 ChargeBearerType1Code = DEBT (CdtTrfTxInf.ChrgBr = DEBT). Here is an end-to-end example of how fees are calculated for all participant organisations using a P2B or Merchant Payment scenario.

P2B_Fees_Example The Payer requests to pay the merchant 50,000 MWK (note that this amount is specified in the Payee's currency). The Payee DFSP charges a 1% fee (500 MWK), so the FXP needs to send 50,500 MWK. The FXP applies their 1% fee (505 MWK), requiring a total conversion amount of 51,005 MWK. At an exchange rate of 75, this translates to 680 ZMW needed to support the transfer. The Payer DFSP then adds their fee of 6 ZMW, meaning the Payer must pay 686 ZMW to complete this payment, while the Payee receives 50,000 MWK.

Let's examine the message sequences that illustrate how this example impacts the messages being transmitted.

P2B: Payee DFSP - Agreement of terms phase

  • Payee DFSP is asked to deposit 50000 MWK
  • Payee DFSP add their fee of 500 MWK
  • Payee DFSP specifies that they require receipt of 50500 MWK

P2B: Payee DFSP agreement

P2B: FXP - Agreement of terms phase

  • FXP need to convert to 50500 MWK
  • FXP fee of 505 MWK is first added
  • FXP Proposes to convert 680 ZMW to provide 51005 MWK to cover fees.

P2B: FXP agreement

P2B: Payer DFSP - Agreement of terms phase

  • Payer DFSP must send 680 ZMW
  • Payer DFSP add their fee of 6 ZMW
  • Payer must pay 686 ZMW

P2B: Payer DFSP agreement

P2B: Payer DFSP - Transfer phase

The transfer phase executes the agreement of terms. P2B: Payer DFSP transfer

P2B: FXP - Transfer phase

The transfer phase executes the agreement of terms. P2B: FXP transfer

P2B: Payee DFSP - Transfer phase

The transfer phase executes the agreement of terms. P2B: Payee DFSP transfer

Last Updated:
Contributors: Paul Baker
Prev
ISO20022 and Merchant Payments.