Digital Payments and Fintech Security Training Course

Duration 10 days 19 modules · 65 contact hours
Level Intermediate Certificate on completion
Who attends Payment Product Managers, Finance Operations Managers and others
Fee from USD 2,200 KSh 190,000 for Kenyan organisations
Where 52 cities + online See dates by city
Next start 16 Nov 2026 Course code SD-FT-032

Before you join: Participants should have working familiarity with business payments, financial operations, banking products, technology projects or risk and compliance processes.

Dates & prices

Two start dates a month in every city, and live online on weekdays or weekends. Fees are per participant; classroom fees include tuition, materials, lunch and refreshments, and the certificate.

Suggest a date or city

Showing the next six months. Later dates, other cities and private deliveries for your team are available on request.

Course overview

Digital payment programmes must balance customer convenience, processing cost, settlement speed, fraud exposure and regulatory obligations. Product, finance, operations and security teams need a shared view of how card payments, account-to-account transfers, wallets, payment gateways and merchant acquiring work together. They also need controls that identify suspicious activity without creating unnecessary payment declines or customer friction.

This course examines the payment lifecycle from customer authentication through authorisation, clearing, settlement, reconciliation, dispute handling and reporting. Participants analyse payment architectures, compare payment rails, assess fintech partner models, interpret PCI DSS responsibilities and apply security controls for APIs, cloud services, mobile wallets and merchant channels. The programme also covers fraud monitoring, sanctions screening, transaction risk scoring, incident response, third-party assurance and payment data governance.

Instructor-led sessions combine focused briefings with financial-services cases, payment-flow analysis, group exercises, fraud-response simulations and structured application planning. Participants work with practical methods from the first week, then develop a payment security and control package for a realistic business scenario. They leave with reusable artefacts including a payment-flow map, control matrix, fraud-rule design, third-party due diligence checklist and incident response plan. The course runs for 10 days, from 08:30 to 16:30, in classroom locations in more than 50 cities or live online, and includes a certificate of completion.

It is suited to professionals responsible for payment products, finance operations, fraud prevention, technology risk, cybersecurity, compliance and fintech partnerships. It is particularly relevant where firms are launching digital payment services, improving merchant acceptance, integrating payment providers or strengthening controls after fraud losses or audit findings.

What you will be able to do

  • Map end-to-end card, wallet and account-to-account payment flows
  • Assess payment rail selection using cost, speed, reach and risk criteria
  • Apply PCI DSS responsibility models to merchant and service-provider environments
  • Design fraud monitoring rules using transaction signals and risk thresholds
  • Evaluate API, mobile and cloud security controls for payment integrations
  • Build reconciliation and settlement control procedures for digital payment operations
  • Conduct fintech third-party due diligence using security and operational risk criteria
  • Produce a payment security and control plan for a defined business case

Benefits of attending

For you

  • Improved ability to challenge payment-provider proposals and integration designs
  • Practical fraud-control skills for reducing false positives and payment losses
  • Clearer communication with security, finance, operations and technology specialists
  • Reusable methods for assessing payment risks during product and vendor decisions
  • Stronger evidence base for progression into payments, fraud or fintech risk roles

For your organisation

  • Better controlled payment launches through documented flows, ownership and security requirements
  • Reduced fraud exposure through stronger monitoring rules and escalation procedures
  • Fewer reconciliation breaks and settlement exceptions through defined operational controls
  • Improved supplier oversight for payment processors, fintech platforms and cloud providers
  • More defensible audit and regulatory evidence for payment security responsibilities

Course modules

19 modules over 10 days

Participants can describe the parties, data exchanges and obligations within a digital payment transaction.

  • Payment value chains: issuers, acquirers, schemes, processors, gateways and merchants
  • Authorisation, clearing and settlement roles within card payment processing
  • Account-to-account payments through open banking and instant-payment rails
  • Digital wallets, token service providers and mobile payment acceptance
  • Merchant categories, payment facilitators and marketplace payment operating models
  • Payment revenue, interchange, scheme fees and acquiring cost components

