Libraries tagged by in_app_purchases

imdhemy/laravel-purchases

284 Favers
410801 Downloads

The top-notch Laravel receipt validator.

Go to Download


aporat/store-receipt-validator

628 Favers
2988731 Downloads

PHP receipt validator for Apple iTunes, Google Play and Amazon App Store

Go to Download


imdhemy/appstore-iap

39 Favers
448537 Downloads

PHP Appstore In-App Purchase implementation

Go to Download


readdle/app-store-server-api

29 Favers
26231 Downloads

Pure-PHP library that allows managing customer transactions using the App Store Server API and handling server-to-server notifications using the App Store Server Notifications V2

Go to Download


readdle/app-store-receipt-verification

12 Favers
18026 Downloads

Pure PHP App Store receipt parsing/validation/verification without API calls to App Store API.

Go to Download


yanlongli/app-store-server-api

20 Favers
3631 Downloads

PHP client for App Store Server API. Manage your customers’ App Store transactions from your server.The App Store Server API is a REST API that you call from your server to request and provide information about your customers' in-app purchases. The App Store signs the transaction and subscription renewal information that this API returns using the JSON Web Signature (JWS) specification.App Store Server API is independent of the app’s installation status on the customer’s devices. The App Store server returns information based on the customer’s in-app purchase history regardless of whether the customer installed, removed, or reinstalled the app on their devices.To request transaction and subscription status information with this API, provide any original transaction identifier that belongs to the customer. The transaction history API responds with a complete list of transactions, 20 at a time, starting with the oldest first. The subscription status API returns the status for all of the customer’s subscriptions, organized by their subscription group identifier.Use the Send Consumption Information endpoint to send information to the App Store when customers request a refund for a consumable in-app purchase, after you receive the CONSUMPTION_REQUEST App Store server notification. Your data helps inform refund decisions.

Go to Download


alxmsl/appstoreclient

31 Favers
9328 Downloads

AppStore client for iTunes purchases receipts verification

Go to Download


stafox/huawei-iap

7 Favers
8199 Downloads

Huawei In-App Purchase (IAP) verification library

Go to Download


jinseokoh/purchase-webhooks

4 Favers
1770 Downloads

Handling App Purchase Server-to-Server Webhooks

Go to Download


ageekdev/geek-credit

1 Favers
220 Downloads

To simplify credit management and in-app purchases in Laravel apps.

Go to Download


briqpay/php-sdk

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


nikapps/bazaar-api-php

5 Favers
460 Downloads

A PHP API wrapper for CafeBazaar Rest Api v2

Go to Download


ivanarivasq/store-receipt-validator

0 Favers
1972 Downloads

PHP receipt validator for Apple iTunes, Google Play and Amazon App Store

Go to Download


chfur/appgallery-iap

6 Favers
255 Downloads

PHP AppGallery In-App Purchase implementation

Go to Download


trunk-studio/laravel-in-app-purchases

0 Favers
269 Downloads

Laravel receipt validator for Google Play

Go to Download


Next >>