1. Executive Summary
FPL Technologies is one of the fastest-growing tech-driven outsourced service providers that offers innovative solutions to businesses and organizations of all sizes.
FPL Technologies operates both the OneCard and OneScore brands that deal with metal cards and a consumer’s Credit Score respectively.
This document details the scope of the engagement between FPL and Karix for SMS, WhatsApp, and RCS services.
2. Problem Statement
FPL team is currently using an internal tool through which extracting the PII is not possible and additional the tool does not support API integration.
Hence they would like to integrate with Karix using FTP provided by FPL Technologies.
3. Requirement Type – Implementation of Existing Feature
FPL Technologies agrees to use the existing FTP automation which Karix offers. Any new enhancements may be taken up separately.
3.1. Requirement Overview
• Karix to deploy standard FTP configurations for each of the following channels on FPL FTP:
o SMS
o WhatsApp
o RCS
• Provide MIS back in FTP reports folders
3.2. Logical Flow of Requirement
3.3. Business Process
a)
FPL Tech to provide an FTP to Karix with three channel-wise folders (refer Image 1):
a.
SMS
b.
c.
RCS
b)
Each sub-folder to have the following structure:
a.
IN – for Input files
b.
REPORT – for Output files
c.
ERROR – for error rows
d.
PROCESSED – for processed files
c)
FPL to place Input file as per agreed format, naming, and file extension in the IN folder along with .done file of same name.
d)
Karix will pick up and process the file as per applied validations.
a.
On successful execution, file will be placed in PROCESS folder
b.
If any row has missing mandatory columns, that row will be moved
c.
Report will be placed next day in the REPORT folder.
3.4. FTP Notes
a)
FTP sub-folder for a channel (eg: SMS/WA/RCS) will be bound to one acode for a specific channel at a time only.
b)
.done file is mandatory.
c)
For SMS, file structure may be whitelisted only once.
d)
For Rich channels (RCS and WhatsApp) each new template ID must be whitelisted by FPL tech with the provisioning team.
e)
Template approval/whitelisting process remains as is.
f)
If there are any media attachments like video or images, FPL tech team must pass a publicly hosted URL of the media in the input file.
g)
For WhatsApp, the sender ID can either be :
a.
in the name of file - eg: WABA-sfmc_karix_tsq_auto-0001_regular_anniversary_wa_22102023_video_7823232323_0.csv]
b.
as a column, with Sender ID mentioned for each row - WABA-sfmc_karix_tsq_auto-0002_t-0_regular_anniversary_wa_22102023_video_1.csv
3.5. Assumptions and Dependencies
a)
FTP to be provided by FPL Tech.
b)
Filename for each channel must be confirmed. FPL Tech to also confirm if any specific validations are to be applied:
a.
Naming of the file.
b.
Date Time validation. Eg: if date is mentioned in file name it should get executed on same day only.
c.
Duplicate check based on file name.
d.
Blocking of file processing during a specific file.
c)
Sign off on input file format and mapping.
d)
Sign off on reporting format.
7
3.5.1. FTP Pre-requsites:
FPL Tech will share their FTP for processing.
a)
They must share the following with Karix:
a.
Host url
b.
Port
c.
Username
d.
Password
b)
FPL Tech must whitelist Karix IP: 103.250.30.1
c)
FPL Tech must provide admin access to the FTP setup to the user.
4. Reporting Requirements
4.1. Reporting formats
Karix will place the DLR report on T+1 basis for each of the channels in respective folders.