Name: Mapping PSP References in Open Payment Framework
Uploaded: 2025-6-18
Duration: 179 s
Description: In this video, you’ll learn how to capture and map the PSP (Payment Service Provider) reference during payment integration. Follow along as we update transaction mapping settings, verify successful payments, and ensure each order can be directly traced back to its Stripe transaction.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

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?

<div><div><div>In this video, you’ll learn how to capture and map the PSP (Payment Service Provider) reference during payment integration. Follow along as we update transaction mapping settings, verify successful payments, and ensure each order can be directly traced back to its Stripe transaction.</div></div></div>

Mapping PSP References in Open Payment Framework

Hello, in this video, I will demonstrate how to verify and map PSP references during payment integration.  Let's begin by testing the current status of the payment process on the storefront checkout page.  As you can see, the order confirmation page is displayed, indicating the payment was successfully processed through Stripe.  Next, I'll check the OPF's transaction page. The related transaction is still marked as waiting, and there is no PSP reference linked to it.  However, the verification status is already marked as authorized.  To resolve this, we need to configure two key steps. 1.  Store the PSP reference so we can link the transaction back to Stripe.  2. Map server-to-server notifications with webhooks to authenticate the transaction using Stripe's webhook capabilities.  In this demo, I will focus on capturing and saving the PSP reference first.  The webhook setup will be covered in a subsequent video.  Now, I'll examine the request log and open the authorization verification request.  I'll copy the payload, as we'll use this information to generate the mapping fields later.  Notice that within the payload, there's a property called payment intent.  This is directly related to the PSP reference.  I'll refer to Stripe's API documentation to confirm that payment intent is the unique identifier for the payment.  Therefore, we'll map this value as the PSP reference.  Next, I will navigate to the authorization configuration page and locate the verification request settings. In the response mapping body, I will replace the previous example payload with the one I just copied.  Then, I will regenerate the fields for mapping.  Most fields remain unchanged, but I will specifically map the payment intent property as the PSP reference.  Let's run a test.  I will add a random product and place a new order.  After completing the order, I will copy the order ID.  Using this ID, I will search for the corresponding transaction.  In the transaction details, you'll see that the PSP reference has now been retained.  Finally, I can copy this PSP reference and use it to locate the transaction directly in Stripe, where all the payment details are available.  That concludes our walkthrough on testing, verifying, and mapping the PSP reference.  Thank you for watching!