Explore

Payment Extension : Improvement Plan

Overview :

Fynd Platform currently offers a set of payment gateways for processing payments to all merchants. If any merchant requires an additional payment integration for their checkout process - Fynd platform onboards PG developers to integrate the required payment gateway via extension. This process is also done by in-house developers for some extensions.

Payment extension is a middle layer between Fynd platform architecture and payment gateway which processes payments by managing communication between both the systems. Payment extensions are developed by Fynd Platform and PG developers by referring the extension

documentation⁠

. This documentation is the source of truth for all external developers for understanding current Fynd architecture and steps to be followed while developing the extension

Current Status :

Target audience : External developers [These developers can be either be experienced or freshers]

Process to develop and deploy an extension

Process to develop and deploy an extension

Step No.

Steps

Action

Problem

Solution

Priority

PG dev reads documentation to understand flow

Lack of information

Confusion

Improvised documentation with tutorial and step by step process

Video Tutorial

Bugs — Hyperlinks not working

Bad experience , brand value reduced

Immediate resolution

PG devs has doubts regarding payment flow

Increased SLA

There are no rows in this table

⁠

Process :

Merchant requests a PG support in Fynd Platform

Fynd Platform asks PG devs to integrate their PG with Fynd Platform

Requirements are communicated to PG devs via Fynd’s Product manager

PG devs refer extension documentation for development

PG devs reach out to PM for any doubts. PM arranges communication between them and Fynd PSE’s. If needed, devs are involved and doubts are solved over google meet

Depending on PG architecture, devs choose whether to use Fynd’s boilerplate/ build extension based on the framework of their choice

PG team may or may not share their code with Fynd team.

Once built, extensions are deployed via process preferred by PG team. The flow is tested by Fynd QA and PM.

Merchant installs and activates payment extension once live on production .

Problems faced by PG developers :

Lack of information :

Why is payment extension needed in Fynd Platform ? How is it integrated in Fynd platform

Difficulty in understanding the

steps for registration⁠

. Why are these required ? Where is it used in the boilerplate . Which FDK methods are these. Why are these used ? What is the existing flow for any PG integration with checkout flow.

⁠