Libraries tagged by nina
nanawel/zend-db-sql-insertmultiple
6182 Downloads
n0nag0n/fatfree-xss-filter
880 Downloads
XSS Filter to properly clean your request data from XSS related attacks.
n0nag0n/fatfree-tracy-extensions
192 Downloads
A few Fat-Free specific extensions for Tracy Debugger to help debug your code quickly.
feature-ninja/testing-matrix
391 Downloads
Easily test multiple scenarios by creating a testing matrix
diego-ninja/laravel-censor
533 Downloads
A content moderation and sentiment analysis library for Laravel 10+
web-id/flan
2923 Downloads
FLAN - Filter Like A Ninja
tuta/terbilang
1738 Downloads
Menampilkan nilai terbilang dari jumlah uang atau angka
nanbando/mysql
5265 Downloads
Nanando-Plugin to backup mysql databases
ernilambar/coding-standard
1052 Downloads
Nilambar Coding Standard for PHP_CodeSniffer.
dekodeinteraktiv/hogan-form
11772 Downloads
Form Module for Hogan, requires Gravity Forms, Contact Form 7 or Ninja Forms.
briqpay/php-sdk
10439 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"
wshafer/ninja-mutex-zf2
24230 Downloads
ZF2 Wrapper for arvenil/ninja-mutex.
webvision/invoice-ninja-xrechnung
59 Downloads
Add-on module for Invoice Ninja 5.x to create electronic invoices for Germany's xRechnung format
tombroucke/ninja-forms-bootstrap-classes
3056 Downloads
tajmahal86/ninja-mutex
730 Downloads
Simple to use mutex implementation that can use flock, memcache, memcached, mysql or redis for locking