Participants can compare payment methods and select appropriate rails for defined customer and business requirements.

  • Card, ACH, wire, real-time and wallet rail characteristics
  • Payment-method selection using reach, cost, speed and certainty criteria
  • Cross-border payment routes, correspondent banking and foreign-exchange considerations
  • Recurring payments, card-on-file arrangements and merchant-initiated transactions
  • Buy-now-pay-later models, credit risk allocation and merchant economics
  • Build-versus-buy decisions for payment orchestration and gateway capabilities

Participants can map a payment architecture and identify control points across system interfaces.

  • Payment architecture diagrams covering channels, services, data stores and providers
  • API request flows between merchant platforms and payment gateways
  • Webhooks, idempotency keys and retry logic for reliable payment processing
  • Tokenisation boundaries for primary account numbers and customer credentials
  • Service-level objectives for authorisation latency, availability and recovery
  • Document integration assumptions, dependencies and failure-handling responsibilities

Participants can assess authentication approaches and authorisation controls for different payment journeys.

  • Strong Customer Authentication under PSD2 and transaction-risk analysis
  • EMV 3-D Secure flows, frictionless decisions and challenge outcomes
  • Multi-factor authentication factors, binding methods and account recovery controls
  • Risk-based authentication using device, behavioural and transaction signals
  • Authorisation response codes, soft declines and retry decision rules
  • Step-up authentication triggers for high-risk payment events

Participants can define PCI DSS scope and assign responsibilities for payment data protection.

  • PCI DSS v4.0.1 scope identification for cardholder-data environments
  • Cardholder data flows, storage prohibitions and retention requirements
  • Network segmentation evidence and isolation of payment system components
  • Shared-responsibility matrices for merchants, processors and cloud service providers
  • Key management controls for encryption, rotation, access and destruction
  • SAQ selection, attestation evidence and compensating control documentation

Participants can specify security requirements for payment APIs and customer-facing payment applications.

  • OWASP API Security Top 10 risks in payment integrations
  • OAuth 2.0, OpenID Connect and scoped access-token controls
  • Mutual TLS, certificate pinning and secure service-to-service authentication
  • Input validation, schema enforcement and API rate-limiting controls
  • Secrets management for API keys, credentials and signing material
  • Secure software development lifecycle evidence for payment applications

Participants can evaluate mobile and digital-channel controls that protect payment users and transactions.

  • Mobile-wallet token provisioning and device-binding security controls
  • Secure enclaves, hardware-backed keys and biometric authentication limitations
  • Mobile application threat modelling using STRIDE categories
  • Rooted-device detection, runtime protection and tamper-response mechanisms
  • Session management, credential stuffing and account-takeover prevention
  • Accessibility and customer-support safeguards during authentication failures

Participants can identify payment fraud patterns and prioritise threats using a structured model.

  • Card-not-present fraud, account takeover and synthetic identity indicators
  • Friendly fraud, chargeback abuse and merchant dispute evidence
  • Authorised push payment fraud and social-engineering attack patterns
  • Money mule networks, transaction layering and beneficiary-risk signals
  • STRIDE threat modelling applied to payment journeys and assets
  • Fraud loss measurement using gross loss, recovery and false-positive rates

Participants can design transaction-monitoring rules and decision paths for payment fraud controls.

  • Rules engines using velocity, amount, geography and device signals
  • Risk scores, decision thresholds and approve-review-decline strategies
  • Feature quality assessment for fraud-model input data
  • Case-management queues, investigator evidence and escalation service levels
  • False-positive reduction through segmented thresholds and feedback loops
  • Champion-challenger testing for fraud-rule and model changes

Participants can place sanctions, AML and transaction-monitoring controls within payment processes.

  • Sanctions screening points for originators, beneficiaries and payment messages
  • Name matching, fuzzy logic and alert disposition evidence
  • Anti-money-laundering red flags within merchant and customer transactions
  • Know-your-customer data quality and beneficial-ownership verification
  • Payment-message fields supporting sanctions and financial-crime investigations
  • Escalation routes for suspicious activity and regulatory reporting

