Libraries tagged by ostatus

maxfrerichs/typo3-prometheus

0 Favers
165 Downloads

Generates Prometheus-readable metrics from TYPO3 system status reports

Go to Download


markguinn/silverstripe-ajax

9 Favers
5956 Downloads

Foundational ajax support for Silverstripe CMS: push/pull server-side regions, trigger client-side events, modals, status messages.

Go to Download


mantix/livewire-kanban-board

2 Favers
159 Downloads

Livewire component to show models/data according to its current status on a Kanban board

Go to Download


magenerds/cronprocesscheck

1 Favers
14328 Downloads

Cron Process check for Magento 2. This modules checks if a cron job process crashed and sets its status to error.

Go to Download


lilt/lilt-connector-sdk-php

0 Favers
7171 Downloads

This document describes the Plugin API for Lilt's Connector platform. The Plugin API is intented to be used by developers who wish to build integrations into their desired systems. The purpose of this API is to enable content transfer and status monitoring for localization projects. - Read more about the concepts and workflows in the [user guide](/docs/api/v1.0). - Test the API interactively via [Swagger UI](/api/v1.0/ui).

Go to Download


lantongxue/php-nohup

1 Favers
7154 Downloads

A library to run a command in the background, it will return the process's pid, and get it's is running status anytime in the another process, and can be stoped anytime. It support Windows, Linux and Mac osx.

Go to Download


igorludgero/colorstatus

0 Favers
2719 Downloads

With this extension you can configure a background color for each order status in Magento 2, and when you access the sales order grid the background of each order will be filled by the configured background color.

Go to Download


havvg/http-exception

2 Favers
11970 Downloads

A collection of exception classes to reflect HTTP status codes.

Go to Download


galata90/php-mail-bounce-handler

12 Favers
2396 Downloads

PHP class to help webmasters handle bounce-back, feedback loop and ARF mails in standard DSN (Delivery Status Notification, RFC-1894).

Go to Download


dgr/nohup

53 Favers
1673 Downloads

A library to run a command in the background, it will return the process's pid, and get it's is running status anytime in the another process, and can be stoped anytime. It support Windows, Linux and Mac osx.

Go to Download


devscreencast/json-response

9 Favers
123 Downloads

A simple class that returns a properly formatted json response with HTTP status

Go to Download


corpus/http

0 Favers
2851 Downloads

HTTP Status Codes and Exceptions

Go to Download


clarkwinkelmann/flarum-ext-who-read

1 Favers
6371 Downloads

Make read status visible to selected groups

Go to Download


bufferapp/update-converters

1 Favers
15499 Downloads

Convert statuses from Twitter, Facebook and Instagram into Buffer updates

Go to Download


briqpay/php-sdk

0 Favers
9343 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


<< Previous Next >>