Technical Business Analyst
Technical depth for BAs: message structures, APIs, integration patterns and testing, with the integration landscape first.
121Core lessons
16Chapters
8.9Hours of narration
5Simulators
Who this is for
A business analyst who writes interface specifications, validates messages and works with engineering teams.
Experience level: Working BA, 3 to 8 years, technical. A BA who writes interface specifications and works with engineering.
What you will be able to do
- Write interface specifications and validate messages against schemas.
- Design API contracts and integration patterns for payments.
- Test and certify a payment integration end to end.
Prerequisites
The Business Analyst pathway, or equivalent BA experience in payments.
Recommended sequence
Work through the chapters in this order. Within each chapter, complete the core lessons listed.
- Banking Integration Patterns (Lessons 1-1)
The integration landscape first, before any API-specific technical material. - ISO 20022 Fundamentals (All lessons)
ISO 20022 fundamentals. - pacs.008 Deep Dive (All lessons)
pacs.008 deep dive. - Complete ISO 20022 Catalogue (All lessons)
The complete ISO 20022 catalogue. - ISO 20022 Technical Implementation (All lessons)
ISO 20022 technical implementation, including XML validation. - pain.001 and pain.002 in Depth (All lessons)
pain.001 and pain.002 in depth. - Claims, enquiries and case management (All lessons)
Claims and case management messages: camt.057, pacs.028, camt.027, camt.087. - Reject and Return in CBPR+ (All lessons)
Reject and return in CBPR+, building on ch41. - API Banking and Open Banking (All lessons)
API banking and open banking. - API design standards and integration patterns (All lessons)
API design standards and integration patterns: versioning, pagination, rate limiting, error taxonomy, idempotency, webhooks. - Banking Integration Patterns (Lessons 2-9)
Banking integration patterns: OpenAPI contracts, event-driven payments and Kafka, OAuth2 and mTLS. - Payment Data Model and Mapping (All lessons)
The payment data model and mapping. - System Design Deep Dive (All lessons)
System design deep dive. - Payment engine internals and observability (All lessons)
Payment engine internals and observability: engine modules, booking entries per message, worklist and audit, orchestration failure handling. - Payment Hub: Enterprise Architecture (All lessons)
Payment hub enterprise architecture, the advanced companion to ch25. - Payment Testing and Certification (All lessons)
Payment testing and certification.
Simulators and labs
Assessments
Capstone: Integration specification
Design an integration for a real payment flow.
Deliverable: An integration specification: an OpenAPI contract for a payment API, a message mapping for one payment type, and a test pack covering the happy path and the main failures.
Completion criteria
- Finish every core lesson in the sequence.
- Pass the APIs, Messaging and Architecture tests with 70% or more.
- Complete the required simulator and lab exercises.
- Submit the integration specification.