Participants can build controls for settlement accuracy, reconciliation and payment exception management.

  • Settlement cycles, prefunding requirements and liquidity exposure measurement
  • Three-way reconciliation across gateway, processor and bank records
  • Exception queues for missing, duplicated and mismatched transactions
  • Suspense-account governance, ageing analysis and resolution ownership
  • Chargeback accounting, reserve balances and merchant settlement adjustments
  • Daily control reports covering volumes, values, breaks and ageing

Participants can manage dispute processes using evidence, time limits and customer-remediation controls.

  • Chargeback reason codes, representment evidence and scheme timeframes
  • Retrieval requests, pre-arbitration stages and arbitration cost implications
  • Customer complaint handling for unauthorised and failed payments
  • Root-cause analysis linking disputes to product and control failures
  • Evidence retention schedules for transaction, authentication and delivery records
  • Dispute dashboards tracking win rates, reasons and financial impact

Participants can prepare response arrangements for payment outages, fraud events and data compromises.

  • Business impact analysis for critical payment services and dependencies
  • Recovery time objectives and recovery point objectives for payment platforms
  • Incident classification for outages, fraud spikes and data breaches
  • Runbooks for processor failure, duplicate payments and settlement disruption
  • Customer communications during payment incidents and service restoration
  • Post-incident reviews using timelines, root causes and corrective actions

Participants can assess cloud control requirements and govern sensitive payment data appropriately.

  • Cloud shared-responsibility models for payment workloads and sensitive data
  • Data classification for cardholder, personal, transaction and authentication data
  • Encryption in transit, encryption at rest and key-custody decisions
  • Access reviews using least privilege and segregation-of-duties principles
  • Logging requirements for payment events, administrative actions and investigations
  • Data residency, retention and deletion controls for payment records

Participants can assess fintech providers and define contractual controls for payment services.

  • Vendor due diligence covering financial viability, security and operational capability
  • SOC 2 reports, penetration-test evidence and control-gap assessment
  • Contract clauses for data processing, audit rights and incident notification
  • Subprocessor disclosure, concentration risk and exit-plan requirements
  • Service-level agreements for availability, support and transaction-processing performance
  • Ongoing monitoring through assurance reviews, incidents and performance metrics

Participants can establish governance, oversight reporting and assurance evidence for payment operations.

  • Payment governance structures defining accountable owners and decision rights
  • Risk appetite statements for fraud loss, outages and compliance breaches
  • Control self-assessments using process owners and evidence standards
  • Key risk indicators for fraud, availability, reconciliation and vendor performance
  • Internal audit testing of payment controls and issue remediation
  • Board reporting on payment risk, incidents and control effectiveness

Participants can use payment data to assess operational performance, risk and commercial outcomes.

  • Authorisation-rate analysis by issuer, channel, geography and payment method
  • Payment conversion funnels from checkout initiation through successful settlement
  • Fraud-rate segmentation by customer, merchant, device and transaction type
  • Cost-of-acceptance analysis using fees, declines and operational exceptions
  • Cohort analysis for recurring-payment retention and involuntary churn
  • Dashboard design linking customer outcomes, risk indicators and financial measures

Participants can assemble a risk-based control design for a new or existing payment service.

  • Control matrices linking payment risks, objectives, owners and evidence
  • Inherent-risk assessment before control selection and residual-risk acceptance
  • Preventive, detective and corrective controls across payment process stages
  • Control testing procedures for design effectiveness and operating effectiveness
  • Prioritised remediation roadmaps using risk, effort and dependency criteria
  • Executive decision papers presenting control gaps, options and recommendations

Participants can build, review and present a complete payment security and control plan for a defined payment service.

  • Define payment service scope, customers, channels and transaction volumes
  • Map payment flows, systems, data assets and external dependencies
  • Assess fraud, security, operational and third-party risks using evidence
  • Specify authentication, monitoring, reconciliation and incident-response controls
  • Prepare implementation priorities, ownership, milestones and assurance metrics
  • Present the plan for peer review and management-level challenge

