Libraries tagged by php events
opiy-org/asterisk-ari-php
1188 Downloads
An object-oriented client for the Asterisk REST Interface (ARI). Handles ARI calls and events for you.
maatify/event-logging
54 Downloads
Framework-agnostic standalone event logging library containing isolated Maatify logging domains. Depends only on explicit Composer/runtime dependencies.
idimsh/php-inotify-monitor
554 Downloads
A wrapper library around PHP Inotify Extension and React PHP to monitor files/directories for 3 main events: Create, Modify, Delete
g-portal/lago-php-client
4306 Downloads
Lago API allows your application to push customer information and metrics (events) from your application to the billing application.
devco/event-emitter
112346 Downloads
Port of NodeJSs EventEmitter to PHP 5.4 using traits
codemonster-ru/events
168 Downloads
PSR-14 event dispatcher primitives for Annabel applications.
briqpay/php-sdk
11964 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.  # 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"
bayfrontmedia/php-hooks
1921 Downloads
An easy to use hooks library for managing events and filters.
amashukov/rector-php-rules
864 Downloads
Opinionated Rector rules for PHP — strict-assertion enforcement, no @phpstan-ignore, no env-checks in src, no superglobals, PSR Clock requirement, no direct DB / event-dispatch / assert() inside functional tests, and a comment-stripper that keeps only PHPStan tag blocks.
zenaton/zenaton-php
43694 Downloads
Zenaton PHP library
prooph/prooph-event-store-module
2650 Downloads
ZF2 module that provides default functionality to use ProophEventStore in a ZF2 application
lp-digital/github-event-parser
2899 Downloads
PHP library to get a readable representation of events dispatched by Github API v3
lastguest/ev
17 Downloads
A PHP Event emitter in only 103bytes
foolz/plugin
2100 Downloads
A plugin system for PHP, with cascading events.
jardisadapter/eventdispatcher
161 Downloads
PSR-14 event dispatcher for PHP with priority-ordered listeners, type-hierarchy matching, stoppable events, and deferred dispatch via EventCollector; a building block of the open-source foundation that Jardis-generated DDD code runs on