Scribd
Upload
36 views8 pages

Payment Link HLD

The document outlines the high-level design for a payment link generation solution that enables merchants to create unique payment URLs for customers, facilitating various payment methods including M-Pesa Wallets and bank transfers. It describes the application architecture, including components such as merchant and customer web interfaces, management services, and the payment flow process. The solution aims to provide a seamless, secure, and customizable payment experience for both merchants and customers across different markets.

Uploaded by

Jeremy Lantana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
36 views8 pages

Payment Link HLD

The document outlines the high-level design for a payment link generation solution that enables merchants to create unique payment URLs for customers, facilitating various payment methods including M-Pesa Wallets and bank transfers. It describes the application architecture, including components such as merchant and customer web interfaces, management services, and the payment flow process. The solution aims to provide a seamless, secure, and customizable payment experience for both merchants and customers across different markets.

Uploaded by

Jeremy Lantana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Payment Link

High Level Design

C2 . M-PESA Africa Internal


Contents
Contents ..................................................................................................................... 2
Overview ..................................................................................................................... 3
Solution Overview ........................................................................................................ 3
Application Architecture ............................................................................................... 4
Link generation and Payment Flows ............................................................................... 5
Link generation ......................................................................................................... 6
Payment ................................................................................................................... 7
API Specification .......................................................................................................... 8
References .................................................................................................................. 8

C2 . M-PESA Africa Internal


Overview
Payment link generation allows merchants to create a unique, shareable payment URL for
customers to complete payments seamlessly. This feature supports payments via M-Pesa
Wallets, local mobile wallets, bank transfers, and card payments. The link provides a
simple and secure way to collect payments from customers across different countries,
supporting cross-border transactions.

Solution Overview
The core capability that this solution will avail is giving internal and external partners the
relevant APIs that can be consumed to generate and send payment links (web URLs) to
their customers, who can subsequently use the links to complete a payment.

The diagram below gives a logical architecture for this solution:

The solution will be hosted in the M-PESA Hub where a suite of microservices will be
deployed to avail the required APIs and Web interfaces. Connectivity to the markets will be

C2 . M-PESA Africa Internal


established for market-bound traffic including G2 API calls, SMSC/notification requests
and USSD gateway requests.

Both PSPs/merchants and customers will have access to a web interface. PSPs and
merchants’ web interface will allow for customizations of look and feel of links they
generate, while customers will have a view of the payment summary as generated by a
given merchant and allow them to submit their MSISDN as part of confirmation.

Merchants and PSPs will have the option of integrating directly to the payment link APIs or
via OpenAPI

Application Architecture
The solution will comprise of the following components as illustrated above:

1. Merchant / PSP admin web UI – This will give merchants and PSPs the option of
customizing the look and feel of their payment links
2. Customer web UI – This will be the landing page for customers after clicking on a
payment link and will give a summary of the payment details and allow them to
submit their MSISDN to initiate the payment
3. Merchant management service – This will be a backend service for managing the list
of merchants using the solution
4. User management service – This will be a backend service for all users requiring log
in to the system (merchant / PSP admins)
5. Profile management service – This will be a backend service for persisting and
managing customizations made by PSPs and merchant admins on their payment
links’ look and feel
6. Notification management service – This service will manage how notifications are
sent to the customer including channel and content
7. Market management service – This service will manage the different market
configurations regarding how payment links are processed
8. Invoice management service – This service will manage how invoices are tied to
payment links and associated metadata
9. Partner management service – This service will be responsible for storing the list of
partners and their roles in the payment journey (e.g. IMT / FX / merchant aggregator
etc.)
10. Request / transaction management service – This will be a general-purpose service
for the end-to-end correlation of an API request from an internal or external system

C2 . M-PESA Africa Internal


11. Link management service – This will manage link generation and the end-to-end
lifecycle of the link up to expiry, cancellation or successful payment
12. Payment service – This will be the service responsible for making the necessary
payment requests to the market and capturing the results to be forwarded
accordingly

Link generation and Payment Flows


The diagram below shows how a typical customer journey will be supported by the
solution:

C2 . M-PESA Africa Internal


Link generation
1. A customer will visit an e-commerce website or application integrated to the
payment link solution and selects their preferred goods and services
2. Once ready to check out, they will have the option of sending themselves a payment
link as availed by the e-commerce website via the payment link integration
3. Upon selecting payment link and supplying their MSISDN on the e-commerce site,
an API call will be made (directly or via a PSP) to generate the payment link
4. The payment link solution will generate the unique link and send it as an SMS
notification to the provided MSISDN

C2 . M-PESA Africa Internal


5. The same link will be returned to the merchant or PSPs backend for any additional
business logic (e.g. sending the same via e-mail)

Payment
1. Once the customer clicks on the provided payment link, they will be directed to an
M-PESA-hosted web interface and for their specific pending payment (e.g. pay.m-
pesa.com/243-43KFD-RXP)
2. The payment link solution will validate the link information and retrieve the payment
details to be rendered on the web interface for the customer’s confirmation
3. Once the customer is satisfied with the payment details, they will input the MSISDN
to be used for payment and submit
4. An asynchronous API call will be made to the payment link solution to request for
payment fulfillment and the customer will be informed to wait for the PIN
confirmation
5. An API call will be made to the relevant market to process the payment
6. The market’s existing service will handle the PIN collection from the customer and
debiting on G2 and will notify the customer of the successful transaction
7. A callback request will be sent to the payment link solution with the results of the
transaction which will then be cascaded to the e-commerce site or PSP
8. The customer will then see the same results on the web interface confirming the
payment has been done

C2 . M-PESA Africa Internal


API Specification

References

C2 . M-PESA Africa Internal

You might also like