Libraries tagged by rule engine

rogervila/php-simple-rules-engine

3 Favers
318 Downloads

PHP Simple Rules Engine

Go to Download


uuf6429/rune

68 Favers
11652 Downloads

PHP Rule Engine.

Go to Download


rawsrc/phpecho

11 Favers
99 Downloads

A native PHP template engine in one class: One class to rule them all

Go to Download


msp/module-notifier-event-api

0 Favers
25874 Downloads

Event based rule engine for MSP Notifier API

Go to Download


msp/module-notifier-event

1 Favers
25683 Downloads

Event based rule engine for MSP Notifier

Go to Download


softonic/jaxer

3 Favers
2242 Downloads

PHP Engine Rule to rule them all

Go to Download


briqpay/php-sdk

0 Favers
9383 Downloads

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. ![alt](https://cdn.briqpay.com/static/developer-portal/checkout-integration.png) # 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: ![alt](https://cdn.briqpay.com/static/developer-portal/suspend-resume.png) 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


zenithsu/easy-rules

4 Favers
165 Downloads

Easy Rules is a PHP rules engine inspired by the easy rules project in java.

Go to Download


vouchedfor/rules-bundle

2 Favers
3317 Downloads

Rules engine for Symfony

Go to Download


samsin33/laravel-decision-engine

4 Favers
8 Downloads

This package provide support for making decision engine in laravel.

Go to Download


robbertstevens/ruleengine

16 Favers
105 Downloads

A simple Rule Engine written in PHP

Go to Download


mpoiriert/business-rule-engine

8 Favers
1367 Downloads

Reusable library

Go to Download


linio/rule-engine

6 Favers
4040 Downloads

Versatile rule engine that allows to apply logic to a given context.

Go to Download


drinks-it/rule-engine

0 Favers
6431 Downloads

Rule Engine Bundle is a (sub)system which allows end-user to run specified actions if they met specified criteria(conditions) on specified events.

Go to Download


braga/enginerule

0 Favers
4023 Downloads

RuleEngine

Go to Download


<< Previous Next >>