Services

Video meeting . 15 mins

Have questions?

Free 1:1 Payment BA Session
FREE
Video meeting . 45 mins
₹249
Digital Product
₹500
Best Seller
Video meeting . 45 mins
₹249
Video meeting . 60 mins
₹499
Popular

About me

I’m a Business Analyst and Payments SME with real-world experience across payment transformation, SEPA, Instant Payments, ISO 20022, Cash Management and Digital Banking. Over the years, I’ve worked across different roles in Payments, including Business Analysis, Product Ownership and Team Management. This has given me a practical view of how payment solutions work—not just from a message or requirement perspective, but from an end-to-end business and customer perspective. Through my LinkedIn Payment BA Awareness and Payment Education series, I share practical lessons from real payment scenarios and encourage BAs to look beyond frameworks and documentation. My core belief is simple: A good BA doesn't just capture what stakeholders say. A good BA understands the problem, asks the right questions, challenges assumptions, connects the dots and thinks about what can happen beyond the happy path. On Topmate, I offer 1:1 sessions around: • Payment Business Analysis • Payment domain knowledge • BA Thinking & problem-solving • Real-world payment scenarios • Payment BA interview preparation • Career and professional guidance Bring me your question, scenario or challenge. Let's think through it together. 📌 Follow my Payment BA content and connect with me on LinkedIn: https://www.linkedin.com/in/jebaraj-d-65b5b01a/ If you're serious about becoming a stronger Payment BA, let's connect.

Frequently asked questions

“I know the ISO 20022 message used for payment cancellation. But can I explain the complete cancellation journey?”

Many of us can confidently answer: “camt.056 is used for payment cancellation.” But what happens when an interviewer asks: “Can you walk me through a real-world end-to-end cancellation journey?” That’s where many of us struggle to connect the dots. A real payment scenario is not just about identifying one message. You need to understand who initiates the request, who receives it, how the original payment is identified, what checks happen, how the request is accepted or rejected, and what happens to the original transaction. For example, depending on the scenario, a cancellation journey can involve camt.055 → camt.056 → camt.029, but the actual flow depends on the payment scheme and processing model. This is where BA thinking becomes important — connecting the message, business event, participants, processing logic and outcome into one story. In this session, let's take a real-world cancellation scenario and connect the dots end-to-end.