Name: Setting Up Payment Authorization Verification in Open Payment Framework
Uploaded: 2025-6-24
Duration: 219 s
Description: A payment authorization verification is required to initiate a payment and proceed with an order in SAP Commerce Cloud. This video demonstrates how to set up a payment authorization verification in the Open Payment Framework.

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>A payment authorization verification is required to initiate a payment and proceed with an order in SAP Commerce Cloud. This video demonstrates how to set up a payment authorization verification in the Open Payment Framework.</div></div></div>

Setting Up Payment Authorization Verification in Open Payment Framework

Hello, in this video, I will demonstrate how to configure payment authorization verification within OPF.  Starting from the checkout page during the payment step,  I'll fill in the required information to initiate the payment.  After submitting, I am redirected back to the checkout page, but an Unable to proceed error appears.  However, when I check the Stripe dashboard, the payment shows as successful.  Despite that, the transaction in OPF remains in a waiting state.  This indicates that the authorization verification step isn't configured.  Let's do it now.  First, I'll edit the authorization settings and navigate to the verification configuration section.  Here, we can define how OPF verifies the payment results coming back from the payment service provider to SAP Commerce Cloud. The key options include local verification using HMAC or verification via API call to the payment provider.  Referring to the documentation, we see that a session ID is generated during checkout session creation.  This session ID is used to access the session endpoint and check the payment status.  To perform the API call, we need to copy the API endpoint URL first.  In OPF, I'll select the method Verification Requires API Call and paste the endpoint URL.  I will need the session ID for this call.  Recall that we received it  during session initialization,  but we did not retain it.  To address this, I'll create a custom  field called Checkout Session ID,  map it from the ID field,  and set it to be retained.  After saving the configuration and reinitializing the payment on the checkout page,  the Checkout session ID field  should be populated in OPF.  Next, I'll go back to the verification settings and assign this custom field's value as the session identifier for verification.  We also need to authenticate the API call. I'll validate the previously created Stripe  demo secret key for authorization.  Then, I will add a new authentication method using this secret key.  The API request will use JSON as the content type.  Since it is a GET request, I will leave the request body empty.  For the response, I will set the response type to JSON and copy the example response from the documentation into the body.  I now generate the necessary configuration fields automatically.  To determine if the transaction is successful, I'll map the verification result based on the payment status.  According to Stripe's API, status values include paid and unpaid. I will map paid to an authorized status and unpaid to a canceled status.  Finally, I'll save the configuration. Thank you for watching!