Name: Configuring Additional Notification Mappings in Open Payment Framework
Uploaded: 2025-7-8
Duration: 336 s

Share feedback

<p>We are aware of intermittent issues in accessing the learning content</p>

We are aware of intermittent issues in accessing the learning content

Personalize your learning.

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

Please try again later

Sorry, we encountered an error

Try again or reset results to continue browsing

We didn’t find what you’re looking for

To continue, please log in

Your session has timed out

Validate your skills and learning by completing the certification exam and gain a highly recognised accreditation.

Book your certification exam

Complete the assessment to validate your SAP PartnerEdge competency qualifications.

Ready to take your assessment?

Learn about the key features and essentials in the latest release to help you prepare for the Stay Certified assessment.

Prepare for assessment

Learn new skills you need at your own pace with our bite-sized lessons.

Prepare for certification

In your My Learning account you can view your certification and learn how to take your Stay Certified assessment.

Ready to take your Stay Certified assessment?

Explore {title} at SAP Learning. Find out more!

Assessment

Course Completion

Knowledge Badge

Certification Exam

Theoretical Exam

Schedule

External Course

Practical Exercise

Practical Test

External Hands-On

External Resource

Learning Journey

Learning Journey Assessment

Lesson

Live Session

Practice System

Quiz

Scenario Based Assessment

Course Assessment

Course

Stay Certified

Subscription

System Based Assessment

Test Out

Unit

Video

Video Playlist

Week

<div><div>In this video, we'll walk you through configuring crucial notification mappings in Open Payment Framework. Starting with a review of existing mappings, we'll highlight the importance of mapping payment methods, request types, and transaction statuses, while introducing key fields like card expiry date and customer order links. You'll learn how to adjust webhook settings, utilize Stripe's client reference ID, and ensure accurate tracking of charge notifications, enabling precise association of transactions with customer orders.</div></div>

Configuring Additional Notification Mappings in Open Payment Framework

Hello, in this video, I will demonstrate how to configure additional important notification mappings in OPF. First, let's review the current notification mappings for the payment integration. We need to map the payment method, determine the request type, and identify the transaction status. Additionally, it's crucial to include key fields such as card expiry date, card type, and the link back to the relevant customer order. Upon examining the current event payload, we notice it lacks some of the data needed for our processes. Therefore, instead of the event type here, we need to select a different one that provides the required information. Switching to the webhook configuration in the Payment Service Provider's Sandbox environment, I'll click here to access the Edit Destination section. For the event, I'll review the available options related to charge. The charge .succeeded event seems ideal for accurately tracking and processing successful transactions. I'll save this change. Next, we need to link the correct order to each notification. Although we previously mapped the PS/PE reference field, it's configured during the verify step, which likely occurs after a notification is sent. To ensure proper correlation, we should use a field available at Session Initialization, which occurs before the notification. Stripe provides a client reference ID, which is a good candidate. I will switch to the Session Initialization request and add this client reference ID to the request mapping. Then, I'll map it to the reference ID field in OPF. to verify i'll go to the transactions page select a transaction and see that the reference id remains linked allowing us to match charge notifications to the correct order after these adjustments i'll return to the storefront and perform a test payment to generate new notifications i'll then check the notification log filtering by our payment integrations configuration id for clarity after a brief wait i see a charge succeeded notification i'll copy this payload to use as an example in the demo and go to the notification request mapping section to replace the current payload with this one now i'll generate the fields and start mapping them for request type i'll select the relevant type field and set its value to charge succeeded from the payload. For transaction status, I'll pick the appropriate status field in the data object and map the value accepted to succeeded. For the card expiry, I'll map the last four digits, expiry month and expiry year. The expiry date could also be used, but since month and year are mapped, it's not needed. For card type, I'll map it to the card brand and map the value of visa to visa. For PS/PE reference, I'll map this from the payment intent field. Finally, I'll map the payment method and set the value credit card to the card field. However, the customer reference for reconciliation is missing from the payload. To address this, we will include it during the session initialization request. I'll go to the request mapping and add a new metadata field within the payment intent object. After generating the new field, I'll then map it to the reference ID in OPF. To demonstrate this, I'll perform another payment request in the storefront. After a few refreshes of the notification logs, filtered by our configuration ID, I see a new transaction linked to the correct order, thanks to the mapped payment intent PS/PE reference and the reference ID metadata. Within this transaction, I can see the new metadata containing the reference ID, which allows us to relate notifications accurately to their respective orders. I'll copy this payload, return to the notification request mapping, and replace the current payload with this new example. Then, I'll generate the additional field, and map the reference ID to the reference ID from the metadata. This setup ensures that even if the notification is sent before the PS/PE reference is available, we can still correctly associate notifications with the order using the reference ID. That concludes the demonstration on configuring additional notification mappings in OPF.