Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Review Mastercard’s Cross-Border Payment Solution:

\uD83D\uDDE3 Discussion topics

Item

Presenter

Notes

Mastercard’s Cross-Border Payment Solution

Florian Greunz

  • Florian Greunz from Mastercard presented Mastercard’s cross-border payment solution, highlighting the challenges with the current correspondent banking model.

  • The pain points identified were high costs, slow transaction times, lack of transparency, and inconsistency.

  • Mastercard's solution leverages their global network of payment partners to facilitate faster, more transparent, and efficient cross-border payments.

  • Mastercard’s solution can reach various endpoints, including cards, bank accounts, mobile wallets, and cash pickup locations.

  • Mastercard's solution can cover three types of government disbursement use cases:

    • Government to Business (G2B): International humanitarian aid, financial aid payments to NGOs abroad.

    • Government to Person (G2P): International pension payments.

    • Government to Government (G2G): Crisis support payments.

  • The benefits of Mastercard's solution include faster payments, real-time transparency, clear fee structures, and diverse payout options

Mastercard’s Cross-Border Payment Solution as a use case for Payments BB


Florian, David Higgins Mauree, Venkatesen

  1. The discussion focused on how Mastercard's solution could integrate with the payment building block.

  2. Two potential models were discussed:

    1. The bank acts as the intermediary between the government and Mastercard Cross-Border Services.

    2. The payment building block acts as the intermediary, integrating Mastercard's APIs and forwarding payment instructions.

  3. The second model, where the payment building block acts as the intermediary, resonated more with the group.

  4. David Higgins suggested that Mastercard Cross-Border Services could be treated as another bank within the payment building block.

  5. The group agreed that a decision mechanism within the payment building block would be needed to determine the optimal route for each payment.

  6. Florian clarified that Mastercard's solution is complementary and does not aim to replace existing networks.

  7. Florian will prepare a flow diagram illustrating the information exchange between the government, the payment building block, and Mastercard Cross-Border Services.

✅ Action items

  1. The group will review the flow diagram and discuss the API integration with the existing payment infrastructure.

  2. Florian: Prepare a flow diagram illustrating the information exchange and payment flows:

  3. Payments BB: Review Florian's flow diagram and provide feedback.

  4. David Higgins Discuss the API integration and connector layer for the Mastercard solution.

  5. The next meeting is tentatively scheduled for August 13th at 4:00 PM Geneva time.

  6. Mastercard to document the Cross-Border Payment Solution use case based on the <Use Case Template> - Development (gitbook.com) and share the draft ahead of the next meeting.

  7. Mastercard to include in the draft use case document the functional requirements required by the payments BB to do the Cross Border Payments using the example 6 Functional Requirements | bb-payments (gitbook.io)

⤴ Decisions

  • The group agreed to explore the model where the payment building block acts as the intermediary between the government and Mastercard Cross-Border Services.
  • A decision mechanism will be implemented within the payment building block to determine the optimal payment route.
  • No labels