Name: Configuring Reauthorization in Open Payment Framework
Uploaded: 2025-8-21
Duration: 276 s
Description: This video explains how to configure reauthorization in OPF, covering payment intent setup, off-session parameters, and ensuring future usage for continuous authorization.

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>This video explains how to configure reauthorization in OPF, covering payment intent setup, off-session parameters, and ensuring future usage for continuous authorization.</div></div>

Configuring Reauthorization in Open Payment Framework

Hello, in this video, I'll demonstrate how to configure reauthorization in OPF.  Reauthorization is necessary when an authorization times out, when a fund's hold expires, or when handling split shipments.  In the case of split shipments.  By checking the current  capture method configuration, which is set to single partial capture per authorization rather than  multiple partial capture, the system will capture payment for the first shipment and then  require reauthorization and recapture for each subsequent shipment.  To configure reauthorization, on the Payment Integration Configuration page,  I'll edit the reauthorization component.   It's important to note that OPF doesn't have access to the original credit card details.  Instead, it relies on a payment token,  which is typically used in the reauthorization process.  According to the API documentation,  this process begins by creating a new payment intent object  and immediately confirming the transaction.  It's essential to include off-session  to indicate that the customer isn't actively present during the reauthorization. The payment method ID must be provided  to associate it with the original transaction.  Lastly, the setup future usage parameter  should be in place to indicate the reuse of the payment method  for subsequent transactions.  Let's begin by copying the initial payment intent  creation request here and then switch back  to the reauthorization configuration page.  I will set the HTTP method to post,  paste the request URL I just copied and replace the hard-coded  endpoint with the variable defined earlier.   I also need to add an authentication method,  set it to the demo secret key created  earlier and save it.  Now, I'm heading over to the request mapping  section to build the payload.  I'll set the content type accordingly,  then fill in each parameter individually based on the details we reviewed  in the API documentation.  This includes the amount and the currency  with sample values.  The confirm parameter needs to be included for automatic authorization.  The off-session flag should be included,  and of course,  the payment method with a sample ID here.  I'll click Generate Fields to see them in the right pane and start mapping them.  I'll map the Amount field to Amount in Exponent.  I'll leave the off-session flag  to a hard-coded value of true.  Then, I'll map the currency to the Currency field.  I'll hold off on mapping the payment method  for now and click Save.  Next, I'll need to map the response.  The API documentation provides a sample response which I can copy directly.  Now, back to the response mapping section, I'll paste the copied response body.  Don't forget to set the content type as JSON.  I'll click the generate button to adjust changes based on the response body example.  Transaction status is mapped to  the gateway field status.  Its accepted value is mapped as succeeded.  I now save.  These are the basic steps.  As you remember, I still have a missing mapping value to complete  my request mapping.  The payment method is still outstanding  and I will map it to the inbuilt field called token.  I'll switch to the notification request mapping.  Here, I'll map the token field  to the gateway field payment method.  I'll save the changes now.  As previously mentioned,  I also need to ensure the setup future usage parameter is set  during the initial authorization.  Hence, I go back to the configuration page and check the authorization component.  However, the field is not configured in the request mapping section and  must be included now. I'll check the checkout,  create a session documentation, and understand that the field under the  Payment Intent section is  payment_intent_data.setup_future_usage,  and the value to be chosen is off_session.  In the request mapping of  the authorization component,  I'll add the needed parameter and the value,  and make sure to click on the Generate button  to incorporate the changes.  Finally, I'll save the updates.  That completes the configuration of  reauthorization in OPF.