Libraries tagged by order step

Quickly and easily preview and test your Magento2 checkout success page, without placing a new order each time

Go to Download

Hyva theme compatibility for mageme/module-eu-withdrawal. Re-renders the customer-facing withdrawal form (4-step SPA + lookup) and order-view integrations using pure Alpine.js + Tailwind utilities — no KO, no jQuery, no Magewire dependency. Hyva checkout integration (precontract block + waiver step) is shipped separately. NOT legal advice — see README disclaimer.

Go to Download

Optional component extending the bulk shipment mass action by an additional step that allows to select shipping product and packaging per order.

Go to Download

Symfony bundle that provides a step system in order to represent an highly customisable workflow

Go to Download

Journey testing for Laravel: run the steps of a user journey in seeded, shuffled orders and assert invariants along the way.

Go to Download

The payments API is used to create a session to offer Klarna's payment methods as part of your checkout. As soon as the purchase is completed the order should be read and handled using the [`Order Management API`](https://docs.klarna.com/api/ordermanagement). **Note:** Examples provided in this section includes full payloads, including all supported fields , required and optionals. In order to implement a best in class request we recommend you don't include customer details when initiating a payment session. Refer to [Initiate a payment](https://docs.klarna.com/klarna-payments/integrate-with-klarna-payments/step-1-initiate-a-payment/) section for further details. Read more on [Klarna payments](https://docs.klarna.com/klarna-payments/).

Go to Download

A declarative and testable way to model entity state transitions (orders, documents, processes…) with guard conditions, actions, and events.

Go to Download

Shopware 6 analytics: multi-backend (Matomo + Plausible), cookieless by default, respects GPC, with Matomo e-commerce tracking (product views, cart updates, checkout steps, orders with revenue).

Go to Download

This is the API documentation for Briqpay. You can find out more about us and our offering at our website [https://briqpay.com](https://briqpay.com) In order to get credentials to the playgrund API Please register at [https://app.briqpay.com](https://app.briqpay.com) # Introduction Briqpay Checkout is an inline checkout solution for your b2b ecommerce. Briqpay Checkout gives you the flexibility of controlling your payment methods and credit rules while optimizing the UX for your customers # SDKs Briqpay offers standard SDKs to PHP and .NET based on these swagger definitions. You can download them respively or use our swagger defintitions to codegen your own versions. #### For .NET `` Install-Package Briqpay `` #### For PHP `` composer require briqpay/php-sdk `` # Standard use-case As a first step of integration you will need to create a checkout session. \n\nIn this session you provide Briqpay with the basic information necessary. In the response from briqpay you will recieve a htmlsnippet that is to be inserted into your frontend. The snippet provided by briqpay will render an iframe where the user will complete the purchase. Once completed, briqpay will redirect the customer to a confirmation page that you have defined.  # JavaScript SDK The first step of integration is to add our JS to your site just before closing the ```` tag. This ensures that our JS library is avaliable to load the checkout. ```` Briqpay offers a few methods avaliable through our Javascript SDK. The library is added by our iframe and is avalable on ``window._briqpay`` If you offer the posibility to update the cart or order amonts on the checkout page, the JS library will help you. If your store charges the customer different costs and fees depening on their shipping location, you can listen to the ``addressupdate``event in order to re-calculate the total cost. ```javascript window._briqpay.subscribe('addressupdate', function (data) { console.log(data) }) ``` If your frontend needs to perform an action whe the signup has completed, listen to the ``signup_finalized`` event. ```javascript window._briqpay.subscribe('signup_finalized', function (status) { // redirect or handle status 'success' / 'failure' }) ``` If you allow customers to change the total cart value, you can utilise the JS library to suspend the iframe while you perform a backen update call towards our services. As described below:  The iframe will auto-resume after 7 seconds if you dont call ``_briqpay.resume()`` before # Test Data In order to verify your integration you will neeed to use test data towards our credit engine. ## Company identication numbers * 1111111111 - To recieve a high credit scoring company ( 100 in rating) * 2222222222 - To test the enviournment with a bad credit scoring company (10 in rating) ## Card details In our playground setup your account is by default setup with a Stripe integration. In order to test out the card form you can use the below card numbers: * 4000002500003155 - To mock 3ds authentication window * 4000000000000069 Charge is declined with an expired_card code. You can use any valid expiry and CVC code # Authentication Briqpay utilizes JWT in order to authenticate calls to our platform. Authentication tokens expire after 48 hours, and at that point you can generate a new token for the given resource using the ``/auth`` endpoint. - Basic Auth - only used on the auth endpoint in order to get the Bearer Token - JWT Bearer Token - All calls towards the API utlizes this method"

Go to Download

Assign Silverstripe E-commerce orders to a specific shop administrator

Go to Download

add a feedbck step to silverstripe e-commerce

Go to Download

Add additional security checks to your Silverstripe e-commerce install.

Go to Download

Checks for possible fraudulent orders using the minFraud API provided by MaxMind.

Go to Download

Panth EU Withdrawal Button - a clear, accessible digital withdrawal (cancellation) function for Magento 2 and Adobe Commerce that complies with Directive (EU) 2023/2673 (effective 19 June 2026). Guest-capable two-step withdrawal flow, durable-medium email proof, withdrawal link in order emails, configurable 14-day window, admin request management and batch refund reminders. Full Hyva and Luma theme support.

Go to Download

Lightweight, synchronous Saga pattern orchestrator for Laravel. Chain steps with execute()/compensate(), auto-rollback completed steps in reverse order on failure — no queues, no database, no migrations.

Go to Download