walletlayer/laravel

WalletLayer Laravel package for hosted checkout integrations.

Maintainers

Package info

github.com/walletlayerio-spec/walletlayer-laravel

Homepage

pkg:composer/walletlayer/laravel

Transparency log

Statistics

Installs: 0

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

Security

Advisories: 0

Aikido package health analysis

v0.2.0 2026-07-17 22:29 UTC

Requires

MIT b78b0d450d8865102d9b207eff14e8a0066b861d

checkoutpaymentscryptolaravelwebhookswalletlayer

Published on Packagist.org on 2026-07-17 22:56 UTC

This package is auto-updated.

Last update: 2026-07-17 22:56:05 UTC

README

WalletLayer Laravel package for server-side checkout integrations.

This package is free to use. WalletLayer billing is based on confirmed checkout transactions and the active plan on your WalletLayer account.

Setup

  1. Create a WalletLayer merchant account.
  2. Create an API key from the dashboard with your brand name, logo, support email, and enabled currencies.
  3. Copy the API secret when it is shown. It is displayed once only.
  4. Install the Laravel package with Composer or download the package zip.
  5. Publish or configure the WalletLayer settings for your Laravel application.
  6. Store the API key, API secret, WalletLayer API URL, and local encryption settings in your environment file or secret manager.
  7. Keep all secrets on your backend only. Do not expose the API secret in Blade templates, frontend builds, mobile apps, or public repositories.
  8. Activate the package from your backend using signed API credentials.
  9. Create the checkout session from your backend and redirect the customer to the hosted WalletLayer checkout URL.
  10. After your webhook route is available, add the webhook URL in the API key settings inside WalletLayer.
  11. Verify WalletLayer payment events before crediting an order, subscription, wallet balance, or customer account.

Security Notes

  • All operational API communication must be signed with your API secret.
  • Wallet mnemonics, encryption keys, treasury private keys, and sweep signing material must remain on your server.
  • If your integration performs local sweeping, estimate live network gas at sweep time and add a small buffer, usually about 10%, instead of using a fixed hardcoded gas amount.
  • WalletLayer should receive only the checkout and public payment metadata required to process the hosted checkout.
  • Review the package source before production use and pin versions in your deployment pipeline.

Billing Notes

The Free plan includes a small monthly transaction allowance. Paid plans increase the included monthly volume. When a plan allowance is exceeded, WalletLayer can charge overage from the merchant balance. If the balance is insufficient, checkout is disabled until the account is funded or the plan is upgraded.