Name: Using Adjacent API Calls with Custom Fields in Open Payment Framework in SAP Commerce Cloud
Uploaded: 2025-8-28
Duration: 332 s
Description: This video demonstrates how to use adjacent API calls with custom fields in OPF to attach a customer to a checkout session, including creating a customer via API, mapping data, storing the customer ID as a custom field, and updating reauthorization requests for seamless and consistent payment processing.

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><div>This video demonstrates how to use adjacent API calls with custom fields in OPF to attach a customer to a checkout session, including creating a customer via API, mapping data, storing the customer ID as a custom field, and updating reauthorization requests for seamless and consistent payment processing.</div></div></div>

Using Adjacent API Calls with Custom Fields in Open Payment Framework in SAP Commerce Cloud

Hello, in this video,  we will look at how to use adjacent API calls with custom fields in OPF.  In a previous video, we encountered an issue with a reauthorization request as there was no customer assigned to our test checkout session.  Here we will see how we can use an adjacent API call to attach a customer to a checkout session and ensure all required data is passed using custom fields.  The Payment Service Provider documentation for checkout sessions shows that we can pass a customer ID.  So first, we'll create a customer for which we'll once again use the PSP documentation to configure our API call. Here we copy the URL information and switch to OPF.  Adjacent API calls allow us to add another API call to this transaction.  We can add the call by clicking the plus icon and then drag the call to position 1.  Then we change the method to post and add the request URL for creating a customer that we just copied from the Stripe documentation, making sure to add our write context variable.  Next, we set the authentication method, for which we'll use a demo setup for this video.  Once again, the PSP documentation shows us what information can be passed along for our customer.  In our case, we will pass an email, name, and billing address.  These values now need to be mapped for this request.  Setting the content type to URL encoded, we can now do our mapping, selecting the various address fields for country, city, postcode, and so on, and the email.  However, to map the name, we can't simply select a value.  The gateway field only provides a name, while we need to map two fields, for first and last name respectively.  So, we switch from mapping an existing field to a script.  We can now tell OPF to input the field first name, and then input the field last name.  For the response, we set the content type to JSON, and add the code snippet for this from the PSP documentation.  This response contains a field for Customer ID, which we will need for our reauthorization request, that we will be running later.  We open the Custom Mapping tab and create a custom field by clicking the Add Custom Mapping button.  This field is to be called Customer, and we'll map it to the mentioned ID.  As we want to use this information again later, we will check the Retain box.  This means the information will be saved beyond the scope of this transaction.  With the creation of our customer covered, we now need to add this customer to our checkout session.  The PSP documentation shows that we can add a parameter for the customer ID to our checkout session.  So we switch to the call to create a checkout session.  We add the customer value to the example request and click the Generate Fields button.  We can now map the customer field we just added to the custom ID field we retained from our create customer call.  This takes care of the authorization, but we also need to make sure to update the reauthorization, where we do the same again.  We add the customer to the example request, map the ID field once again, and save our changes.  It's now time to test our setup.  We place an order on the SAP Commerce Cloud storefront and can see the email address has been populated.  The payment is authorized, and we can switch back to OPF.  In the payment interactions, we can open the request log for this order and see that a customer is being requested and the checkout session has a customer passed with it.  In the transaction view, we can see an accepted transaction and the customer ID in the list of custom fields. The customer ID can now be used for  any follow on linked transactions. In the next video we will complete  all remaining changes  and finalize testing of the reauthorization.