Libraries tagged by iveri
magadanuhak/laravel-provably-fair
2157 Downloads
A Laravel package to get Provably Fair random numbers that user can verify
mactape/la-rules
188 Downloads
Laravel rules for verifying the correctness of entered personal data
libriciel/file-validator
1917 Downloads
Permet de vérifier la validité d'un fichier
lexide/pharmacist
767 Downloads
Verifies that your syringe config is correct
juvo/wp-secure-actions
2240 Downloads
Framework to securely handle verifiable actions in wordpress
ibrahem-kamal/laravel-otp
634 Downloads
generate and verify otp being sent to users
h2entwicklung/sign-checker
7011 Downloads
Verifies
eighteen73/laravel-turnstile
851 Downloads
Add Cloudflare Turnstile verification to Laravel forms
dicibi/eloquent-modification
1730 Downloads
Capture, Rollback and Verify Changes on Eloquent
danielburger1337/openid-hash
108 Downloads
Create/Verify OpenID Connect (OIDC) verification hashes.
danielburger1337/oauth2-pkce
89 Downloads
Create/Verify OAuth2 PKCE code challenges.
danielburger1337/oauth2-dpop
98 Downloads
Create/Verify OAuth2 DPoP tokens.
copernica/webhook-security
3167 Downloads
PHP lib to verify webhook security
clearvox/constraints-date
10884 Downloads
DateTime Constraints Library. Use this to add constraints to a validator and verify DateTime objects pass those constraints.
briqpay/php-sdk
9489 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"