Name: Configuring Payment Authorization By Initializing A Payment Form within Open Payment Framework
Uploaded: 2025-6-10
Duration: 387 s
Description: This video demonstrates how to configure a payment authorization by initializing a payment form within 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>This video demonstrates how to configure a payment authorization by initializing a payment form within Open Payment Framework.</div></div></div>

Configuring Payment Authorization By Initializing A Payment Form within Open Payment Framework

Hello, in this video, I'll show you how to configure payment authorization by initializing a payment form within the OpenPayment framework. After creating a payment integration in the framework workbench, the next step is to set up authorization. First, navigate to the Payment Processing pane and edit the authorization settings. To configure the front-end component, you need to select and set up a payment form. There are several display options available. The first is iframe, which embeds the payment page directly into your site. The second is payment page, which involves redirecting users to a hosted payment page. The third is hosted fields, which uses your payment provider's JavaScript to generate a payment form with multiple iframes, giving you more control over the user experience. For instance, if we look at Stripe's documentation from the Quick Start series for checkout creation, Stripe Checkout is a hosted page, so I'll select the Payment Page option. Next, we need to specify how to initialize the checkout process on the front end. According to Stripe's documentation, creating a checkout session requires a server-side API call that establishes the session, followed by redirecting the customer to the checkout page. Therefore, the Session Initialization Request is required. Looking at the API example for creating a checkout session, I see that it returns a URL and no custom JavaScript is necessary. So, I'll choose the Create Payment Page by URL as the method for creating the Gateway Page. This completes the initial setup options for creating a payment form. The next step is configuring the API call within the OpenPayment framework to generate the checkout session. This involves specifying parameters such as order details, payment or subscription type, success and cancellation URLs, and currency, etc. To keep things straightforward, I'll build a minimal working example. Since Stripe uses a combination of post requests with Xform URL content type and returns a JSON response, I'll set the HTTP request method to post and ensure the content type is set to Xform URL accordingly. I can copy the API endpoint URL directly to be the API URL. I see that basic authentication has already been set up, so now I need to configure the secret key to authenticate the API call. To do this, I'll switch to the Stripe dashboard for the test account I created earlier and copy the secret key directly from the API keys section. Now, within the API call configuration, I'll add a new authentication method. For this call, I'll select basic authentication as the type and be sure to give it a simple, recognizable name. In the username field, I'll paste the secret key I just copied. The password field isn't required in this case, so I can leave it blank and simply save the configuration. The next step is to specify the request parameters. To keep things straightforward, I'll start by including only the mandatory ones. The first is the currency. Switching back to the API call configuration and the payment provider example field, I'll enter a sample value for the currency, such as USD, to serve as an illustrative example. Next, let's review the mandatory parameters, the return URL and the success URL. I'll use this example URL as my success URL. For the return URL, I can use the same value, perhaps with a different suffix like failed to indicate a failed payment. Once I have these URLs, I can generate the necessary fields automatically by clicking this button here, which makes mapping straightforward. The return URL should be mapped to the existing field called Cancel URL. The success URL should be mapped to the result URL field. Finally, the currency parameter should be mapped to its corresponding field, simply labeled currency. After completing these mappings, I'll save my configuration. After configuring the request with authentication and parameters, the next step is to set up the response mapping. To do this, I'll review the example response in JSON format. I can copy the entire response example and paste it into the designated field here. Using the provided tools, I can then easily generate the essential response fields. In this case, the redirect URL from the response should be mapped to the gateway field named URL. For now, I can leave the other response fields unchanged and proceed to save the changes. Finally, I'll configure the front -end component to use this setup. In the Create Gateway page configuration, I'll set the HTTP method to get, select Xform URL as the content type, and specify the request URL as the redirect URL returned by Stripe. Using the Framework Smart Fields feature, I can dynamically select the correct URL field provided. With this, the setup for initializing a payment form that handles authorization via the API call is complete. This concludes our demonstration. Thank you.