Skip to main content
To process credit card transactions on a storefront, we must first set up a “Payment Gateway” and then assign that gateway to “Payment Types”.“Payment Gateways” are created for each supported credit or gift card type, meaning that we can use different gateways for each individual card type, or the same gateway with different credentials. Once gateways have been created, we can assign them through the “Payment Type” settings.In this video, I’m going to demonstrate how to create and manage “Payment Gateways” To process credit card transactions on a storefront, we must first set up a “Payment Gateway” and then assign that gateway to “Payment Types”. “Payment Gateways” are created for each supported credit or gift card type, meaning that we can use different gateways for each individual card type, or the same gateway with different credentials. Once gateways have been created, we can assign them through the “Payment Type” settings. In this video, I’m going to demonstrate how to create and manage “Payment Gateways” In the left menu, on the “SYSTEM” tab, click “Settings”, then click “Payment Gateways”. In the left menu, on the “SYSTEM” tab, click “Settings”, then click “Payment Gateways”. This is the “Payment Gateways” menu. It lists all gateways that have been previously created in this tenant. This is the “Payment Gateways” menu. It lists all gateways that have been previously created in this tenant. To “Edit” an existing payment gateway, we can click on the “Ellipses” button on the far right of the gateway, then click “Edit”. We can also “Delete” the gateway from here. Alternatively, we can click directly on the individual payment gateway to “Edit”. This will direct us to a dedicated page where we can edit the settings of that specific gateway. To “Edit” an existing payment gateway, we can click on the “Ellipses” button on the far right of the gateway, then click “Edit”. We can also “Delete” the gateway from here. Alternatively, we can click directly on the individual payment gateway to “Edit”. This will direct us to a dedicated page where we can edit the settings of that specific gateway. The “Edit Payment Gateway” screen allows users to adjust various details that may be required. All required fields are noted by the “Green Asterisk” next to the field name. In this example, “Nickname”, “Transaction Key”, and “Merchant ID” are all required fields. When we’ve edited the necessary fields, we’ll click the “Save” button on the upper right to save all edits. The “Edit Payment Gateway” screen allows users to adjust various details that may be required. All required fields are noted by the “Green Asterisk” next to the field name. In this example, “Nickname”, “Transaction Key”, and “Merchant ID” are all required fields. When we’ve edited the necessary fields, we’ll click the “Save” button on the upper right to save all edits. Back on the main “Payment Gateways” menu screen, we can click the “Create New Payment Gateway” button on the top right to create a new “Payment Gateway”. Back on the main “Payment Gateways” menu screen, we can click the “Create New Payment Gateway” button on the top right to create a new “Payment Gateway”. This will open the “Create Payment Gateway” screen, which serves as the starting point for configuring a new “Payment Gateway”. Within this window, we’ll find a dropdown menu labeled “Payment Gateway”. As shown here, there are a number of payment gateways, digital wallets, third-party payments, and fraud gateways available out-of-the-box, while others require applications to be installed and configured in the Dev Center first. Users can also create their own applications and “Custom Gateways” through “Payment Extensibility”.A list of available Payment Gateways is available in KIBO Documentation. We’ll look at creating a payment application through “Payment Extensibility” shortly. This will open the create payment Gateway screen, which serves as the starting point for configuring. A new payment Gateway. Within this window, we’ll find a drop-down menu, labeled payment Gateway. As shown here, there are a number of payment gateways digital wallets third-party payments and fraud gateways available out of the box While others require applications to be installed and configured in the dev Center. First Users can also create their own applications and custom gateways, through payment extensibility. A list of available payment gateways is available in kibo documentation. We’ll look at creating a payment application, through payment extensibility shortly. A No-Operation, or “NoOp” gateway, is not a real gateway that connects to an external service. It does not require any credentials and will consider all actions submitted to it to be automatic successes, since it does not actually perform any operations.These are useful for testing Order Management features that don’t require live payment processing, or for Order Management-only instances of KIBO, where the actual payment actions have been performed by the storefront service, and the payment information is only being passed into KIBO with the order data for fulfillment. A no-operation or no-op, Gateway is not a real Gateway that connects to an external service. It does not require any credentials and will consider all actions submitted to it to be automatic successes since it does not actually perform any operations. These are useful for testing order management features that don’t require live Payment Processing or for order management. Only instances of kibo where the actual payment actions have been performed by the storefront service. And the payment information is only being passed into kibo with the order data for fulfillment. Based on the payment gateway selected, enter a “Nickname” and any other necessary authentication credentials. The “Nickname” is used to identify a particular set of credentials and payment gateway when enabling payment types.In this example, for “Apple Pay”, we would also need to provide our merchant website details to Apple in order to validate our implementation of Apple Pay.Learn more about “Apple Pay” configuration in KIBO Documentation. Based on the payment gateway selected, enter a “Nickname” and any other necessary authentication credentials. The “Nickname” is used to identify a particular set of credentials and payment gateway when enabling payment types. In this example, for “Apple Pay”, we would also need to provide our merchant website details to Apple in order to validate our implementation of Apple Pay. Learn more about “Apple Pay” configuration in KIBO Documentation. As mentioned earlier, “Payment Extensibility” is a feature that allows users to add new gateways to use in a tenant by creating an application in the KIBO Dev Center, configuring that application as a gateway adapter, and then installing that application in their tenant.This is the KIBO Dev Center. We did a full overview of the Dev Center in a previous video. As mentioned earlier, “Payment Extensibility” is a feature that allows users to add new gateways to use in a tenant by creating an application in the KIBO Dev Center, configuring that application as a gateway adapter, and then installing that application in their tenant. This is the KIBO Dev Center. We did a full overview of the Dev Center in a previous video. On the “Applications” menu, we’ll click the “Create Application” button on the top right. On the “Applications” menu, we’ll click the “Create Application” button on the top right. This will open a “Create Application” modal window, where we can give our new “Payment Gateway” application a required “Name” and “Application ID”. When completed, we’ll click the “Save” button. This will open a “Create Application” modal window, where we can give our new “Payment Gateway” application a required “Name” and “Application ID”. When completed, we’ll click the “Save” button. When we’ve clicked “Save”, it will open the “Application Configuration” menu screen, like we see here. When we’ve clicked “Save”, it will open the “Application Configuration” menu screen, like we see here. Once we’re in the “Configuration” screen for our “New Payment Gateway” app, we’ll click the “Packages” tab on the left, then click the “Capabilities” tab. Once we’re in the “Configuration” screen for our “New Payment Gateway” app, we’ll click the “Packages” tab on the left, then click the “Capabilities” tab. Then we’ll click the “Add Capability” button on the right. Then we’ll click the “Add Capability” button on the right. This will open the “Add Capability” modal window, which gives us access to multiple validators, adapters, and a “Tax Calculator”. We’ll click “Payment Gateway Adapter”. This will open the “Add Capability” modal window, which gives us access to multiple validators, adapters, and a “Tax Calculator”. We’ll click “Payment Gateway Adapter”. When we’ve selected “Payment Gateway Adapter” from the dropdown, we’ll click the “Ok” button. When we’ve selected “Payment Gateway Adapter” from the dropdown, we’ll click the “Ok” button. This displays the Configure Payment Gateway Adapter screen. This displays the Configure Payment Gateway Adapter screen. Here, we’ll enter our Payment Gateway endpoint URL. This field is used for payment gateway testing only. It indicates the endpoint for the payment gateway processor. Here, we’ll enter our Payment Gateway endpoint URL. This field is used for payment gateway testing only. It indicates the endpoint for the payment gateway processor. In the Gateway Configuration field, a template is displayed for us to enter configurations for our payment gateway in JSON format. In the Gateway Configuration field, a template is displayed for us to enter configurations for our payment gateway in JSON format. Next, we’ll select the countries whose payments we want this payment gateway to process. Next, we’ll select the countries whose payments we want this payment gateway to process. Then we’ll click the “Save” button to save the configuration. Then we’ll click the “Save” button to save the configuration. Lastly, we’ll click the “Save” button on the top right to save our “New Payment Gateway” application. There are a few more steps to add the application to our tenant and test it, and instructions for that can be found in KIBO Documentation. Lastly, we’ll click the “Save” button on the top right to save our “New Payment Gateway” application. There are a few more steps to add the application to our tenant and test it, and instructions for that can be found in KIBO Documentation.

Want to learn more?

Payment Gateways

Learn more about this topic

Payment Overview

Learn more about this topic