Exercises and examples are adapted to each cohort's sectors and roles.

What you take back to work

  1. End-to-end payment-flow mapping template
  2. Payment security control matrix
  3. Transaction fraud-rule design sheet
  4. Settlement reconciliation procedure template
  5. Fintech provider due diligence checklist
  6. Payment incident response plan

Who should attend

  • Payment Product Managers — need to design viable, controlled payment propositions
  • Finance Operations Managers — need stronger settlement, reconciliation and exception controls
  • Fraud and Financial Crime Analysts — need practical transaction monitoring and response methods
  • Information Security Managers — need to assess payment data, API and mobile security risks
  • Compliance and Risk Managers — need oversight of payment regulations and third-party exposures
  • Fintech Partnership Managers — need structured assessment of providers, processors and platform partners

Skills and tools covered

Payment flow analysisFraud risk managementPCI DSS complianceAPI security controlsSettlement reconciliationFintech due diligence

Tools and standards

PCI DSS v4.0.1, OWASP API Security Top 10, NIST Cybersecurity Framework 2.0, ISO 20022

How the course runs

Training methodology

Teaching combines short instructor briefings with payment-flow cases from banks, merchants, fintechs and public-service payment programmes. Participants analyse transaction journeys, identify control failures, compare fraud scenarios and review realistic provider evidence. Group exercises use payment architecture diagrams, reconciliation data, API-control requirements and incident-response decisions. Simulations test judgement during fraud spikes, service outages and data-security events. Each participant maintains an application plan, building a payment security and control package that can be adapted to their own payment environment.

Requirements and prerequisites

Participants should have working familiarity with business payments, financial operations, banking products, technology projects or risk and compliance processes. Experience with card payments, merchant acquiring, fraud operations, cybersecurity or fintech partnerships is useful but not essential. Participants should be comfortable reading process diagrams, discussing basic data flows and using spreadsheets for simple analysis. Coding, penetration-testing expertise, cryptography mathematics and prior PCI DSS certification are not required. The course explains payment terminology and technical control concepts before applying them to operational and risk decisions.

A typical training day

08:30 – 10:30First session
10:30 – 10:45Refreshment break
10:45 – 12:30Second session
12:30 – 13:30Lunch and networking
13:30 – 15:00Third session
15:00 – 15:15Refreshment break
15:15 – 16:30Workshop and daily review

Live online deliveries follow the same structure in East Africa Time, with shorter screen blocks and longer breaks.

What the fee includes

  • Instruction by a practitioner facilitator
  • Full course workbook and materials
  • Exercise files, templates and case studies
  • Refreshments and lunch on classroom deliveries
  • Certificate of completion
  • Post-course application plan

Frequently asked questions

Participants should understand basic business payments, financial operations, technology projects or risk processes. Prior card-payment, cybersecurity or fraud experience is helpful, but coding and specialist security qualifications are not required.

Bring a laptop for live-online delivery and, where permitted, non-sensitive examples of payment flows, control issues or provider questions from your workplace. Do not bring customer data, cardholder data, credentials or confidential incident records.

The course suits payment product, finance operations, fraud, security, compliance, risk and fintech partnership professionals. It also helps managers who oversee payment providers or payment-service change programmes.

This course focuses specifically on payment transaction flows, payment operations, fraud controls, settlement, card-data protection and provider oversight. General fintech courses usually focus more on business models, while cybersecurity courses may not address payment economics or reconciliation.

Participants can use the templates to map an existing payment journey, assess control gaps, review a payment provider or improve fraud and reconciliation reporting. The capstone plan can be adapted into a practical workstream for a launch, audit response or control improvement project.

The first week establishes payment rails, architecture, authentication, data protection and fraud controls. The second week covers operations, resilience, third-party risk, governance, analytics and the final payment security and control plan; each day runs 08:30 to 16:30 with about 6.5 contact hours.

Questions about this course?

Ask about dates, fees, group bookings or running it for your team. Our training team replies by email.