PHPackages                             robbinc91/botble-redsys - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Payment Processing](/categories/payments)
4. /
5. robbinc91/botble-redsys

ActivePackage[Payment Processing](/categories/payments)

robbinc91/botble-redsys
=======================

Redsys Payment Gateway for Botble CMS

v0.2.0(1mo ago)00MITPHPPHP >=8.2.11

Since May 8Pushed 1mo agoCompare

[ Source](https://github.com/robbinc91/botble-redsys)[ Packagist](https://packagist.org/packages/robbinc91/botble-redsys)[ Docs](https://github.com/robbinc91/botble-redsys)[ RSS](/packages/robbinc91-botble-redsys/feed)WikiDiscussions main Synced 1w ago

READMEChangelog (1)Dependencies (1)Versions (3)Used By (0)

Botble Redsys Plugin
====================

[](#botble-redsys-plugin)

Redsys (Servired / Sermepa) payment gateway integration for Botble CMS.

Package metadata
----------------

[](#package-metadata)

FieldValue**Composer package**`robbinc91/botble-redsys`**Homepage / source**[github.com/robbinc91/botble-redsys](https://github.com/robbinc91/botble-redsys)**Plugin ID** (`plugin.json`)`robbinc91/botble-redsys`**PHP namespace**`Botble\Redsys\`**Author**Robin Cabeza Ruiz**License**MITFeatures
--------

[](#features)

- Redsys as a checkout payment method (with Botble `payment` plugin).
- Redsys settings under **Admin → Payments**.
- Signed notification handling and optional OK-return verification.
- Successful payments fire Botble’s `PAYMENT_ACTION_PAYMENT_PROCESSED` hook.
- Idempotent processing to reduce duplicate payment rows.

Requirements
------------

[](#requirements)

- **PHP** `>= 8.2.11` (see `composer.json`).
- **Botble** with **`botble/payment`** plugin installed and active.
- **HTTPS** on production for callback URLs.
- Redsys **notification URL** must be reachable from Redsys servers.

Dependencies
------------

[](#dependencies)

- **`botble/payment`** — required Botble plugin (`plugin.json`).
- **`ssheduardo/redsys-laravel`** `~1.5.0` — Redsys Laravel SDK (`composer.json`).

### Composer vs `vendor/robbinc91`

[](#composer-vs-vendorrobbinc91)

If you only copy this plugin into **`platform/plugins/redsys`** and run **`composer update`** at the project root, Composer installs **merged dependencies** (e.g. `ssheduardo/redsys-laravel`) into **`vendor/`**. It does **not** necessarily create **`vendor/robbinc91/botble-redsys`** unless the root app **`composer require`s** `robbinc91/botble-redsys`. That layout is normal for Botble plugins deployed as files under `platform/plugins/`.

**Option A (merge-plugin):** SDK is declared in this plugin’s `composer.json` and resolved into the app’s root `vendor/` after `composer update`.

Installation
------------

[](#installation)

### Method A — Copy into Botble (most common)

[](#method-a--copy-into-botble-most-common)

1. Put the plugin folder here (folder name **`redsys`**):

    `platform/plugins/redsys`
2. From the **project root**:

    ```
    composer update
    ```
3. Activate using the **directory name** under `platform/plugins` (here **`redsys`**). Botble’s CLI strips any `vendor/` prefix but still resolves the folder — **`cms:plugin:activate botble-redsys` would not match** if your folder is `redsys`.

    ```
    php artisan cms:plugin:activate redsys
    ```

    Or use **Admin → Plugins**.

### Method B — Install as Composer package (optional)

[](#method-b--install-as-composer-package-optional)

If the package is on Packagist or a VCS repository configured in the root `composer.json`:

```
composer require robbinc91/botble-redsys:^1.0
```

You still need the plugin **discovered by Botble** under `platform/plugins/redsys` (copy, symlink, or your deployment strategy). Botble scans **direct children** of `platform/plugins`, not arbitrary nested vendor paths.

Configuration
-------------

[](#configuration)

**Admin → Payments** — enable Redsys and set:

- Merchant code (FUC)
- Terminal
- SHA-256 secret key
- Environment: `test` or `live`
- Trade name

HTTP routes
-----------

[](#http-routes)

MethodPathNameGET`/payment/redsys/checkout``payments.redsys.checkout`POST`/payment/redsys/notification``payments.redsys.notification`GET`/payment/redsys/ok``payments.redsys.ok`GET`/payment/redsys/ko``payments.redsys.ko`Configure Redsys backoffice (example):

- **Notification:** `https://your-domain.com/payment/redsys/notification`
- **OK:** `https://your-domain.com/payment/redsys/ok`
- **KO:** `https://your-domain.com/payment/redsys/ko`

CSRF
----

[](#csrf)

Exclude the notification route from CSRF verification (Redsys server POST has no Laravel token):

- Path prefix / URI: **`payment/redsys/notification`**

(Typically in `app/Http/Middleware/VerifyCsrfToken.php` `$except`.)

Integration behaviour
---------------------

[](#integration-behaviour)

- **Notification** (`POST …/notification`) is the primary authoritative confirmation.
- **OK** return can assist when session/callback ordering differs; signatures are verified when Redsys sends parameters.
- Hotel/booking flows that listen for `PAYMENT_ACTION_PAYMENT_PROCESSED` behave like other gateways (e.g. Stripe) once this hook runs.

Verify installation
-------------------

[](#verify-installation)

```
php artisan route:list --name=payments.redsys
```

Expect four routes named `payments.redsys.*`.

Then: test mode checkout → confirm notification → confirm payment and order/booking linkage → switch to live credentials.

Translations
------------

[](#translations)

Language files live under `resources/lang/{locale}/redsys.php` (e.g. `en`, `es`).

###  Health Score

36

—

LowBetter than 79% of packages

Maintenance94

Actively maintained with recent releases

Popularity0

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity37

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

2

Last Release

32d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/aac6c4212a97a36941e5404eab00434359dcedbf0c9eee3aa5c34c7e588c50af?d=identicon)[robbinc91](/maintainers/robbinc91)

---

Top Contributors

[![robbinc91](https://avatars.githubusercontent.com/u/35306990?v=4)](https://github.com/robbinc91 "robbinc91 (5 commits)")

---

Tags

redsyspayment gatewaybotble

### Embed Badge

![Health badge](/badges/robbinc91-botble-redsys/health.svg)

```
[![Health](https://phpackages.com/badges/robbinc91-botble-redsys/health.svg)](https://phpackages.com/packages/robbinc91-botble-redsys)
```

###  Alternatives

[shetabit/payment

Laravel Payment Gateway Integration Package

943336.8k5](/packages/shetabit-payment)[shetabit/multipay

PHP Payment Gateway Integration Package

293355.3k4](/packages/shetabit-multipay)[sermepa/sermepa

Pasarela de pago Redsys, Sermepa

209412.2k8](/packages/sermepa-sermepa)[cybersource/rest-client-php

Client SDK for CyberSource REST APIs

40930.1k6](/packages/cybersource-rest-client-php)[ssheduardo/redsys-laravel

Package redsys for laravel

101136.5k2](/packages/ssheduardo-redsys-laravel)[jomweb/billplz

PHP Agnostic library for working with BillPlz API

77201.2k3](/packages/jomweb-billplz)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)