devnet.kentico.com/articles/building-an-integration-stripe-(part-2)

Preview meta tags from the devnet.kentico.com website.

Linked Hostnames

9

Thumbnail

Search Engine Appearance

Google

https://devnet.kentico.com/articles/building-an-integration-stripe-(part-2)

Building an Integration (Stripe) - Part 2 - Web API Controllers

This article series covers the planning and implementation of the Stripe payment gateway implementation.The previous article covered the process of creating necessary settings categories and keys, adding resource strings to the Xperience admin app, and adding Stripe Checkout to the live site.The admin library of this integration has two main tasks to accomplish. First, it needs to accept webhook requests from Stripe and update Xperience orders appropriately. Second, it needs to capture funds for payments using delayed capture.This article will focus on the first part, which is one of the most vital to the integration. With the live site code alone, orders can be paid for through stripe, but there is no way to automatically propagate that information back to Kentico. Store staff would have to manually keep track of orders and update them according to data in Stripe. We’ll create an endpoint so that Stripe webhooks can automatically keep our Xperience orders up to date.



Bing

Building an Integration (Stripe) - Part 2 - Web API Controllers

https://devnet.kentico.com/articles/building-an-integration-stripe-(part-2)

This article series covers the planning and implementation of the Stripe payment gateway implementation.The previous article covered the process of creating necessary settings categories and keys, adding resource strings to the Xperience admin app, and adding Stripe Checkout to the live site.The admin library of this integration has two main tasks to accomplish. First, it needs to accept webhook requests from Stripe and update Xperience orders appropriately. Second, it needs to capture funds for payments using delayed capture.This article will focus on the first part, which is one of the most vital to the integration. With the live site code alone, orders can be paid for through stripe, but there is no way to automatically propagate that information back to Kentico. Store staff would have to manually keep track of orders and update them according to data in Stripe. We’ll create an endpoint so that Stripe webhooks can automatically keep our Xperience orders up to date.



DuckDuckGo

https://devnet.kentico.com/articles/building-an-integration-stripe-(part-2)

Building an Integration (Stripe) - Part 2 - Web API Controllers

This article series covers the planning and implementation of the Stripe payment gateway implementation.The previous article covered the process of creating necessary settings categories and keys, adding resource strings to the Xperience admin app, and adding Stripe Checkout to the live site.The admin library of this integration has two main tasks to accomplish. First, it needs to accept webhook requests from Stripe and update Xperience orders appropriately. Second, it needs to capture funds for payments using delayed capture.This article will focus on the first part, which is one of the most vital to the integration. With the live site code alone, orders can be paid for through stripe, but there is no way to automatically propagate that information back to Kentico. Store staff would have to manually keep track of orders and update them according to data in Stripe. We’ll create an endpoint so that Stripe webhooks can automatically keep our Xperience orders up to date.

  • General Meta Tags

    7
    • title
      Building an Integration (Stripe) - Part 2 - Web API Controllers
    • charset
      UTF-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1, maximum-scale=1
    • google-site-verification
      JWey8gEnlg5ksHr1jGTVwp2WgxUKG9wTYuwP8uGl5L4
  • Open Graph Meta Tags

    5
    • og:title
      Building an Integration (Stripe) - Part 2 - Web API Controllers
    • og:type
      article
    • og:description
      This article series covers the planning and implementation of the Stripe payment gateway implementation.The previous article covered the process of creating necessary settings categories and keys, adding resource strings to the Xperience admin app, and adding Stripe Checkout to the live site.The admin library of this integration has two main tasks to accomplish. First, it needs to accept webhook requests from Stripe and update Xperience orders appropriately. Second, it needs to capture funds for payments using delayed capture.This article will focus on the first part, which is one of the most vital to the integration. With the live site code alone, orders can be paid for through stripe, but there is no way to automatically propagate that information back to Kentico. Store staff would have to manually keep track of orders and update them according to data in Stripe. We’ll create an endpoint so that Stripe webhooks can automatically keep our Xperience orders up to date.
    • og:image
      https://devnet.kentico.com/DevNet/media/ArticleTeasers/Open%20Graph/integrationthumbnail.jpg?ext=.jpg
    • og:site_name
      Kentico DevNet
  • Twitter Meta Tags

    1
    • twitter:card
      summary_large_image
  • Link Tags

    19
    • apple-touch-icon
      /i/favicons/apple-touch-icon-57x57.png
    • apple-touch-icon
      /i/favicons/apple-touch-icon-114x114.png
    • apple-touch-icon
      /i/favicons/apple-touch-icon-72x72.png
    • apple-touch-icon
      /i/favicons/apple-touch-icon-144x144.png
    • apple-touch-icon
      /i/favicons/apple-touch-icon-60x60.png

Links

40