Skip to content

Latest commit

 

History

History
26 lines (23 loc) · 1.47 KB

heidelpay-oms-workflow.md

File metadata and controls

26 lines (23 loc) · 1.47 KB
Raw
title last_updated template originalLink originalArticleId redirect_from
Heidelpay OMS workflow
Jun 16, 2021
concept-topic-template
604f600e-3f95-4194-90ed-4b2f7e9fac26
/2021080/docs/heidelpay-oms-workflow
/2021080/docs/en/heidelpay-oms-workflow
/docs/heidelpay-oms-workflow
/docs/en/heidelpay-oms-workflow
/docs/scos/dev/technology-partner-guides/202200.0/payment-partners/heidelpay/heidelpay-oms-workflow.html
/docs/scos/dev/technology-partner-guides/202307.0/payment-partners/heidelpay/heidelpay-oms-workflow.html
/docs/pbc/all/payment-service-provider/202307.0/third-party-integrations/heidelpay/heidelpay-oms-workflow.html

We use state machines for handling and managing orders and payments. To use Heidelpay, create a new OMS which includes necessary Heildelpay payment methods. You can use the same state machines or build new ones. The state machine commands and conditions trigger Heidelpay facade calls in order to perform the needed requests to Heidelpay API.

Some examples of the basic and fully functional state machines for each payment method were already built: vendor/spryker-eco/heidelpay/config/Zed/Oms

  • HeidelpaySofort01.xml
  • HeidelpayPaypalDebit01.xml
  • HeidelpayIdeal01.xml
  • HeidelpaySofort01.xml
  • HeidelpayCreditCardSecureAuthorize01.xml