Libraries tagged by AcceptJS

vendor-patch/composer-installers-extender

0 Favers
40 Downloads

Extend the composer/installers plugin to accept any arbitrary package type.

Go to Download


vella/vellapay-magento2x

1 Favers
41 Downloads

VellaPay Payment gateway for accepting fiat and crypto payments globally

Go to Download


uzdevid/yii2-cardlink

3 Favers
11 Downloads

Service for accepting payments on the Internet, with a fast connection and a modern API.

Go to Download


troupe-tecnologia/accent-string-regex-builder

0 Favers
224 Downloads

Simple helper to create a regex from string to match all the results ignoring accents.

Go to Download


trex/codeception-selenium

0 Favers
246 Downloads

A extension to start selenium server before acceptance test suite starts and stop it at the end of execution

Go to Download


tidycode/magento2-ai-fraud-detection

1 Favers
3 Downloads

Allows you to analyze orders placed and determine which of them are suspected frauds. You can specify the degree of personally acceptable risk or report fali positives and false negatives

Go to Download


svscorp/yandexkassa-bundle

0 Favers
16 Downloads

Bundle allows you to accept YandexKassa payments

Go to Download


stephencoduor/rave-magento2

0 Favers
12 Downloads

Rave payment gateway for accepting payments via credit/debit cards, bank accounts, Mpesa, Ghana Mobile Money and Barter on your Magento store.

Go to Download


souldigital/silverstripe-userforms-payments

2 Favers
104 Downloads

UserForms Payments enables CMS users to create dynamic forms that accept payment via a drag and drop interface and without getting involved in any PHP code

Go to Download


shell/data-and-reporting-sdk

0 Favers
61 Downloads

Data And Reporting product consists of API's which provides details of transaction and invoice informations about shell cards. The Shell Card Transaction and Invoice API is REST-based and employs Basic authentication in Version 1 and Oauth authentication in Version 2 end points. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes. All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources.

Go to Download


shell/card-management-sdk

0 Favers
49 Downloads

The Shell Card Management API is REST-based and employs OAUTH 2.0,Basic and ApiKey authentication. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes.All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources. The internal workings of the platform are not important when interacting with the API. However, it is worth noting that the platform uses a microservice architecture to communicate with various backend systems and some API calls are processed asynchronously. All endpoints use the POST verb for retrieving, updating, creating and deleting resources in the Shell Card Platform. The endpoints that retrieve resources from the Shell Card Platform allow flexible search parameters in the API request body.

Go to Download


seunex17/paychant-php

3 Favers
18 Downloads

The easiest way to accept crypto currency payment on you website

Go to Download


seizonio/laravel-php-code-analysis-hook

3 Favers
74 Downloads

A GIT pre-commit hook for running php code sniffer, php mess detector and phpunit before a commit can be accepted.

Go to Download


segnivo/php-sdk

0 Favers
0 Downloads

**API Version**: 1.7 **Date**: 9th July, 2024 ## 📄 Getting Started This API is based on the REST API architecture, allowing the user to easily manage their data with this resource-based approach. Every API call is established on which specific request type (GET, POST, PUT, DELETE) will be used. The API must not be abused and should be used within acceptable limits. To start using this API, you will need not create or access an existing Segnivo account to obtain your API key ([retrievable from your account settings](https://messaging.segnivo.com/account/api)). - You must use a valid API Key to send requests to the API endpoints. - The API only responds to HTTPS-secured communications. Any requests sent via HTTP return an HTTP 301 redirect to the corresponding HTTPS resources. - The API returns request responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key or with details in the message key. ### 🔖 **Need some help?** In case you have questions or need clarity with interacting with some endpoints feel free to create a support ticket on your account or you can send an email ([[email protected]](https://mailto:[email protected])) directly and we would be happy to help. --- ## Authentication As noted earlier, this API uses API keys for authentication. You can generate a Segnivo API key in the [API](https://messaging.segnivo.com/account/api) section of your account settings. You must include an API key in each request to this API with the `X-API-KEY` request header. ### Authentication error response If an API key is missing, malformed, or invalid, you will receive an HTTP 401 Unauthorized response code. ## Rate and usage limits API access rate limits apply on a per-API endpoint basis in unit time. The limit is 10k requests per hour for most endpoints and 1m requests per hour for transactional/relay email-sending endpoints. Also, depending on your plan, you may have usage limits. If you exceed either limit, your request will return an HTTP 429 Too Many Requests status code or HTTP 403 if sending credits have been exhausted. ### 503 response An HTTP `503` response from our servers may indicate there is an unexpected spike in API access traffic, while this rarely happens, we ensure the server is usually operational within the next two to five minutes. If the outage persists or you receive any other form of an HTTP `5XX` error, contact support ([[email protected]](https://mailto:[email protected])). ### Request headers To make a successful request, some or all of the following headers must be passed with the request. | **Header** | **Description** | | --- | --- | | Content-Type | Required and should be `application/json` in most cases. | | Accept | Required and should be `application/json` in most cases | | Content-Length | Required for `POST`, `PATCH`, and `PUT` requests containing a request body. The value must be the number of bytes rather than the number of characters in the request body. | | X-API-KEY | Required. Specifies the API key used for authorization. | ##### 🔖 Note with example requests and code snippets If/when you use the code snippets used as example requests, remember to calculate and add the `Content-Length` header. Some request libraries, frameworks, and tools automatically add this header for you while a few do not. Kindly check and ensure yours does or add it yourself.

Go to Download


sc_zencart/commerce_spectrocoin_zencart

0 Favers
4 Downloads

accept bitcoin payments in your zencart project

Go to Download


<< Previous Next >>