Download the PHP package mymage/saasykit-peachpayments without Composer

On this page you can find all versions of the php package mymage/saasykit-peachpayments. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of mymage/saasykit-peachpayments

Informations about the package saasykit-peachpayments

SaasyKit Peach Payments Package

Adds Peach Payments as a payment provider to SaasyKit — one-time purchases via Hosted Checkout V2, and subscriptions via card tokenization + a scheduled recurring (MIT) charge command.

Requirements

This is a publish-into-app package: it copies its app/, resources/views/, and public/ files directly into your SaasyKit installation and requires a short manual wiring step (below), matching how the built-in providers (Stripe/Paddle/Polar/LemonSqueezy) live inside SaasyKit itself.

Install

1. Require the package

(Or, while developing locally, add a path/VCS repository entry pointing at this repo and composer require mymage/saasykit-peachpayments:@dev.)

2. Publish the files

This copies:

3. Wire it into the host app

The package intentionally does not register anything in the container — do this explicitly so it is visible in your app's own code.

(a) Tag the provider — app/Providers/AppServiceProvider.php

(b) Add the slug constant — app/Constants/PaymentProviderConstants.php

(c) Seed the provider row — database/seeders/PaymentProvidersSeeder.php

(d) Add the config block — config/services.php

(e) Whitelist the config keys — app/Constants/ConfigConstants.php

Add to OVERRIDABLE_CONFIGS:

Add the secret ones to ENCRYPTED_CONFIGS (identifiers like entity/client/merchant ID are not secrets and are intentionally left out):

(f) Register the settings page — app/Filament/Admin/Resources/PaymentProviders/PaymentProviderResource.php

(g) Add the routes — routes/api.php

Both routes must stay outside CSRF protection (the api group already is) since they're called by Peach Payments' servers / a cross-site browser POST-back, not your own app.

(h) Schedule renewal charges — routes/console.php

(withoutOverlapping() plus per-subscription row locking inside the command guard against double-charging if runs ever overlap.)

(i) Use the settings page

Visit Admin → Payment Providers → Peach Payments Settings to enter your credentials (Entity ID, Secret Token, Client ID/Secret, Merchant ID, Recurring Entity ID/Access Token, Test Mode toggle). The page's "how to" panel walks through where to find each value in the Peach Payments dashboard.

(j) Peach Payments dashboard setup

How subscriptions work

Peach Payments has no native subscription object. The first checkout tokenizes the card (createRegistration=true → registrationId), which is stored on subscriptions.extra_payment_provider_data. The app:peachpayments-charge-renewals command (scheduled hourly) charges that token via Peach's recurring/MIT API whenever a subscription's ends_at is due, then advances ends_at by one billing interval. Failed renewal charges are retried daily (default 3 attempts, max_renewal_retries) with the subscription marked past_due, then canceled.

Notes and current limitations:

Testing

The package ships a PHPUnit test suite (client signature scheme, webhook handler including replay/refund/partial-refund cases, and the renewal command's success/dunning/cancellation paths). Publish it into your app's tests/ directory and run it:

For end-to-end verification, use Peach's sandbox credentials and hosts (test_mode enabled) end-to-end: run a checkout, confirm the webhook and checkout-result routes fire (webhooks need a publicly reachable URL — use a tunnel for local dev, or simulate with signed curl POSTs), then force a subscription's ends_at into the past and run php artisan app:peachpayments-charge-renewals to observe a sandbox MIT charge.

All versions of saasykit-peachpayments with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package mymage/saasykit-peachpayments contains the following files

Loading the files please wait ...