[1.0.x]Redsys Button

Created on 9 May 2024, 6 months ago

With this module, we can create a payment form in Drupal compatible with RedSys without the need to use Commerce. In other words, this module allows you to solve two very common problems easily. Let's see what they are:

  1. I want to receive payments through RedSys on my website, whether for collecting donations, billing invoices, or any other reason; and I don't want to have to set up the whole infrastructure, heaviness, and maintenance of a commerce module.
  2. I have the Commerce module installed, working, and my store sells perfectly, but I want to separate the payments I make for my consultancy invoices from the sales I make through the POS in my online store, I want these payments to come via RedSys because PayPal charges a high fee and some customers do not want transfers.

RedSys is the most used method by most banks within Spain: Banco Santander, BBVA, La Caixa, Banco Sabadell, ING, etc.

Project link

https://www.drupal.org/project/redsys_button

📌 Task
Status

Closed: duplicate

Component

module

Created by

🇪🇸Spain alexjluna

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @alexjluna
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    Thank you for applying!

    Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smother review.

    The important notes are the following.

    • If you have not done it yet, you should run phpcs --standard=Drupal,DrupalPractice on the project, which alone fixes most of what reviewers would report.
    • For the time this application is open, only your commits are allowed.
    • The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status won't be changed by this application and no other user will be able to opt projects into security advisory policy.
    • We only accept an application per user. If you change your mind about the project to use for this application, please update the issue summary to give the link to the correct project link and the issue title to contain that project name.

    To the reviewers

    Please read How to review security advisory coverage applications , What to cover in an application review , and Drupal.org security advisory coverage application workflow .
    Reviewers only describe what needs to be changed; they don't provide patches to fix what reported in a review.

  • Status changed to Closed: duplicate 6 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    It appears there are multiple project applications created using your account.

    Since a successful completion of the project application process results in the applicant being granted the necessary role to be able to opt projects into security advisory coverage, there is no need to take multiple applications through the process. Once the first application has been successfully approved, the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers, which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as Closed (duplicate), with only one application left open.

  • 🇪🇸Spain alexjluna

    ok, thank you so much!

Production build 0.71.5 2024